feat: abort controller

[kwasniew]

About the changes

Abort controller that aborts previous request when a new one is made.

Sample use cases:

• slow network + multiple consecutive updateContext calls
• slow network + very short interval

Important files

Discussion points

[nammi-kobler]

I keep getting these:

the requests comes in pairs (within 2 seconds), and if I upgrade to v3.3.0 I get these every other request (so one is always cached and the other has this error in the console:

downgrading to 3.2.0 fixes these for me.

this is what Stack Overflow tells me about the NS_BINDING_ABORTED ones: https://stackoverflow.com/questions/704561/ns-binding-aborted-shown-in-firefox-with-httpfox

[nammi-kobler]

error message in Chromium:

Safari:

[kwasniew]

@nammi-kobler those errors are expected when the requests are aborted e,g, when you're on a slow network and you have very short refreshInterval and the original request hasn't finished and you start the next one. From what I understand your refresh interval is 2s. Can you increase it and see if the problem persists? The abort operation should be an exception not a regular operation.

[nammi-kobler]

The refresh interval is set to 15s, but for some reason they always come in pairs (every 15 sec), and then one of them always fails. any idea on why they would come in pairs?

[kwasniew]

@nammi-kobler Can you check if this PR https://github.com/Unleash/unleash-proxy-client-js/pull/207 fixes your issue? It's applied in the https://github.com/Unleash/unleash-proxy-client-js/releases/tag/v3.4.0 release

[nammi-kobler]

@nammi-kobler Can you check if this PR #207 fixes your issue? It's applied in the https://github.com/Unleash/unleash-proxy-client-js/releases/tag/v3.4.0 release

Thanks for this! Firefox:

Vivaldi:

Safari:

Looks better, but it seems like it still happens over time

[kwasniew]

@nammi-kobler Thanks for checking. So is it correct that the console.error is gone and now you're only left with the double request problem? Can you remind me if you use unleash-proxy-client-js directly or through react or nextjs wrapper? I couldn't reproduce this problem in this vanilla client so my guess is it's some wrapper adding those extra calls.

[nammi-kobler]

@nammi-kobler Thanks for checking. So is it correct that the console.error is gone and now you're only left with the double request problem? Can you remind me if you use unleash-proxy-client-js directly or through react or nextjs wrapper? I couldn't reproduce this problem in this vanilla client so my guess is it's some wrapper adding those extra calls.

we are using unleash-proxy-client

NextJS warning is from a wrapper that comes with Mantine I think?

[kwasniew]

Are you running in Strict Mode by any chance? https://react.dev/reference/react/StrictMode It runs code twice in development.

[nammi-kobler]

Are you running in Strict Mode by any chance? https://react.dev/reference/react/StrictMode It runs code twice in development.

haha yes. that's maybe the answer then.