crude:punted during clay sync with bunted date

[joshuareagan]

Booted ~taglux-nidsep and joined the help channel. Then I got this, shortly after an attempted sync:

; ~zod not responding still trying
; ~zod is ok
; ~binzod not responding still trying
; ~binzod is ok
beginning sync from %kids on ~binzod to %base
; ~binzod not responding still trying
~poldec-tonteg> you mean not used or not valid?
; ~binzod is ok
~palfun-foslup> currently nobody/no code cares though, and i really wouldn't
                worry about it
[%fail-ack 0]
crude: all delivery failed!
event: hear
  %failed-jack
  [%failed-take %c]
  [ %failed-swim
    %c
    %f
    [~ u=/foreign-plops/~taglux-nidsep/~binzod/kids/~2000.1.1]
  ]
  [%swim-take-vane %c %made]
  [%failed-slym-in %c]
  /~zod/home/~2019.1.18..01.05.15..f066/sys/hoon:<[17.106 5].[17.107 36]>
  /~zod/home/~2019.1.18..01.05.15..f066/sys/hoon:<[17.107 5].[17.107 36]>
  /~zod/home/~2019.1.18..01.05.15..f066/sys/hoon:<[17.094 5].[17.096 37]>
  /~zod/home/~2019.1.18..01.05.15..f066/sys/hoon:<[17.095 5].[17.096 37]>
  /~zod/home/~2019.1.18..01.05.15..f066/sys/hoon:<[17.096 5].[17.096 37]>
  /~zod/home/~2019.1.18..01.05.15..f066/sys/hoon:<[17.096 6].[17.096 29]>
  /~zod/home/~2019.1.18..01.05.15..f066/sys/hoon:<[17.096 13].[17.096 28]>
  "validate foreign plops failed"
  \/%path: no matches for /~taglux-nidsep/home/~2019.1.17..22.19.17..5a1a/mar/\/
    txt-diff/hoon
  \/                                                                          \/
  ford: %vale failed while searching for %txt-diff:
  %ford-fail
crude: punted

The only possibly dubious thing I can think I did was run a bit of nock in the chat:

.*([8 7] [8 [[1 0] [[1 0] [1 0]]] [8 [1 [6 [5 [0 15] [0 27]] [0 12] [9 5 [[0 2] [[[0 12] [[0 26] [4 [0 27]]]] [0 7]]]]] [6 [5 [0 14] [0 26]] [9 4 [[0 2] [[[0 12] [[1 0] [0 27]]] [0 7]]]] [9 5 [[0 2] [[[4 [0 12]] [[4 [0 26]] [0 27]]] [0 7]]]]]] [9 4 [0 1]]]])

[joshuareagan]

Update:

I should add that I can still use talk from ~taglux, but naturally the ota update didn't go through. This morning I'm now seeing a new series of messages:

~dirwex-dosrev> ~racwyl-padfes, i'm also seeing the last line being cut off by
                the text entry box
proxy: write downstream: operation canceled
proxy: write downstream: operation canceled
proxy: write downstream: operation canceled
proxy: write downstream: operation canceled
proxy: write downstream: operation canceled
proxy: write downstream: operation canceled
proxy: write downstream: operation canceled
proxy: write downstream: operation canceled
proxy: write downstream: operation canceled
proxy: write downstream: operation canceled
proxy: write downstream: operation canceled
proxy: write downstream: operation canceled
proxy: write downstream: operation canceled
proxy: write downstream: operation canceled
proxy: write downstream: operation canceled
proxy: write downstream: operation canceled
~taglux-nidsep> test
~taglux-nidsep:talk> 

[eglaysher]

I also got a crude:punted with the same backtrace when I booted up a moon under my planet.

[joemfb]

@eglaysher, did your backtrace also include the ~2000.1.1 date in the foreign-plops wire? That date is used for the +load and +stay calls that arvo makes to vanes, but shouldn't be used for anything else. Maybe it's being improperly cached and not replaced with the actual date?

@joshuareagan, I'd advise ignoring the proxy: printfs. Right now, it prints an "error" message for any TCP stream that isn't closed with EOF, but that's just too common an occurrence to print every time.

[eglaysher]

Yes, the wire also had a ~2000.1.1 date.

[joemfb]

I had thought that this issue was likely caused by a stale sample in Arvo's vane caches, but my reasoning was based on stale facts. @da used to bunt to 0, like so:

> `@da`0
~292277024401-.1.1

But, with the advent of the new +spec structures and their engine +ax, we now have aura-specific defaults:

> *@da
~2000.1.1

%clay bunts dates all over the place, so I have zero insight into what might be causing this.

[eglaysher]

FYI, I got this again on the latest ames hotfix push. Here's the longer stack trace now that we're !: in more places:

