-
Notifications
You must be signed in to change notification settings - Fork 1
Virtual / Hardware threads, remove libcurl (event loop) #5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Summary of ChangesHello @malvads, 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 represents a significant architectural shift, moving the core crawling engine from a synchronous, Highlights
Changelog
Activity
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. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This is a significant and impressive refactoring that replaces the previous threading model and libcurl/libwebsockets dependencies with a modern, asynchronous approach using Boost.Asio and C++20 coroutines. The separation of concerns into IO threads and a worker thread pool for CPU/disk-bound tasks is excellent. The introduction of a storage abstraction and improved robots.txt handling (including Crawl-delay) are also great additions. I've found a few critical issues related to data correctness and security, along with some high-severity resource leaks and suggestions for improvement. Overall, this is a fantastic step forward for the project's architecture.
|
/gemini review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This is a significant and impressive refactoring of the crawler's core networking and concurrency model. The transition from libcurl and std::thread to Boost.Asio with C++20 coroutines is a major architectural improvement that greatly enhances readability and maintainability. The introduction of a dedicated storage abstraction and the support for Crawl-delay are also excellent additions. I've identified a critical bug in the new termination logic that could cause the crawler to hang, along with a few other potential issues related to error handling and robustness. Once these are addressed, this will be a very solid foundation for the project.
a46404d to
94eae51
Compare
…solve build conflicts
458c96c to
dcb4848
Compare
No description provided.