Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@tanema
Copy link
Contributor

@tanema tanema commented Dec 3, 2020

fixes #857

In previous work, I added in a bunch of arbitrary timeouts, this was because I wanted requests to fail faster if there was an issue. This however was misguided because the actual solution was cancelling the requests. The timeouts were also copied over from our webhook delivery service that I worked on and themekit and that service have vastly different request requirements. Webhook delivery requires fast completion on delivery, however themekit is used to uploading very large files that need more time to complete, so this was done in error.

I have just removed all of these timeouts as the defaults are either pretty large or no timeout is set at all. There is still a general overall request timeout so that does not mean requests will get stuck.

This fix has been confirmed in the issue linked

Warn Checklist

  • This changes the interface and requires a Major/Minor version change.
  • I have 🎩'd these changes by using the commands I changed by hand.
  • I have added a dependancy to the project.
  • I have considered any potential impact on node-themekit

@tanema tanema force-pushed the remove_arbitrary_timeouts branch from 0875e6b to 9cbdd69 Compare December 3, 2020 17:10
@tanema tanema force-pushed the remove_arbitrary_timeouts branch from 9cbdd69 to 7fd8d33 Compare December 3, 2020 17:15
@tanema tanema merged commit 4e9ac30 into master Dec 3, 2020
@tanema tanema deleted the remove_arbitrary_timeouts branch December 3, 2020 17:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Updating my app.js & app.css on theme watch/deploy supposedly fails, but reflects success on the actual storefront

1 participant