Strange phenomenon: Subsequent methods or subs won't succeed

[afrokick]

lets move live idea info Slack #lives cannel )

[waldgeist]

@afrokick

If anyone interesting in this topic, i can do a live to talk

Definitely, count me in.

[waldgeist]

That looks interesting. Will have a deeper look at it!

[waldgeist]

Seems like we have another case that looks very similar to the original phenomenon mentioned in this thread:

Meteor loggingIn stuck on true even though user is logged in

Hi everyone, seeing this weird issue on a new Galaxy deployment of a working codebase. Meteor.loggingIn() is stuck on true, but Accounts.onLogin callback is executing, Meteor.user() is defined. Meteor.logout() has no effect, user remains even after reloading the page. Meteor.status() says connected I looked at the raw messages in the websocket and everything looks normal: Client calls connect, calls login with resume token, and subs to loginServiceConfiguration and autoupdate client versions …

[mozibrand]

Hi, out in the end, have you worked out the problem, I want to know any reason, as long as it is able to solve, this is the original main cause I left the pub/sub, and I now use the Apollo of non real-time response to data docking, if you have experience, give me a more detailed talk about, I might try again using the pub/sub

[waldgeist]

This problem is not directly related to pub/sub, it also affects methods.

[mozibrand]

So how did you solve it in the end, I want to learn

[waldgeist]

I don’t have a solution yet. I added this.unblock() to all methods (except those that delete data), and now I am waiting if this helped or not. Which is hard to tell, because the problem only appeared after weeks of normal operation.

[mozibrand]

I look forward to the message again.

[drone1]

Any updates on resolving this?

I’m encountering a similar issue with Galaxy where I make a simple Meteor.call() and the callback is never triggered, despite confirmation that the result is reaching the client (I can see it in Meteor DevTools Evolved DDP tab). It happens after the server’s been up for a few days or so.

Never happens on dev.

I’m going to deploy my app now with a unhandledRejection handler to see if I catch anything funky.

Would love any tips if anyone’s learned anything since Feb 2021

I’m running Meteor 2.14, with latest packages and npm packages. I’m using Atlas for DB with an oplog.