Logged Conversation (all times UTC)
[12:57] <stellar-slack> when core folks get in this morning: c85993f seems to just exit on its own
[12:57] <stellar-slack> last couple logs are
[12:57] <stellar-slack> ```
[12:57] <stellar-slack> 2015-04-20T12:56:02.487 ad6cc5 [History] INFO put .well-known/stellar-history.json in history archive 'core-001'
[12:57] <stellar-slack> 2015-04-20T12:56:02.487 ad6cc5 [History] INFO Initialized history archive 'core-001'
[12:57] <stellar-slack> 2015-04-20T12:56:02.487 ad6cc5 [default] INFO Application destructing
[12:57] <stellar-slack> 2015-04-20T12:56:02.488 ad6cc5 [default] INFO Application destroyed
[12:57] <stellar-slack> ```
[12:57] <stellar-slack> it does store that hist file successfully. Also no core dump that I can see so looks like a clean exit. Just not sure why
[17:30] <stellar-slack> epsilon: re 'martiarchal': over the line again. women get enough grief simply existing in the tech industry, don't need to be made extra self-conscious.
[17:30] <stellar-slack> matschaffer: that's normal behavior for an application run with --newhist
[17:30] <stellar-slack> matschaffer: it initializes a history archive then exits
[21:07] <stellar-slack> graydon: happens without newhist as well
[21:08] <stellar-slack> oh actually nm
[21:08] <stellar-slack> k. that’s my bug. I think the start script is checking the wrong place to see if history has been initialized or not
[21:08] <stellar-slack> yep! thanks
[21:08] <stellar-slack> yep
[21:12] <stellar-slack> wat
[21:15] <stellar-slack> mat: looks like whoever setup the public slack didn’t restrict slackbot’s responses to admins only
[21:16] <stellar-slack> cleaning it up now
[21:16] <stellar-slack> thanks Scott
[21:16] <stellar-slack> that’d be me
[21:16] <stellar-slack> didn’t even know that was a setting
[21:16] <stellar-slack> nor did I, good to know
[21:17] <stellar-slack> no worries! I just discovered it myself as well :simple_smile:
[21:20] <stellar-slack> yep
[21:25] <stellar-slack> `state" : "Synced!”` - Nice exclamation point
[21:30] <stellar-slack> lol
[21:33] <stellar-slack> that's how i know that everything is :+1:
[21:35] <stellar-slack> the 3rd node syncs now too. Sweet!
[21:37] <stellar-slack> hmm, for some reason torquebox 4 is not handling streaming responses :disappointed: Going to check with their dev team, but that’s more pressure to move towards a different deployment strategy for horizon
[21:48] <stellar-slack> gotcha
[21:55] <stellar-slack> fuck: https://github.com/jruby/jruby-rack/issues/119
[21:55] <stellar-slack> how’d I miss that.
[22:01] <stellar-slack> because it surprising :)
[22:01] <stellar-slack> oops that was a respone to mat above
[22:06] <stellar-slack> haha! the exclamation point you mean
[22:06] <stellar-slack> exciting anyway :simple_smile:
[22:09] <stellar-slack> scott: yeah, that’s a bummer. If it works on MRI I’m okay going that route for the time being
[22:14] <stellar-slack> yeah, that’s what I’m going to proceed with for now.
[22:43] <stellar-slack> Lemme know if there's a particular version. Or I'll probably just end up using the latest release when the ticket comes around
[22:47] <stellar-slack> sure. I have it running in travis against 1.9.3 and 2.1.5, and 2.2.0
About StellarVerse IRC Logger
StellarValue IRC Logger
is part of