-
Notifications
You must be signed in to change notification settings - Fork 57
Comet %hall hang #576
Comments
Looks like it's trying to fetch all messages from ~marzod's urbit-meta. That's a lot of messages, and apparently too many for it to process. It shouldn't be trying to fetch them all if it was running the latest talk version, but I'm guessing it isn't? |
Hmm, it definitely should be. It is a comet I started on 30th of december, never had a problem until yesterday. How can I verify if it runs a new talk? |
Hmm yeah, a fix for the behavior I described got merged on December 14th. You can check by diffing the files in your comet's base desk against those from the repo. Did you ever ;join urbit-meta on this comet? Was it just (Also, it might eventually resolve if you just let it spin for a long time.) |
Okay, so first I will let it spin. I did join urbit-meta on ~binzod. |
Ok, so it turns out it was trying to pull all of messages despite me being never subscribed to ~marzod/urbit-meta. The cause was webtalk actually, which according to ~palfun does not have this precaution build in. |
The comet I have been using to develop on suddenly started to hang.
Every time I boot it up, after some time %ames spinner shows up and spins indefinitely.
When interrupted, it dumps the following:
Eventually dump stops, and I can use the comet. But after some time the same situation occurs, and so on.
The text was updated successfully, but these errors were encountered: