-
Notifications
You must be signed in to change notification settings - Fork 38
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
Cleanup: Remove the ai-logs flag. #679
Conversation
You doing push & pray over there 😆, @jlewi? |
You caught me. |
Lets try this again. I fixed the build.
Lint gives me errors when running locally. But errors seem unrelated to any files I modified.
Also seeing some test failures locally.
Looks in CI there is a test timeout now. Are tests known to be flaky? |
* This flag is deprecated and no longer used. * The frontend should have stopped using this flag starting in 3.7.5 * The frontend is now up to 3.8.5 * So we should be good to remove this flag because the frontend should no longer be setting it. * Related to jlewi/foyle#211
e50ed70
to
7ef34a6
Compare
Quality Gate passedIssues Measures |
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.
✅ LGTM. I have an eye on the flakes. I made them more stable on Linux but they still only seem to flake in GHA :-/.
This flag is deprecated and no longer used.
The frontend should have stopped using this flag starting in 3.7.5
The frontend is now up to 3.8.5
So we should be good to remove this flag because the frontend should no longer be setting it.
Related to Move AI Logging Of Execution Into VSCode Frontend and out of RunMe GRPC Server jlewi/foyle#211