Skip to content

chore: remove unused simulated io latency config from UringIoEngineConfig - #26

Closed
detail-app[bot] wants to merge 1 commit into
mainfrom
detail/dead-code/chore-remove-unused-simulated-io-latency-config-fr-77008b
Closed

detail-app[bot] wants to merge 1 commit into
mainfrom
detail/dead-code/chore-remove-unused-simulated-io-latency-config-fr-77008b

Conversation

@detail-app

@detail-app detail-app Bot commented Sep 15, 2026

Copy link
Copy Markdown

Remove the write_io_latency and read_io_latency fields, their None initializers in new(), and the with_write_io_latency/with_read_io_latency setter methods from UringIoEngineConfig.

These symbols were dead: the setters were never called on UringIoEngineConfig anywhere in the workspace (foyer-bench only calls them on PsyncIoEngineConfig), and the fields were written but never read by the uring engine's build/run/read/write paths. They were added for API parity with psync but never wired into the uring engine, and the foyer-bench CLI documents the feature as "Only effective when using psync io engine".

History


Dead Code PRs can be configured here.

@detail-app

detail-app Bot commented Oct 15, 2026

Copy link
Copy Markdown
Author

Closing this pull request because it has had no human activity in 30 days (since 2026-09-15) and was opened 30 days ago. Detail closes its pull requests once they are more than 30 days old and have had no human activity for 14 days.

If this change is still useful, reopen the pull request and Detail won't close it again. To keep a Detail pull request open, add the detail-keep-open label to it.

@detail-app detail-app Bot closed this Oct 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants