Link issues together to show that they're related. Learn more.
Activity
- Owner
@MattJ Could you give a look here, please? What does those timeout could mean?
@alexbourlier aren't we in a case where trying to estimate is already almost doing the work?
- Author Maintainer
@rachel I couldn't tell... :-)
- Please register or sign in to reply
- Developer
The timeout one is about trying to fetch my vCard. It's possible (even probable) that this is being blocked because nobody on the startinblox server is in my contact list, and I have some rules that ignore/reject traffic from unknown senders.
I'd hope that the app is not blocked by vCard requests anyway, so I don't think this is the issue.
The other one may be a problem, it's processing the list of rooms the user is member of (remember that userRooms promise you set up for me?). Looks like that list contained an invalid JID perhaps? (or null or something), and then it failed to parse it.
- Owner
You mean that the 5+1+1 timeouts after yours are related to an error on this object, right?
Edited by Jean-Baptiste Pasquier - Developer
Oh, I didn't see all those ones the first time around.
My guess is that something is blocking Converse.js (for >10s), or that the uncaught exception interrupted something important (such as actually sending the requests that timed out).
I'd focus on fixing the obvious and easy issue (the null dereference) and see if that solves it.
- Author Maintainer
Sounds like a plan
- Owner
@MattJ I let you estimate both of them, time & exp. delivery date, added a line on the management sheet for this issue. You can consider the null dereference as funded.
- Jean-Baptiste Pasquier assigned to @MattJ
assigned to @MattJ
- Author Maintainer
This is the most painful issue at the moment. I upgrade it to s1 at the app is not usable at the moment.
- Developer
Estimating up to 2h to investigate and fix, assuming my diagnosis is correct. I also need an environment where this can be reproduced.
- Author Maintainer
@MattJ Can't you reproduce it on the staging platforms?
@alexbourlier FYI on my side, this is not reproductible on stagings. It would require stagings with lots of data... and even though... I'm not reproducing it in production either :/
- Author Maintainer
@rachel OK.
I can share my credentials on the production platform with anyone, so you can at least see the issue and dig where you wish.
- Developer
We're in the middle of moving the staging sites over to the new Prosody server, and my accounts there aren't working anyway, so... no, not right now :)
- Author Maintainer
Roger that.
- Alex changed title from App freeze when I start it now to App freeze
changed title from App freeze when I start it now to App freeze
- Author Maintainer
@jbpasquier I got the first 4 lines of these logs before a big freeze. The rest got spit out one the ~1 min freeze was over.
- Owner
A timeout to your inbox and to few other urls like user avatars. Disconnection related?
About other errors:
- the vcard timeout have been expelled from this freeze issue
- I've asked Xavi about the scrollTop one, probably unrelated, but need a fix
- 404 on Berengere, we need to find which circle have her on its members, as the user does not exist anymore and remove her. ActivityQueue is coming and may help to spot future cases like that
- Matthieu is investigating on the DOMException on his side (Not shown on your capture)
- Author Maintainer
I can't tell regarding the timeout on the inbox, but I can investigate if you want.
- Jean-Baptiste Pasquier mentioned in issue components/solid-xmpp-chat#192
mentioned in issue components/solid-xmpp-chat#192
- Owner
Closing, most freeze issues are solved.
Opened components/solid-xmpp-chat#192 & components/solid-xmpp-chat#193 (closed) about errors issues.
- Author Maintainer
Very cool
- Jean-Baptiste Pasquier closed
closed