Closed ritfed-tabryg closed 3 years ago
~tadwyt-mormus replicated this bug, also with basehash u8adu ~debug/apps output: https://pastebin.com/aq22SN5h
~tadwyt-mormus here. I set that paste to expire after a day, so here it is for posterity.
~tacryt-socryp is taking a look at this now! — ~poldec-tonteg http://urbit.org
On Thu, Dec 17, 2020 at 7:55 AM Alan Liddell notifications@github.com wrote:
~tadwyt-mormus here. I set that paste to expire after a day, so here it is for posterity.
aq22SN5h.txt https://github.com/urbit/urbit/files/5709885/aq22SN5h.txt
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/urbit/urbit/issues/4172#issuecomment-747452943, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAMJBY4QPXVFATC4WUKGTIDSVIEVNANCNFSM4U5ATYCQ .
Someone on the urbit discord asked how to join a group from the command line. The intended command seems to be
:group-store|join ~bitbet-bolbel %urbit-community
, but this command doesn't work.To Reproduce In a ship's
dojo
, run the command:group-store|join ~bitbet-bolbel %urbit-community
(or replace the ship and group name with any other valid group).Expected behavior The ship joins the group. The new group is visible in landscape.
Unexpected result If the ship is already in the group, nothing happens:
I don't know if this is the intended result or not if the ship is already in the group. More importantly, if the ship is not already in the group, a stack trace is dumped:
Additional context This happens on planets and comets alike. My
+trouble
: