- 
          
 - 
                Notifications
    
You must be signed in to change notification settings  - Fork 11k
 
[Misc] Update guided decoding logs to debug #15310
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
| 
           👋 Hi! Thank you for contributing to the vLLM project. 💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels. Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run  Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging. To run CI, PR reviewers can either: Add  🚀  | 
    
feff087    to
    fb2f0c3      
    Compare
  
    | 
           Should we just revert this to debug? Would rather not make these functions have more options if we can avoid it  | 
    
| 
           +1 with rob, let's just make it   | 
    
Guided decoding json schema contains potentially sensitive user inputs. Do not log user inputs on INFO while ignoring `disable_log_requests=True`. Signed-off-by: Benjamin Merkel <benjamin.merkel@tngtech.com>
fb2f0c3    to
    10b2bf1      
    Compare
  
    | 
           Okay, then let's keep things simple and just revert the logs to debug.  | 
    
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.
Can you also update the title to "[Misc] Update guided decoding logs to debug"
Thanks
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
| 
           Thank you all!  | 
    
Signed-off-by: Benjamin Merkel <benjamin.merkel@tngtech.com> Co-authored-by: Benjamin Merkel <benjamin.merkel@tngtech.com>
Signed-off-by: Benjamin Merkel <benjamin.merkel@tngtech.com> Co-authored-by: Benjamin Merkel <benjamin.merkel@tngtech.com> Signed-off-by: Wes Medford <wryanmedford@gmail.com>
Signed-off-by: Benjamin Merkel <benjamin.merkel@tngtech.com> Co-authored-by: Benjamin Merkel <benjamin.merkel@tngtech.com> Signed-off-by: Louis Ulmer <ulmerlouis@gmail.com>
Signed-off-by: Benjamin Merkel <benjamin.merkel@tngtech.com> Co-authored-by: Benjamin Merkel <benjamin.merkel@tngtech.com>
Signed-off-by: Benjamin Merkel <benjamin.merkel@tngtech.com> Co-authored-by: Benjamin Merkel <benjamin.merkel@tngtech.com>
Signed-off-by: Benjamin Merkel <benjamin.merkel@tngtech.com> Co-authored-by: Benjamin Merkel <benjamin.merkel@tngtech.com> Signed-off-by: Mu Huai <tianbowen.tbw@antgroup.com>
The json schema as part of guided decoding details can contain sensitive user inputs. I believe user inputs should not be logged when the engine is started with
disable_log_requests=True.These logs have existed for a while at DEBUG level but only made visible at INFO level with v0.8.0 (#12955). I would be fine with reverting the relevant line's log level back to DEBUG instead of my proposed change.