Keeping gradio from phoning home #9

New Issue

lightmare · 2023-02-07T21:22:44Z

lightmare commented

2023-02-07 21:22:44 +00:00

Gradio tries to call api.gradio.app during every startup.
This might be a potential fix.

Gradio tries to call `api.gradio.app` during every startup. [This](https://github.com/AUTOMATIC1111/stable-diffusion-webui/blob/c4b9ed1a2791e411f95a96a6324b4986b8b85b84/modules/ui.py#L51-L54) might be a potential fix.

mrq commented

2023-02-07 21:45:53 +00:00

Added in commit f03b6b8d97, courtesy of >>>/g/89228409

Added in commit f03b6b8d977b22e5747a81e58d31607dae4ffe9d, courtesy of [>>>/g/89228409](https://desuarchive.org/g/thread/89228054/#89228409)

lightmare commented

2023-02-07 22:33:22 +00:00

This patch doesn't really do anything on my end. Still seeing a call to gradio and a couple of lookups to huggingface.co (presumably for models, even though they are already cached).
I found analytics_enabled, but passing that here didn't do much either.

This patch doesn't really do anything on my end. Still seeing a call to gradio and a couple of lookups to huggingface.co (presumably for models, even though they are already cached). I found [`analytics_enabled`](https://www.gradio.app/docs/#blocks), but passing that [here](https://git.ecker.tech/mrq/tortoise-tts/src/commit/f03b6b8d977b22e5747a81e58d31607dae4ffe9d/app.py#L343) didn't do much either.

mrq commented

2023-02-09 02:01:07 +00:00

presumably for models

Indeed, I managed to catch a stack trace while trying to quickly kill it while working on something else, at /tortoise/utils/wav2vec_alignment.py#L56, which isn't really something I can nix checking for updates on initialization.

> presumably for models Indeed, I managed to catch a stack trace while trying to quickly kill it while working on something else, at [/tortoise/utils/wav2vec_alignment.py#L56](https://git.ecker.tech/mrq/tortoise-tts/src/branch/main/tortoise/utils/wav2vec_alignment.py#L56), which isn't really something I can nix checking for updates on initialization.

mrq commented

2023-02-09 22:08:50 +00:00

Added setting Only Load Models Locally to force all model loading to only load the model locally in commit 3621e16ef9.

This should nail out any other remaining network requests, but I can't be assed to validate it for sure.

Added setting `Only Load Models Locally` to force all model loading to only load the model locally in commit 3621e16ef906e2effd2fbef5900bfcbb50d2e62f. This should nail out any other remaining network requests, but I can't be assed to validate it for sure.

accountts commented

2023-02-27 01:02:34 +00:00

I'm still getting attempts at some outside connections

Exception in callback _ProactorBasePipeTransport._call_connection_lost(None)
handle: <Handle _ProactorBasePipeTransport._call_connection_lost(None)>
Traceback (most recent call last):
  File "[path]\python\lib\asyncio\events.py", line 80, in _run
    self._context.run(self._callback, *self._args)
  File "[path]\python\lib\asyncio\proactor_events.py", line 162, in _call_connection_lost
    self._sock.shutdown(socket.SHUT_RDWR)
ConnectionResetError: [WinError 10054]

Everything still works fine, just this stacktrace at each generation.

I'm still getting attempts at some outside connections ``` Exception in callback _ProactorBasePipeTransport._call_connection_lost(None) handle: <Handle _ProactorBasePipeTransport._call_connection_lost(None)> Traceback (most recent call last): File "[path]\python\lib\asyncio\events.py", line 80, in _run self._context.run(self._callback, *self._args) File "[path]\python\lib\asyncio\proactor_events.py", line 162, in _call_connection_lost self._sock.shutdown(socket.SHUT_RDWR) ConnectionResetError: [WinError 10054] ``` Everything still works fine, just this stacktrace at each generation.

Sign in to join this conversation.

No Label

No Milestone

No project

No Assignees

3 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: mrq/tortoise-tts#9