You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe it's related to the event loop once many different things are happening on it. One millisecond in setTimeout doesn't guarantee one actual millisecond, quite far from it. This means that fetch can resolve sooner than the abort signal is dispatched.
There's nothing we can do here as long as fetch itself doesn't allow us to meddle with its intrinsic timeout mechanism.
If we want to guarantee that a timeout will successfully occur, we need to mock fetch and make it wait for the abort signal indefinitely.
Description
The following test is failing:
Screenshots or Logs
https://github.com/meilisearch/meilisearch-js/actions/runs/14459420962/job/40549120917
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: