kentonv changed the topic of #sandstorm to: Welcome to #sandstorm: home of all things sandstorm.io. Say hi! | Have a question but no one is here? Try asking in the discussion group: https://groups.google.com/group/sandstorm-dev
<ocdtrekkie>
I added what I'm working on to the community project Wekan.
<ocdtrekkie>
I tried to set the yellow label as "App Updates" to differentiate from App Porting, but I think abliss has to do it.
<abliss>
Done, lemme know if you have ideas for other labels.
frigginglorious has quit [Read error: Connection reset by peer]
<CaptainCalliope>
Time for our new tuesday evening conference call!
<CaptainCalliope>
Ugh. Someone turned on a microwave and it kicked me from the video.
<abliss>
is the call over? i'm getting silence on the POTS link
<isd>
Yeah, we were pretty close to done when you called in; didn't really have anything left to talk about.
<abliss>
ok, sorry i missed it.
<CaptainCalliope>
It was a short agenda. I think my biggest takeaway from the last two meetings is that there's not as much to talk about atm because things we've discussed previously are in various stages of actually happening!
<CaptainCalliope>
Go team!
<isd>
...why does building meteor-spk require building both mongo and some fork of mongo from source?
<isd>
Aha. I understand now. That's unpleasant.
<isd>
Went and investigated, the typescript capnp implementation still doesn't do RPC, so that's a big project that would need to happen before we could even consider switching.
Nemo_bis has joined #sandstorm
nicoo has quit [Remote host closed the connection]
nicoo has joined #sandstorm
frigginglorious has joined #sandstorm
<isd>
kentonv: re: node-capnp, signed up for an npm account, username isd.
<isd>
...apparently 'hack' is in their list of bad words that you're not allowed to use in a username, so my usual handle is out...
frigginglorious has quit [Read error: Connection reset by peer]
frigginglorious has joined #sandstorm
<ill_logic>
haha
<ill_logic>
I'm trying to figure out what kind of mishap lead to that rule.
<ill_logic>
(Just imagining, no fun looking it up)
<ill_logic>
Oh this would be a fun one to have packaged once we figure out federation in general https://yacy.net/
frigginglorious1 has joined #sandstorm
frigginglorious has quit [Ping timeout: 240 seconds]
frigginglorious1 is now known as frigginglorious
frigginglorious has quit [Read error: Connection reset by peer]
frigginglorious has joined #sandstorm
<kentonv>
isd, for security paranoia purposes (since IRC is not secure), can you open an issue on node-capnp github requesting that I add you to npm and verifying your npm username?
<isd>
btw, I get a fair number of warnings when building sandstorm about unused lambda captures (in the existing code, not stuff I've added), but I'm unsure whether it's actually safe to remove them. It's vaguely annoying because sometimes it means actual errors get cut off in the log and I have to futz with ekam-client and the log length to see what the error I care about is. Any advice?
<kentonv>
yeah probably they are safe to remove and we should do so
<kentonv>
the warning has gotten more sensitive over the years
<isd>
Ok. I'll add that to my TODO list.
<isd>
hm, what do I have to do to get actual function names in stack traces? right now it's just giving me a list of what I assume are pc values.
<kentonv>
build in debug mode, or use addr2line
<kentonv>
which program?
<kentonv>
(if it's inside the sandbox then debug mode won't help, since KJ in debug mode shells out to addr2line, but it won't be available in the sandbox)
<isd>
This is the bridge, so I guess I'm out of luck.
<isd>
Or I guess I need to add that to the package.
<kentonv>
I suggest just calling addr2line manually
<kentonv>
(outside the sandbox)
<kentonv>
copy/paste the addresses over
<isd>
Useful, thanks
<kentonv>
this is what I end up doing 99% of the time (e.g. most stack traces I debug in Cloudflare Workers are generated inside the sandbox, so I have to decode them manually)