Disable Gradio Analytics #1165
Merged
Disable Gradio Analytics #1165
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
Gradio analytics can be disabled by either using the kwargs `enable_analytics` on `gr.Blocks`, or by setting the env variable `GRADIO_ANALYTICS_ENABLED` to something different from `True`. Since that Gradio does not seem to respect their code contract (around `enable_analytics`), and that they are performing other operations only based on the value of `GRADIO_ANALYTICS_ENABLED` (c.f. `gradio.strings` https://github.com/gradio-app/gradio/blob/main/gradio/strings.py#L39), we are disabling gradio analytics by setting the required env variable to `False`. Note: Setting an environment variables using `os.environ['foo'] = 'bar'` on system that are not based on unix might not work. c.f. https://docs.python.org/3/library/os.html#os.environ for details on how `os.environ` works and all its caveats
|
After this change, there will be absolutely no HTTP call made to gradio API, cleaning the |
imartinez
previously approved these changes
Nov 6, 2023
lopagela
commented
Nov 6, 2023
imartinez
approved these changes
Nov 6, 2023
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.
Gradio analytics can be disabled by either using the kwargs
enable_analyticsongr.Blocks, or by setting the env variableGRADIO_ANALYTICS_ENABLEDto something different fromTrue.Since that Gradio does not seem to respect their code contract (around
enable_analytics), and that they are performing other operations only based on the value ofGRADIO_ANALYTICS_ENABLED(c.f.gradio.stringshttps://github.com/gradio-app/gradio/blob/main/gradio/strings.py#L39), we are disabling gradio analytics by setting the required env variable toFalse.Note: Setting an environment variables using
os.environ['foo'] = 'bar'on system that are not based on unix might not work.c.f. https://docs.python.org/3/library/os.html#os.environ for details on how
os.environworks and all its caveatsSee #1144 for the similar PR on chromaDB telemetry (that motivated this PR)