-
Notifications
You must be signed in to change notification settings - Fork 425
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Two refreshes causes exception: The operation was aborted. #1091
Comments
🤯 So it seems MiniProfiler is monkey patching After disabling MiniProfiler, the error disappears. So this is not an issue with Turbo. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Running
8.0.0-beta.1
, testing in Firefox 118.We have a page which is subscribed to two types of streams:
When a child changes, it touches the parent. Therefore two refresh actions are sent shortly after each other, refreshing the same page. This causes the second request to cancel the first one. This raises an exception:
The exception causes the whole page to be refreshed by the browser instead of in a
fetch
request.There are two things that might be a bug here:
Turbo.current_request_id
, which is used in the debouncer. So I really get to refreshes closely after each other. But given there are two streams, they still both should update. In production we do a lot of data handling with jobs (Sidekiq) and you also don't get aTurbo.current_request_id
, so the debouncer might not work as expected.The text was updated successfully, but these errors were encountered: