-
Notifications
You must be signed in to change notification settings - Fork 188
Rename DEBUG input to GEMINI_DEBUG and pass --debug flag to CLI.
#407
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
54441e5 to
2e8f0ea
Compare
|
/gemini review |
|
@gemini-cli /review |
1 similar comment
|
@gemini-cli /review |
|
🤖 Hi @MJjainam, I've received your request, and I'm working on it now! You can track my progress in the logs for more details. |
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.
This pull request renames the DEBUG input to GEMINI_DEBUG to avoid conflicts with the Node.js debugger and updates the debug logging mechanism. The changes are generally good, but there are a few important issues to address, including a security policy violation and the use of an unreliable sleep command.
🔍 General Feedback
- The changes to
README.mdare clear and effectively warn users about the previous issues with theDEBUGvariable. - The move to
GEMINI_DEBUGis a good improvement to avoid environment variable collisions.
|
Should we update all the vars.DEBUG variable to vars.GEMINI_DEBUG ? |
Updated all the references |
related to #337
Env variable DEBUG is used in CONTRIBUTING.md?plain=1#L356
Setting this to true will start gemini in inspect-brk mode which will wait for node debugger to attach indefinitely. resulting in looks like freeze.
so i have removed the support of the env variable and added warning to users to notify it side effects.