crude: all delivery failed!
event: hear
  %failed-jack
  [%failed-take %c]
  [ %failed-swim
    %c
    %f
    [~ u=/foreign-plops/~ponnys-podfer/~binzod/kids/~2000.1.1]
  ]
  [%swim-take-vane %c %made]
  [%failed-slym-in %c]
  /~zod/home/~2019.2.14..21.50.56..4e2e/sys/vane/clay:<[3.983 3].[4.145 5]>
  /~zod/home/~2019.2.14..21.50.56..4e2e/sys/vane/clay:<[3.984 3].[4.145 5]>
  /~zod/home/~2019.2.14..21.50.56..4e2e/sys/vane/clay:<[3.998 3].[4.145 5]>
  /~zod/home/~2019.2.14..21.50.56..4e2e/sys/vane/clay:<[4.012 3].[4.145 5]>
  /~zod/home/~2019.2.14..21.50.56..4e2e/sys/vane/clay:<[4.018 5].[4.096 7]>
  /~zod/home/~2019.2.14..21.50.56..4e2e/sys/vane/clay:<[4.019 5].[4.096 7]>
  /~zod/home/~2019.2.14..21.50.56..4e2e/sys/vane/clay:<[4.073 7].[4.080 17]>
  /~zod/home/~2019.2.14..21.50.56..4e2e/sys/vane/clay:<[4.074 7].[4.080 17]>
  /~zod/home/~2019.2.14..21.50.56..4e2e/sys/vane/clay:<[4.075 7].[4.080 17]>
  /~zod/home/~2019.2.14..21.50.56..4e2e/sys/vane/clay:<[4.076 7].[4.080 17]>
  /~zod/home/~2019.2.14..21.50.56..4e2e/sys/vane/clay:<[4.077 7].[4.080 17]>
  /~zod/home/~2019.2.14..21.50.56..4e2e/sys/vane/clay:<[4.078 9].[4.079 66]>
  /~zod/home/~2019.2.14..21.50.56..4e2e/sys/vane/clay:<[4.079 9].[4.079 66]>
  /~zod/home/~2019.2.14..21.50.56..4e2e/sys/vane/clay:<[4.079 14].[4.079 66]>
  /~zod/home/~2019.2.14..21.50.56..4e2e/sys/vane/clay:<[1.888 5].[1.907 15]>
  /~zod/home/~2019.2.14..21.50.56..4e2e/sys/vane/clay:<[1.889 5].[1.907 15]>
  /~zod/home/~2019.2.14..21.50.56..4e2e/sys/vane/clay:<[1.890 5].[1.907 15]>
  /~zod/home/~2019.2.14..21.50.56..4e2e/sys/vane/clay:<[1.891 5].[1.907 15]>
  /~zod/home/~2019.2.14..21.50.56..4e2e/sys/vane/clay:<[1.891 9].[1.901 11]>
  /~zod/home/~2019.2.14..21.50.56..4e2e/sys/vane/clay:<[1.892 9].[1.901 11]>
  /~zod/home/~2019.2.14..21.50.56..4e2e/sys/vane/clay:<[1.892 19].[1.892 81]>
  "validate foreign plops failed"
  /~zod/home/~2019.2.14..21.50.56..4e2e/sys/vane/clay:<[1.892 54].[1.892 80]>
  /~zod/home/~2019.2.14..21.50.56..4e2e/sys/vane/clay:<[498 5].[499 57]>
  /~zod/home/~2019.2.14..21.50.56..4e2e/sys/vane/clay:<[499 5].[499 57]>
  /~zod/home/~2019.2.14..21.50.56..4e2e/sys/vane/clay:<[489 5].[489 40]>
  /~zod/home/~2019.2.14..21.50.56..4e2e/sys/vane/clay:<[489 27].[489 39]>
  \/%path: no matches for /~ponnys-podfer/home/~2019.2.14..22.29.27..761c/mar/\/
    txt-diff/hoon
  \/                                                                          \/
  ford: %vale failed while searching for %txt-diff:
  /~zod/home/~2019.2.14..21.50.56..4e2e/sys/vane/clay:<[482 44].[482 54]>
  %ford-fail
  /~zod/home/~2019.2.14..21.50.56..4e2e/sys/vane/clay:<[482 30].[482 55]>
  /~zod/home/~2019.2.14..21.50.56..4e2e/sys/vane/clay:<[553 19].[553 53]>
  /~zod/home/~2019.2.14..21.50.56..4e2e/sys/vane/clay:<[553 16].[553 53]>
crude: punted
[%fail-ack 0]

[joemfb]

There's a candidate fix for this in #1074

[ngzax]

This looks similar to the issue I opened, #1067. I'm getting these alot, though mine are in /vane/eyre not clay.

[belisarius222]

@philipcmonk Can we close this now that #1074 has been merged?

[jtobin]

Closing this as the lack of follow-up leads me to infer it was fixed by the linked PR.