-
Notifications
You must be signed in to change notification settings - Fork 16
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
Liveview 0.18.0? #18
Comments
@TheFirstAvenger is this resolved yet? |
I've been working on it this week. I've got it upgraded locally, but I ran into some issues that I am still working through. I hope to have it done tomorrow or early next week. |
@aselder I have a branch with 0.18, would you have time to try it out and let me know if you run into any issues?
|
@TheFirstAvenger I'll try to give it a shot tomorrow. |
@TheFirstAvenger I downloaded and gave it a shot. It works on really simple pages, for instance a static asset being served by Plug.Static. However, once I get to anymore complicated pages, I'm getting GenServer time outs in the |
It looks like we're blowing out the MessageQ of the capture server :) Then eventually cowboy terminates the connection and kills everything.
|
@aselder Thanks for the update. Yes, I did see that crash last week, but then it seemed to not happen any more this week. I feel like there is a deadlock happening which is why the |
@aselder I have a branch that reworks the trace issue, but as you pointed out the root cause is the message Q being overloaded. I enabled debug and it looks like it is spinning its wheels inside
Continuing to investigate. |
Confirmed that this also happens with Jason v1.2. |
Interesting. Reverting back to |
I was able to reproduce the issue with OTP 23. So far I am not able to find a combination that doesn't trigger this. Ideally I would like to test this issue on a project with the main branch of Flame On (0.5.2) after reproducing it with that same project running this liveview branch. That would tell us if the issue is this branch or if this was an always-existing thing. The problem is that I can't run 0.5.2 on any of my current projects as they are already LiveView 0.18. I think what I am going to do at this point is merge this PR and the other two into main, and start then work on digging into the specific issue moving forward, since trying to determine if/when it started isn't proving fruitful. |
I have opened #26 to track the overloading issue. Note that #24 changes the initial failure we were seeing from a 5 second GenServer timeout to a hanging no response scenario, which is a worse user experience, but will help us diagnose and resolve this issue. I am not planning on publishing a new version of Flame On till we resolve this issue. |
Any chance this can be updated to support Liveview 0.18.0?
The text was updated successfully, but these errors were encountered: