-
Notifications
You must be signed in to change notification settings - Fork 437
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
Not being notified when N+1 is detected in turbo frame or turbo stream #724
Comments
@tpaulshippy bullet frontend notification only works in html response, turbo doesn't provide any means to execute JS |
The funny thing about that statement is that turbo is written in javascript. 😁 But yeah I get it that there is not an easy solution here. Even if it was just intercepting the request and returning "Content missing" like rails does with a lot of turbo issues, that would be better. I'm not sure why bullet couldn't stream back the warning through turbo. Or provide a turbo client side event hook that detects something in the response and does the |
@tpaulshippy bullet injects the html response in |
Great. I'll start there. Thanks. |
Code in this branch seems to be working. Decided to just timebox it and got it done. |
I'm not sure if this belongs as an issue in https://github.com/flyerhzm/uniform_notifier or here.
Our team makes heavy use of Turbo in our applications. We have been dealing with a lot of N+1 issues that Sentry is able to detect but Bullet is not always alerting us to them at development time. One of the reasons we have noticed is that Bullet will not notify us when there is an issue with a request that is either streamed back via turbo stream or just on a navigation that is shown in a turbo frame.
I have created a branch in my playground app to illustrate the issue.
Despite having the following in my development.rb --
I am not seeing any indication that there is an issue unless I examine my server logs in my terminal.
This commit shows the issue with streams.
And this commit shows the issue with frames.
Here is a screen recording of the issue --
bullet-turbo-issue-smaller.mov
The only "workaround" for this is:
The text was updated successfully, but these errors were encountered: