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

Default fetcher timeouts are too shprt #455

Open
timbl opened this issue Nov 6, 2020 · 2 comments
Open

Default fetcher timeouts are too shprt #455

timbl opened this issue Nov 6, 2020 · 2 comments

Comments

@timbl
Copy link
Member

timbl commented Nov 6, 2020

They are set to 30s by default.
Suggest 2 mins, os that if someone is on a flakey line they don't get a 'fetcher timed out' error when in fact if they had waited they would have got the data.
@timbl timbl mentioned this issue Nov 6, 2020
Open
@timbl
Copy link
Member Author

timbl commented Nov 6, 2020

See PR #454

@michielbdejong
Copy link
Collaborator

I think most responses that take more than 30s are themselves waiting for some timer to time out?

See also the contradictory situation here when for instance the rdflib code in NSS is trying to read in an external vcard group to decide on an ACL, https://gitter.im/solid/solidcommunity.net?at=5fa54c68c10273610aeca65a

Maybe making the default timeout shorter rather than longer would have the desired effect of making NSS faster?

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

No branches or pull requests
2 participants
@michielbdejong @timbl