00:55 <GauntletWizard> A most auspicious portent: http://www.thenational.ae/uae/elusive-arabian-sand-cat-photographed-in-abu-dhabis-western-region

00:57 <zarvox> :D

01:36 <dwrensha> in case anyone's curious, this project is why I was keen on getting opencv working in ipython on Sandstorm: http://lea.zone/blog/making-of-fortunes/

01:47 <zarvox> That's a pretty awesome project + writeup!

01:47 <zarvox> Hardware, software, craft, and whimsy, all in one.

05:35 <ocdtrekkie> asheesh, I totally need help.

05:55 <zarvox> ocdtrekkie: anything I can help you with?

05:56 <ocdtrekkie> zarvox: Mebbe.

06:14 <ocdtrekkie> Collections 1.0 \o/

06:14 <ocdtrekkie> Feature request filed. :D

08:11 <JonTheNiceGuy[m]> My sandstorm server won't start up, and I'm getting loads and loads of csr and json files in /opt/sandstorm/var/sandcats/https/jonspriggs.sandcats.io

08:12 <JonTheNiceGuy[m]> http://pastebin.com/2b16YhLs <- My log file

08:12 <JonTheNiceGuy[m]> I've deleted a load of csr and response files because I wasn't sure if that was the cause

14:12 <dwrensha> oh, sweet --- the demo now comes with preinstalled apps

15:14 <ocdtrekkie> And so does vagrant-spk :(

15:56 <asheesh> Hah, interesting ocdtrekkie re: vagrant-spk + preinstalled aps

15:57 <asheesh> +/- 'p'

15:57 <asheesh> JonTheNiceGuy[m]: That sounds pretty urgent and bad. I'll read your log now.

16:04 <asheesh> JonTheNiceGuy[m]: Do you have another service listening on port 443, by any chance?

16:20 <asheesh> (in my testing, that doesn't seem to trigger the problem, so I'm actually still confused; see https://github.com/sandstorm-io/sandstorm/issues/2355 )

16:36 <JonTheNiceGuy[m]> Asheesh: http://jonspriggs.plus.com/ps.txt actually netstat -antp

16:38 <JonTheNiceGuy[m]> If you want to mail me an SSH public key, I'll stick it on the root account so you can have a poke around

17:23 <JonTheNiceGuy[m]> Oops, no it actually is a ps. One tic

17:25 <JonTheNiceGuy[m]> http://jonspriggs.plus.com/netstat.txt

18:50 <depb> Hi all, does anyone know if there are plans to port sandstorm to run on clusters with ARM processor?

18:54 <asheesh> Hi depb!

18:54 <asheesh> It depends how much work you want to do, which is another way of saying mostly-no.

18:55 <asheesh> There are currently no near-term plans to enable ARM for Sandstorm; we mostly think it'll make app QA harder, which isn't something we can commit resources to in order to make it worthwhile.

18:55 <asheesh> Out of curiosity, what's your interest?

18:56 <asheesh> I hear the request for ARM support periodically and I'd like to better-understand why people ask for it, if you're willing to share.

19:03 <depb> What a shame .... I ask it because I wanted equipment with Hardware Libre. Because now if all goes well it would be possible by EOMA68, each has A20 Dual-Core ARM Cortex A7, 1.2 GHz and 2GB of Ram, each of them. I would be in the clouds to have all FLOSSH XD And connect everything to Guifi.net it would be my dream come true XD

19:04 <maurer> depb: So, from my understanding of the tech stacks involved, there's nothing fundamentally problematic in running on arm

19:04 <maurer> depb: it's just that there's no releng for it

19:05 <maurer> depb: so you'd have to do your own updates, builds, etc

19:05 <maurer> and it might have bugs

19:05 <maurer> but if you're already going the length to try to use exclusively free hardware, I suspect this might be within your risk/work tolerance

19:05 <maurer> (you'd also have to do your own builds of spks, and wouldn't be able to use the app store)

19:10 <mokomull> A technical limitation that might prevent that is that the ARM SoC vendors aren't particularly well-known for supporting newer kernels after they're released, so the giant-blob-dump of $VENDOR may not ever support software interfaces required for Sandstorm.

19:10 <depb> but in theory it would be possible, with possible bugs in the process ... of course? I simply compile all necessary software, like I do with soft from github?

19:11 <maurer> depb: Yes, but as mokomull notes, you may want to test your kernel for the features sandstorm uses for sandboxing first before you go through the trouble

19:11 <mokomull> I know several that are stuck at 3.4, and even on x86 Intel doesn't support anything other than a huge-patch atop 3.10 (with a bunch of useful features CONFIG_*=n'ed out) on the Edison.

19:11 <maurer> depb: Unless you're building recent vanilla on your devices and having them work, it's kind of a crapshoot whether those features are enabled

19:12 <mokomull> depb: I also want to caution you that basically all of the vendors aren't know for quality or responsiveness to security issues, either. Libre may not

19:12 <mokomull> Libre may not be quite the benefit you're imagining.

19:20 <zarvox> There's also the additional issue that app packages are binary, so you'd also have to get app authors to build/release packages for ARM too. And we're not currently set up to deal with architectures that aren't x86_64.

19:21 <zarvox> Alternately, you'd have to automate the build pipeline enough that you could hand off some "source package" equivalent to automated builders. But then package signing gets complicated.

19:22 <zarvox> Also, two of our dependencies, mongodb and meteor, didn't officially support running on ARM last I checked.

19:26 <zarvox> So, all that said, supporting Sandstorm on ARM isn't currently a priority for us. There's a lot of work for comparatively little gain, and there's a lot of unmitigatable risk from external factors.

19:27 <depb> Ok I see, It will be difficult if not impossible. Thank you very much to all I'll have everything you have told me in mind. For now I will install sandstorm on x86-64 and I will try as an experiment on an ARM processor when I get my EOMA68

20:04 <mokomull> zarvox: asheesh: I do have an AArch64 development board (the Dragonboard 410c) if y'all become interested in playing with it. WiFi was once shaky, but there's far newer drivers than I've had a chance to install.

20:18 <JonTheNiceGuy[m]> Asheesh, would your access to my machine help?

20:25 <TC01> asheesh: thanks for publishing my app :)

