Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
`timeout` option set on viewer does not seem to have an effect
See original GitHub issueI passed a timeout: 10, expecting timeout errors, but didn’t get any. Confirmed in chrome dev tools that tiles fetched were not being fetched from cache, and did take more than 10ms to fetch.
Setting OpenSeadragon.DEFAULT_SETTINGS.timeout = 10; did trigger the timeouts I expected. So that global setting does work to override timeout. But passing timeout as option to Openseadragon() viewer creation does not seem to.
Have not yet tried to trace the code to figure out what’s going on.
One thing that would make things more transparent is if the timeout errors printed to console also included the timeout value, so you at least knew what timeout value it was working with. Probably useful for debugging even if this is fixed.
Issue Analytics
- State:
- Created 6 years ago
- Comments:10 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Looking at the date that this issue was filed (Aug. 3, 2017), you must have been using no later than the 0.3.3 rubygem, so the OSD in question is 2.2.1 or earlier (before #1192).
Based on that, and your report of the behavior of
test-certainandtest-unlikely, I’m confident this can be closed.Awesome… Thank you for following up on this!