These are chat archives for tableflip/boss

28th
Nov 2014
Alan Shaw
@alanshaw
Nov 28 2014 15:44
Screen Shot 2014-11-28 at 15.43.32.png
Alex Potsides
@achingbrain
Nov 28 2014 17:16
Looks nice
Are you dropping a documentation update?
Alan Shaw
@alanshaw
Nov 28 2014 18:13
Should do shouldn't I! Is that diagram roughly right? Obv communication is both ways, and I guess there should be a box around boss-daemon, boss-local and boss...
Alex Potsides
@achingbrain
Nov 28 2014 18:31
Yeah, it looks accurate
Alan Shaw
@alanshaw
Nov 28 2014 18:33
I'm having trouble finding where stop and restart are actually exposed - they don't seem to be in the API
Alex Potsides
@achingbrain
Nov 28 2014 18:33
stop is the 'kill' method on the ProcessRPC class
Alan Shaw
@alanshaw
Nov 28 2014 18:34
God I wish there was some sort of developer spell check that knows "words" like api
Alex Potsides
@achingbrain
Nov 28 2014 18:35
restart is also on ProcessRPC and it's like kill but it tells the daemon that it's about to kill itself and that it should be restarted
Alan Shaw
@alanshaw
Nov 28 2014 18:36
Cool thanks
Why are you dependency injecting core modules btw?
Alex Potsides
@achingbrain
Nov 28 2014 18:38
unit testing without proxyquire
proxyquire makes me ick
pretty sure it's all going to explode with node 0.12 too
whenever that turns up
Alan Shaw
@alanshaw
Nov 28 2014 18:42
I see.
Maybe they'll just node 1.0
Alex Potsides
@achingbrain
Nov 28 2014 18:43
doesn't that mean it's finished?
Alan Shaw
@alanshaw
Nov 28 2014 18:43
Ha, like, dead
Yeah you're right, looking forward to streams 4
"rivers"
Alex Potsides
@achingbrain
Nov 28 2014 19:22
have you ever seen problems with filename lengths for unix sockets with net.listen?
just swapped out /tmp/foo for os.tmpdir() + '/foo' and all the boss integration tests broke
os.tmpdir() is very long on my mac
the dirs were os.tmpdir() + '/boss-test/' + uuid.v4() which ended up being 105 characters long
swapped out uuid for shortid to get 77 char dirs and the tests start passing again
weird
they were failing with ENOENT trying to load socket files for processes
the actual socket files appeared truncated
e.g. the full path should have been: /var/folders/m1/8m_hh8996718p5dxsx2zw0840000gn/T/337b32ed-2b48-4f11-a6a7-814cc67caab9/run/processes/55768
but on the filesystem was: /var/folders/m1/8m_hh8996718p5dxsx2zw0840000gn/T/337b32ed-2b48-4f11-a6a7-814cc67caab9/run/processes/557