02:42 <garrison> Is it possible to open a shell within a grain to run an interactive debugger? A bash prompt would work, but my real goal is to get to the julia repl, from which I can start a debugging session. This is to further debug my effort at https://github.com/garrison/sandstorm-pluto-jl which is failing for some unknown reason, as subprocesses of julia's

02:42 <garrison> "Distributed" multiprocessing system aren't able to see installed packages. I suspect this has something to do with the sandbox, as I cannot reproduce the issue outside sandstorm.

02:43 <ocdtrekkie> How are you packaging the app?

02:44 <ocdtrekkie> vagrant-spk enter-grain is what you are looking for, but it's unfortunately not generalized to work with other packaging tools.

02:44 <garrison> I am using docker-spk, but I can "start over" to get that feature

02:45 <ocdtrekkie> I think it might technically be able to talk to other dev mode grains, but the scaffolding around it assumes vagrant-spk, basically.

02:45 <garrison> or rather, do my investigations using vagrant-spk, then probably just go back to using docker-spk once I figure it out

02:47 <isd> ocdtrekkie: the logic for enter-grain itself is pretty agnostic towards the packaging tool, but docker-spk doesn't do the filesystem watching stuff that spk dev does, so if you try to launch a shell in a grain that doesn't have one, it just won't work, rather than pulling in the files it needs from the host dynamically.

02:58 <garrison> isd: is there any way to enter the grain using docker-spk?

03:00 <isd> docker-spk doesn't really have a version of spk dev so there's not really a comparison to make... but if you set up searchPath correctly you can do spk unpack and then spk dev...

03:01 <garrison> I have used spk dev with docker-spk. Does it have a way of entering the grain?

03:03 <isd> Not nicely bundled; we really should factor the logic out from vagrant-spk so it's usable by other tools.

03:03 <isd> You could do this inside of a vagrant-spk spawned box, and then do vagrant-spk enter-grain from outside..

03:04 <isd> It just looks for grains in dev mode, so should still work fine if it's a grain that wasn't actually launched by vagrant-spk...

03:09 <garrison> OK, I will play with this more tomorrow. Thanks for the info.

04:26 <xet7> Why Node.js has security updates so often? It feels like PHP.

04:30 <xet7> Actually, recently Node.js has had security updates more often than PHP.

04:31 <xet7> Well, it could be that there's more research about that...

04:42 <ocdtrekkie> xet7: I would say the more prolific something is used, the more often people find ways to exploit it maliciously.

04:43 <ocdtrekkie> What PHP and Node have in common is that they're both extremely popular setups for web servers, and hence a very lucrative target for compromise.

04:44 <xet7> What programming language would be more secure?

13:12 <TimMc> The funny thing is that it's not really the language, per se, as much as the standard library having security issues.

13:12 <TimMc> PHP's standard library is historically a giant pile of land mines.