[urbit] :talk %ap-fill-full

[c***@gmail.com]

Upon starting my planet today, urbit tried to sync the :talk log and hit a
bump. It was able to print a couple telegrams, but then hit 100% CPU and
hung for a while...before printing out
"[%ap-fill-full [~mossug-tasled %talk] ~doznec 72]" several hundred times
and hanging again. Pressing ^C emits a [%swim-take-vane %g %unto], and
pressing it again returns a several hundred line stacktrace looping line
1470 to 1468 for the next several interrupts. After spamming it a little
bit I was able to escape the :talk events, but attempting to send a message
just restarts the cycle :/

I think the %ap-fill-full is from sending messages to a full duct, which
isn't that abnormal. I've actually been getting that nearly everytime I
boot anyways, even before the launch, but it quickly cleared up and I never
had to try and abort events. I assume this time the chat backlog is too
large due to the whitepaper launch...

[c***@gmail.com]

Oh, also, the first time I booted it used 100% for a while after printing
%ap-fill-full and then crashed with a bail: meme out of loom. Which is bad.
Upon restarting it's just stuck at the current issue.

Post by c***@gmail.com
Upon starting my planet today, urbit tried to sync the :talk log and hit a
bump. It was able to print a couple telegrams, but then hit 100% CPU and
hung for a while...before printing out
"[%ap-fill-full [~mossug-tasled %talk] ~doznec 72]" several hundred times
and hanging again. Pressing ^C emits a [%swim-take-vane %g %unto], and
pressing it again returns a several hundred line stacktrace looping line
1470 to 1468 for the next several interrupts. After spamming it a little
bit I was able to escape the :talk events, but attempting to send a message
just restarts the cycle :/
I think the %ap-fill-full is from sending messages to a full duct, which
isn't that abnormal. I've actually been getting that nearly everytime I
boot anyways, even before the launch, but it quickly cleared up and I never
had to try and abort events. I assume this time the chat backlog is too
large due to the whitepaper launch...

[Philip Monk]

Hmm, %ap-fill-full definitely means that there's a full duct somewhere. It
sounds like maybe it's being auto-restarted, which would just cause the
problem again. Do you have webtalk open? If so, I would close that for a
bit until it works out all of its problems. Also, if you can run |reload
%f, that might help with possible memory issues.

Post by c***@gmail.com
Oh, also, the first time I booted it used 100% for a while after printing
%ap-fill-full and then crashed with a bail: meme out of loom. Which is bad.
Upon restarting it's just stuck at the current issue.

Post by c***@gmail.com
Upon starting my planet today, urbit tried to sync the :talk log and hit
a bump. It was able to print a couple telegrams, but then hit 100% CPU and
hung for a while...before printing out
"[%ap-fill-full [~mossug-tasled %talk] ~doznec 72]" several hundred times
and hanging again. Pressing ^C emits a [%swim-take-vane %g %unto], and
pressing it again returns a several hundred line stacktrace looping line
1470 to 1468 for the next several interrupts. After spamming it a little
bit I was able to escape the :talk events, but attempting to send a message
just restarts the cycle :/
I think the %ap-fill-full is from sending messages to a full duct, which
isn't that abnormal. I've actually been getting that nearly everytime I
boot anyways, even before the launch, but it quickly cleared up and I never
had to try and abort events. I assume this time the chat backlog is too
large due to the whitepaper launch...

--
You received this message because you are subscribed to the Google Groups "urbit" group.
To unsubscribe from this group and stop receiving emails from it, send an
For more options, visit https://groups.google.com/d/optout.

[Curtis Yarvin]

I'm trying to fix this garbage right now! Well, replace it anyway.

Sent from my iPhone

Hmm, %ap-fill-full definitely means that there's a full duct somewhere. It sounds like maybe it's being auto-restarted, which would just cause the problem again. Do you have webtalk open? If so, I would close that for a bit until it works out all of its problems. Also, if you can run |reload %f, that might help with possible memory issues.

Oh, also, the first time I booted it used 100% for a while after printing %ap-fill-full and then crashed with a bail: meme out of loom. Which is bad. Upon restarting it's just stuck at the current issue.

Upon starting my planet today, urbit tried to sync the :talk log and hit a bump. It was able to print a couple telegrams, but then hit 100% CPU and hung for a while...before printing out
"[%ap-fill-full [~mossug-tasled %talk] ~doznec 72]" several hundred times and hanging again. Pressing ^C emits a [%swim-take-vane %g %unto], and pressing it again returns a several hundred line stacktrace looping line 1470 to 1468 for the next several interrupts. After spamming it a little bit I was able to escape the :talk events, but attempting to send a message just restarts the cycle :/
I think the %ap-fill-full is from sending messages to a full duct, which isn't that abnormal. I've actually been getting that nearly everytime I boot anyways, even before the launch, but it quickly cleared up and I never had to try and abort events. I assume this time the chat backlog is too large due to the whitepaper launch...

--
You received this message because you are subscribed to the Google Groups "urbit" group.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "urbit" group.
For more options, visit https://groups.google.com/d/optout.

[c***@gmail.com]

Ok, so I managed to get it working again. Spammed interrupts, reconnected
to talk, rebooted the planet. The problem is that now it looks like ~doznec
is ignoring me - trying to send messages in :talk never echos, and running
`+ls /~doznec/home=` just camps forever, while doing the same command on
~zod works fine.
Might have screwed up %ames a little bit, and have to abandon ship...

Post by c***@gmail.com
Upon starting my planet today, urbit tried to sync the :talk log and hit a
bump. It was able to print a couple telegrams, but then hit 100% CPU and
hung for a while...before printing out
"[%ap-fill-full [~mossug-tasled %talk] ~doznec 72]" several hundred times
and hanging again. Pressing ^C emits a [%swim-take-vane %g %unto], and
pressing it again returns a several hundred line stacktrace looping line
1470 to 1468 for the next several interrupts. After spamming it a little
bit I was able to escape the :talk events, but attempting to send a message
just restarts the cycle :/
I think the %ap-fill-full is from sending messages to a full duct, which
isn't that abnormal. I've actually been getting that nearly everytime I
boot anyways, even before the launch, but it quickly cleared up and I never
had to try and abort events. I assume this time the chat backlog is too
large due to the whitepaper launch...