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.

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

Make REQUEST_TIMEOUT user configurable #120

Closed
cd-rite opened this issue Jun 6, 2024 · 3 comments · Fixed by #123
Closed

Make REQUEST_TIMEOUT user configurable #120

cd-rite opened this issue Jun 6, 2024 · 3 comments · Fixed by #123
Labels
enhancement New feature or request

Comments

@cd-rite
Copy link
Collaborator

cd-rite commented Jun 6, 2024

Currently set in consts.js

@vogtjob
Copy link

vogtjob commented Jun 7, 2024

Hi. We're currently running the Windows executable of STIGMAN Watcher and are having an issue with a rather large collection that spawns the error "Timeout awaiting 'request' for 5000ms......"

I'm assuming this is what is being referenced here?

I was going to ask if there was an undocumented environment variable we could set, but it appears that will be in a later version.

Thanks!

@Matte22
Copy link
Collaborator

Matte22 commented Jun 7, 2024

We're aware of the api timeout error with large collections in STIGMAN Watcher. Our team is currently working on it. Keep an eye out for the update!

@csmig
Copy link
Member

csmig commented Jun 7, 2024

@vogtjob The timeout you're seeing is probably the result of Watcher over fetching from the API.

While determining which Assets in a batch of results need to be created, Watcher fetches a detailed list of all the Assets in a Collection. For the largest Collections, this list too big to be returned to Watcher before the default timeout expires.

In #123 we've put a band aid on the problem by increasing the default timeout and exposing it via an envvar. The problem will be more fully addressed by #124 which will refactor the code that is over fetching to be more efficient.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development

Successfully merging a pull request may close this issue.

4 participants