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
kentonv has quit [Quit: Leaving]
kentonv has joined #sandstorm
frigginglorious has joined #sandstorm
strugee has quit [Remote host closed the connection]
frigginglorious has quit [Quit: frigginglorious]
<isd> Reminder: office hours tomorrow
_whitelogger has joined #sandstorm
strugee has joined #sandstorm
_whitelogger has joined #sandstorm
strugee has quit [Ping timeout: 260 seconds]
strugee has joined #sandstorm
strugee has quit [Remote host closed the connection]
NwS has joined #sandstorm
<isd> Reminder: office hours in 20 minutes
<abliss> cool, i just tried https://github.com/latacora/acme-dns-01-gcp as an acme plugin for Google Domains, and it seems to work
<abliss> unfortunately, running "make update" in my sandstorm repo seems to have broken my server :(
<abliss> `Error: Cannot find module '/node_modules/capnp.js'`
<abliss> what does this mean in `node_modules/capnp.js/Readme.md`? `## undefined.js
<abliss> Define your `undefined` yo!`
<kentonv> huh? capnp.js should be a file, not a directory...
<abliss> something must've gotten screwed up with my meteor/node stuff i guess
<abliss> `sandstorm/package-lock.json` is full of undefined stuff
<kentonv> I don't even have a package-lock.json...
<kentonv> certainly not one in the top-level sandstorm directory
<abliss> this is probably because i tried running `npm install` in the root directory (i was told to by some subprocess of `make`)
<abliss> `==== building meteor frontend ====
<abliss> Browserslist: caniuse-lite is outdated. Please run next command `npm update``
<kentonv> time to git clean I guess
<isd> Yeah, that might cause problems
<kentonv> yeah unfortunately some random dependency gave you a bad instruction
<isd> (fwiw I do have a package-lock.json, though my setup is working)
<kentonv> so, anything npm-related should be done under `shell`, and probably using `meteor npm` (not just `npm`)
<kentonv> but even then, I'm dubious of that message you saw
<kentonv> because I just ran `meteor npm update` yesterday
<kentonv> and I think I've seen that log line before
<kentonv> I'd ignore it
<abliss> i'd cry if i had to git clean, since it takes me about a day to get through a sandstorm build... i'm going to try selectively nuking node stuff that looks out of place
<kentonv> really? It takes like 10 minutes for me, at most
<abliss> lots of things go wrong (sometimes because I only have 2Gb of ram, so random JS/ekam stuff has a tendency to get OOM-killed), and debugging it often seems to involve starting all the way over again
<isd> Yeah, the caniuse-lite thing is there every time I build
<kentonv> get some more ram. :)
<isd> A cold build for me is also about 10 minutes
<isd> What are the specs on your machine?
<isd> Also, enabling swap might at least dodge the oom issues if you're not going over by much8
<isd> Still, if it's taking a day something is seriously wrong
<abliss> it doesn't take the computer a day of CPU time, but it takes a day of wall-clock time of me and the computer working together (with me getting distracted by other stuff in the long down-times)
<isd> Office hours now.
<abliss> any ideas for more ways to clear out a bad node/meteor state without killing all the c++ stuff? i trashed all of bundle/ and I touched shell/package.json , but `make bundle` still produces a `bundle/node_modules/` with nothing but a `capnp/` directory (which contains nothing but `.capnp` files)
<abliss> Makefile says `we need Ekam to build node_modules before we can run Meteor` but i'm not sure what that means exactly
<abliss> shell/package.json doesn't specify any dependency on capnp, so `npm install` doesn't seem to create it
<isd> I think if you nuke everything outside of bin/ and tmp/, that should keep the stuff ekam has built but clear out everything else.
<abliss> what's supposed to be in repo_root/node_modules ?
<abliss> or what triggers the build in deps/capnp-node?
<abliss> and what version of node am i supposed to be using for it? because build.js fails due to `sp.stdout` being undefined
<abliss> sorry, null, not undefined
<isd> The build should use the version of node that ships with meteor.
<abliss> which meteor?
<isd> run ./find-meteor-dev-bundle.sh
<abliss> so the 1.10, not the 1.8?
<isd> everything under deps/ gets handled by ekam
<isd> Correct. 1.8 is just used for the one font related hack.
<abliss> how do i make ekam rebuild node-capnp? touching package.json doesn't seem to do it
<isd> touch the C++ file?
<abliss> ok, that made something happen
<abliss> `ekam-provider/canonical/node-capnp/capnp.cc:29:10: fatal error: 'node.h' file not found`
<abliss> i think i probably started this `make continuous` back before i had to nuke & replace my `~/.meteor` and now the paths are different in there
<abliss> e.g. `.meteor/packages/meteor-tool/.1.10.1.u6noau.fjrw++os.linux.x86_64+web.browser+web.browser.legacy+web.cordova/mt-os.linux.x86_64/dev_bundle/` now has a different random-looking hash after .1.10.1
<abliss> maybe a running ekam can't cope with that?
<isd> That's possible.
<isd> If it's still using the old node, that could be a problem
<abliss> i'd kill it and start over, but that means giving up on getting sandstorm built today... :(
<abliss> ah well, so it goes. maybe i'll have better luck tomorrow.
cbaines has quit [Quit: bye]
cbaines has joined #sandstorm