refactor(ethexe-processor): Instrument codes in custom threadpool#5258
refactor(ethexe-processor): Instrument codes in custom threadpool#5258
Conversation
Changed Files
|
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request refactors the threadpool implementation and migrates key components of the Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. Footnotes
|
… for `chunk_execution_spawn` module and `spawn_chunk_execution` function
There was a problem hiding this comment.
Code Review
This pull request refactors the code processing pipeline to be asynchronous, transitioning process_code from a synchronous to an async function across the compute and processor crates. Key changes include replacing tokio::task::JoinSet with futures::stream::FuturesUnordered in the CodesSubService and introducing a custom thread pool to handle blocking operations such as code instrumentation and chunk execution. Consequently, numerous tests have been updated to use tokio::test and await. Feedback was provided regarding a critical recursive call in the ProcessorExt implementation for Processor that would result in a stack overflow, along with a suggestion to disambiguate the call using fully qualified syntax.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a36adbc2b8
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Also refactor threadpool a little bit