Conversation
…ed metrics paths, copied walkthrough
Summary of ChangesHello @heidi-dang, 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 integrates a new 'P6/doctor preflight' feature into the Highlights
Changelog
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.
Code Review
The pull request updates the build configuration to include new core components and tests. However, it inadvertently includes a large volume of generated build artifacts, binaries, and dependency source code within the build/ directory. These files should be removed from the repository and managed via a .gitignore file to keep the repository clean and avoid environment-specific conflicts. Additionally, some improvements to the CMake configuration are recommended to improve portability and maintainability.
| @@ -0,0 +1,592 @@ | |||
| # This is the CMakeCache file. | |||
There was a problem hiding this comment.
| crypto | ||
| pthread |
There was a problem hiding this comment.
Instead of linking crypto and pthread directly, it is better practice to use find_package to locate these libraries. For example, use find_package(Threads REQUIRED) and link against Threads::Threads. For crypto, use find_package(OpenSSL REQUIRED) and link against OpenSSL::Crypto. This ensures that the correct include paths and linker flags are used across different platforms.
| heidi_engine/cpp/core/core.cpp | ||
| heidi_engine/cpp/core/clock.cpp | ||
| heidi_engine/cpp/core/config.cpp | ||
| heidi_engine/cpp/core/journal_writer.cpp | ||
| heidi_engine/cpp/core/run_id.cpp | ||
| heidi_engine/cpp/core/status_writer.cpp | ||
| heidi_engine/cpp/core/subprocess.cpp | ||
| heidi_engine/cpp/core/mock_provider.cpp | ||
| heidi_engine/cpp/core/async_collector.cpp | ||
| heidi_engine/cpp/core/manifest.cpp |
No description provided.