Erin Marshall

Wouldn't it be easiest to write most everything as a preprocessor macro? Then you could save _all_ the cycles :D

Or `sudo killall qemu`. If you're running under Vagrant, you'll have to do another `vagrant ssh` in a different shell to quit it, obviously ;)

We should probably pull NEXT and template `docker-compose.yml` in an `ExecStartPre`, and then do ``` ExecStart=docker-compose -f $COMPOSE_FILE up ExecStop=docker-compose -f $COMPOSE_FILE down ``` in `next.service`.

No, I haven't? Liam On Thu, Jun 29, 2017 at 5:36 PM, Scott Sievert wrote: > Did you create a new AMI for this? I'm seeing an AMI with the...

@dconathan We're contemplating a release soon-ish; can you open a PR with that code?

Backed off on this change for now. Some comments @dconathan made on Slack about why we're not doing this: > I have moved to celery 4. I have noticed getQuery...

@dconathan can you test this again, since it's apparently fixed (c.f. celery/celery#3814)

@lalitkumarj The try-except blocks had essentially duplicated code in each, so the exception handling was moved into tasks.py, where each of the app functions is called. This is done by...

That's not _actually a part_ of an OS. This guide is about an OS, and he shows in the `userland` folder how to use libc. Just write your REPL normally...

Lua is nice, that's pretty simple to interface. Maybe a better approach to loading levels would be to have a `levels/` folder with multiple level scripts?