Skip to content

callWithRetry updates, add back node-fetch polyfill due to unsolved SocketClosed error#388

Merged
twelch merged 11 commits intodevfrom
callWithRetry-fixes
Dec 18, 2024
Merged

callWithRetry updates, add back node-fetch polyfill due to unsolved SocketClosed error#388
twelch merged 11 commits intodevfrom
callWithRetry-fixes

Conversation

@twelch
Copy link
Copy Markdown
Contributor

@twelch twelch commented Dec 14, 2024

  • callWithRetry
    • add optional ifErrorMsgContains string, will now retry unless error message contains that string.
    • add exponential backoff so that there is a an increasing wait before the next retry.
  • rasterStats will now catch geoblaze vrm error when passing zeroSketch, and return rasterStat default values in that case, rethrow all other errors.
  • add back node-fetch polyfill to cog and flatgeobuf to solve SocketError showing up during high volume network call situation (e.g. smoke tests).

…rs unless error message contains that string
…instead of rethrow, to better understand the errors
* polyfill with node-fetch in cog and flatgeobuf
* simplify rasterStats caught error log, callWithRetry - add exponential backoff and up maxRetry to 4
…ow rest (#391)

reduce retries to 3 and quicken retry rate, catch vrm error and rethrow rest
@twelch twelch changed the title callWithRetry updates callWithRetry updates, add back node-fetch polyfill due to unsolved SocketClosed error Dec 18, 2024
@twelch twelch merged commit a4b6aa0 into dev Dec 18, 2024
@twelch twelch deleted the callWithRetry-fixes branch December 18, 2024 02:18
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.

1 participant