:talk on a moon about arvo

[galenwp]

Hm. Having shut that moon down for a day I restarted it to test something and get:

[ ! 
    \/gall: %hood: diff: no /talk-report/drum/phat/~bottus-macped-talsur-todre\/
      s/talk
    \/                                                                        \/
  [%ap-lame %hood %diff]
]
[ ! 
    \/gall: %hood: diff: no /talk-report/drum/phat/~bottus-macped-talsur-todre\/
      s/talk
    \/                                                                        \/
  [%ap-lame %hood %diff]
]
[ ! 
    \/gall: %hood: diff: no /talk-report/drum/phat/~bottus-macped-talsur-todre\/
      s/talk
    \/                                                                        \/
  [%ap-lame %hood %diff]
]
[ ! 
    \/gall: %hood: diff: no /talk-report/drum/phat/~bottus-macped-talsur-todre\/
      s/talk
    \/                                                                        \/
  [%ap-lame %hood %diff]
]
[ ! 
    \/gall: %hood: diff: no /talk-report/drum/phat/~bottus-macped-talsur-todre\/
      s/talk
    \/                                                                        \/
  [%ap-lame %hood %diff]
]
[ ! 
    \/gall: %hood: diff: no /talk-report/drum/phat/~bottus-macped-talsur-todre\/
      s/talk

Basically forever.

[ponnys-podfer]

:talk is also getting unlinked for me on moon creation after the last breach.

From the moon:

[~widmev-bacdev-ponnys-podfer, driving ~widmev-bacdev-ponnys-podfer]
activated app home/dojo
[linked to [p=~widmev-bacdev-ponnys-podfer q=%dojo]]
sync succeeded from %kids on ~ponnys-podfer to %base
[unlinked from [p=~ponnys-podfer q=%talk]]
/~ponnys-podfer/home/0/app/talk:<[2.194 3].[2.202 40]>
/~ponnys-podfer/home/0/app/talk:<[2.195 3].[2.202 40]>
/~ponnys-podfer/home/0/app/talk:<[2.197 3].[2.202 40]>
/~ponnys-podfer/home/0/app/talk:<[2.198 5].[2.200 42]>
mack

On the planet which issued the moon:

[%peer-talk-stranger ~widmev-bacdev-ponnys-podfer]

I've done this twice now and I still don't have a moon with a linked talk

[juped]

I was under the impression that a recent patch (the one with ++team) fixed this, but it seems not.

[juped]

The relevant line (and a longtime thorn in my side) being

~?  !=(src.hid our.hid)  [%peer-talk-stranger src.hid]

which prevents any other ships from subscribing to a ship's talk console, when it should prevent any other ships besides its moons.

[cgyarvin]

Well, that's just the printf, but yes. Seems like an easy fix...

On Tue, Aug 16, 2016 at 11:28 PM, Raymond Pasco [email protected]
wrote:

The relevant line (and a longtime thorn in my side) being

~? !=(src.hid our.hid) [%peer-talk-stranger src.hid]

which prevents any other ships from subscribing to a ship's talk console,
when it should prevent any other ships besides its moons.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#26 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AALyATujILLMpwNO2er8_pGyMvmaPnX1ks5qgn_7gaJpZM4HiPks
.

[joemfb]

I think it's actually explicit in drum: https://github.com/urbit/arvo/blob/master/lib/drum.hoon#L81. I've been meaning to investigate further and open a PR ...

While I'm looking at ++deft-apes, any particular reason for comets to start :talk and :dojo out of %base instead of %home?

[joemfb]

That comment is mostly incoherent -- I guess that's what happens after a vacation ...

I just tested a new moon, the problem is indeed ?> =(our.hid src.hid) at https://github.com/urbit/arvo/blob/master/app/talk.hoon#L2198