-
Notifications
You must be signed in to change notification settings - Fork 41
Support recording workflow running status #397
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
base: main
Are you sure you want to change the base?
Conversation
Summary of ChangesHello @pan-x-c, 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 significantly improves the observability and debugging capabilities of workflows by introducing a robust system for recording and monitoring their running status. It establishes a clear mechanism for workflows to report their internal state via 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. 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 pull request introduces a mechanism for recording and monitoring the running status of workflows. The overall implementation is good, but there are a few critical issues that need to be addressed. I've identified a busy-loop in the scheduler's monitoring task that could lead to high CPU usage, and several race conditions in the workflow runner when updating state, which could result in inconsistent state reads. Additionally, there's some unused code and a leftover print statement in a test. I've provided detailed comments and suggestions to resolve these issues.
|
/unittest-diff |
Summary
Failed Tests
Skipped
Tests
Github Test Reporter by CTRF 💚 |
|
/unittest-module-explorer |
Summary
Skipped
Tests
Github Test Reporter by CTRF 💚 |
|
/unittest-diff |
Summary
Skipped
Tests
Github Test Reporter by CTRF 💚 |
| dynamic_timeout: | ||
| enable: false | ||
| ratio: 3.0 | ||
| runner_state_report_interval: 0 |
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.
Minor comment: 默认是-1会不会好一些?
runner_state_report_interval=0可以误以为每隔0秒就report一次(i.e. 持续report)
Description
As the title says
Checklist
Please check the following items before code is ready to be reviewed.