Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Telemetry request has no configured timeout #3791

Open
Rojuinex opened this issue Nov 21, 2024 · 0 comments · May be fixed by #3792
Open

Telemetry request has no configured timeout #3791

Rojuinex opened this issue Nov 21, 2024 · 0 comments · May be fixed by #3792

Comments

@Rojuinex
Copy link

The requests in scarf_analytics have no timeout set, which can cause an application using the unstructured client to hang.

https://github.com/Unstructured-IO/unstructured/blob/3b9b01c502cf5f319fd8bb2427232af96af5c637/unstructured/utils.py#L281C1-L309C18

Right now the only work around is to set SCARF_NO_ANALYTICS or DO_NOT_TRACK, but that opts out of analytics completely. A better approach is to set the timeout parameter to a reasonable value to avoid deadlocking the application.
@Rojuinex Rojuinex linked a pull request Nov 21, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add timeout to scarf telemetry requests Rojuinex/unstructured
1 participant
@Rojuinex