Victoria Fierce tdfischer

Codius Sandbox Eventing

At some point, a sandboxed process will try to run a syscall that interacts with IO, such as:

open(const char* path, int mode)

Within our sandbox, the following events happen:

The process calls libc's open call
Libc translates this to system(SYS_open, path, mode) using the constants in /usr/include/asm/unistd_64.h

Howdy Hackers.

Lets have a heart-to-heart.

I love Noisebridge.

I really do love Noisebridge.

To say that my motivations for moving 3,000 miles from Akron, Ohio to put down roots on the west coast did not include Noisebridge would be a lie.

I hereby claim:

To claim this, I am signing this object:

	#!/usr/bin/python
	import smtplib
	from email.mime.text import MIMEText
	import os
	import sys
	from twilio.rest import TwilioRestClient
	import imp

	config = imp.load_source('login_notify.config', '/etc/sysconfig/login-notify')

	/home/tdfischer/Projects/ripple/codius/rust/codius-sandbox-core/src/lib.rs:22:9: 25:10 error: cannot infer an appropriate lifetime due to conflicting requirements
	/home/tdfischer/Projects/ripple/codius/rust/codius-sandbox-core/src/lib.rs:22 \|sbox,e\| {
	/home/tdfischer/Projects/ripple/codius/rust/codius-sandbox-core/src/lib.rs:23 let s: sbox_ptr = mem::transmute(sbox);
	/home/tdfischer/Projects/ripple/codius/rust/codius-sandbox-core/src/lib.rs:24 event_cb (s, e);
	/home/tdfischer/Projects/ripple/codius/rust/codius-sandbox-core/src/lib.rs:25 }
	/home/tdfischer/Projects/ripple/codius/rust/codius-sandbox-core/src/lib.rs:21:25: 21:37 note: first, the lifetime cannot outlive the expression at 21:24...
	/home/tdfischer/Projects/ripple/codius/rust/codius-sandbox-core/src/lib.rs:21 let sbox = Box::new(Sandbox::new(
	^~~~~~~~~~~~
	/home/tdfischer/Projects/ripple/codius/rust/codius-s

	bluebird.promisifyAll(SomeType.prototype);

	var foo = new SomeType();

	foo.doFooAsync().then(function(r) {

	//SOME COMPUTERING

	foo.doMoreAsync().then(function(r) {

	FROM ansible/centos7-ansible:stable

	MAINTAINER Team Caminus <[email protected]>

	ADD .
	RUN ansible-playbook playbooks/www-config.yml

	...** SANDSTORM SUPERVISOR: Starting up grain.
	sandstorm/supervisor.c++:1136: warning: ip_tables kernel module not loaded; cannot set up transparent network forwarding.
	Traceback (most recent call last):
	File "/usr/lib64/python2.7/site.py", line 556, in <module>
	main()
	File "/usr/lib64/python2.7/site.py", line 538, in main
	known_paths = addusersitepackages(known_paths)
	File "/usr/lib64/python2.7/site.py", line 266, in addusersitepackages
	user_site = getusersitepackages()
	File "/usr/lib64/python2.7/site.py", line 241, in getusersitepackages

	[22:40:48] <tdfischer> hi so I want to put my frumpy hat on and say that yes ##computer is interested in technical problems to a limited degree compared to the support group therapy problem that we are primarily focused about
	[22:41:04] <tdfischer> but the group therapy is the big thing we're all about
	[22:41:30] <tdfischer> I think its totally acceptible for someone to ask about a technical problem and get an answer every once in a while
	[22:42:17] <tdfischer> but I don't think it can be a trend as long as we like the primary group therapy focus
	[22:42:45] <tdfischer> correspondingly, I /do not/ think it is okay for randos to come in and ask tech problems and get answers without contributing to the group therapy concept
	[22:43:47] <tdfischer> I think a perfectly legitimate thing would be for someone to come in and say, for example, "How can I teach this technical concept to a coworker"
	[22:44:03] <tdfischer> which blurs the line but I think thats the kind of "technical" problem I'm interested in addressing

	from django.utils import timezone
	from django.core.management.base import BaseCommand
	from django.db.models import Count
	from crm.models import Turf
	from django.core.mail import EmailMessage
	from django.template import loader

	class Command(BaseCommand):
	def handle(self, args, *options):
	email_template = loader.get_template('new-neighbors-notification.eml')