chore: Disable analytics in Gradio interface #694
Merged
+1
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit disables the analytics feature in the Gradio interface within the `s_command.py` file. Disabling analytics can help maintain user privacy and align with data protection policies or organizational guidelines. The change involves adding the `analytics_enabled=False` parameter to the `gr.Interface` constructor, ensuring that no usage data is collected from users interacting with the application.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit disables the analytics feature in the Gradio interface within the
s_command.pyfile. Disabling analytics can help maintain user privacy and align with data protection policies or organizational guidelines. The change involves adding theanalytics_enabled=Falseparameter to thegr.Interfaceconstructor, ensuring that no usage data is collected from users interacting with the application.Presently, the environment is the only way to disable it. Something like: