~doznec flips out needing something about arvo

[juped]

Oh, and I had to manually |reset it before any other ship could talk to it

[galenwp]

@ohAitch can you weigh in here?

[ohAitch]

foreign-hat is the redirect for cross-ship SSO. The crash says that we're
getting a hostname response from a ship whose hostname we didn't ask for(in
fact, no requests are pending); no obvious idea how this would happen, or
why it would go away on reset.

On Monday, 14 March 2016, Galen Wolfe-Pauly <[email protected]
javascript:_e(%7B%7D,'cvml','[email protected]');> wrote:

@ohAitch https://github.com/ohAitch can you weigh in here?

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#71 (comment)

[juped]

It didn't go away on reset, doznec's inability to communiciate with the network went away on reset.

[juped]

And the legend says that to this day, ~doznec continues to flip out, dumping a stack trace every couple seconds.

-- Scary Urbit Stories To Tell Your Kids

[ohAitch]

Looks like the ship responsible exponentially backed off or sth, at any
rate I do not currently see a flood of traces on doznec(though a bunch in
the past).

On Tuesday, 15 March 2016, Raymond Pasco [email protected] wrote:

And the legend says that to this day, ~doznec continues to flip out,
dumping a stack trace every couple seconds.

-- Scary Urbit Stories To Tell Your Kids

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#71 (comment)

[galenwp]

Closed, because... ancient.