20:57 <zarvox> Looks like AArch64 support will land in mongo 3.3? https://jira.mongodb.org/browse/SERVER-1811

21:00 <zarvox> Meteor doesn't official support ARM, but there appear to be some community forks intended to run on ARM: https://meteor-universal.tumblr.com/

21:01 <nliao> hello

21:02 <nliao> I'm trying to build a sandstorm app, but came across an error when running 'vagrant-spa dev'

21:02 <nliao> see below:

21:02 <nliao> gyp ERR! build error

21:02 <nliao> gyp ERR! stack Error: `make` failed with exit code: 2

21:02 <nliao> gyp ERR! stack at ChildProcess.onExit (/home/vagrant/.meteor/packages/meteor-tool/.1.1.3.4sddkj++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:267:23)

21:02 <nliao> gyp ERR! stack at ChildProcess.emit (events.js:98:17)

21:02 <nliao> gyp ERR! stack at Process.ChildProcess._handle.onexit (child_process.js:820:12)

21:02 <nliao> gyp ERR! System Linux 3.16.0-4-amd64

21:02 <nliao> gyp ERR! command "node" "/home/vagrant/.meteor/packages/meteor-tool/.1.1.3.4sddkj++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--release"

21:02 <nliao> gyp ERR! cwd /home/vagrant/bundle/programs/server/node_modules/fibers

21:02 <nliao> gyp ERR! node -v v0.10.36

21:02 <nliao> gyp ERR! node-gyp -v v1.0.1

21:02 <nliao> gyp ERR! not ok

21:05 <dwrensha> nliao: it might be the meteor-spk does not yet support the version of meteor that you are using

21:20 <nliao> I'm using meteor version 1.4

21:22 <dwrensha> yeah, sadly that won't work yet. :(

21:23 <nliao> thanks

21:23 <nliao> will try down grading

21:55 <xet7> asheesh: We don't need to continue discuss terminology on that GitHub issue, I think changing terminology needs more thought and me reading more of the documentation for more complete proposal.

22:03 <asheesh> xet7: OK!

22:03 <asheesh> JonTheNiceGuy[m]: Yes! Just overwhelmed with other things at the moment.

22:04 <asheesh> nliao: Glad that dwrensha was able to help you!

22:08 <mrdomino> i am midway through writing skylark capnp -> c++ rules

22:08 <mrdomino> hoo boy

22:09 <dwrensha> skylark?