00:04
jadewang has joined #sandstorm
00:10
joshbuddy has quit [Quit: joshbuddy]
00:26
[d__d] has quit [Remote host closed the connection]
00:27
tdfischer_ has quit [Quit: No Ping reply in 180 seconds.]
00:28
joshbuddy has joined #sandstorm
00:28
tdfischer has joined #sandstorm
00:37
[d__d] has joined #sandstorm
00:54
jadewang has quit [Remote host closed the connection]
00:59
natea has joined #sandstorm
01:07
mcpherrin has quit [Ping timeout: 264 seconds]
01:07
jadewang has joined #sandstorm
01:07
jadewang has quit [Remote host closed the connection]
01:50
mcpherrin has joined #sandstorm
02:08
jadewang has joined #sandstorm
02:13
jadewang has quit [Ping timeout: 255 seconds]
02:20
gopar has joined #sandstorm
02:41
joshbuddy has quit [Quit: joshbuddy]
03:09
jadewang has joined #sandstorm
03:14
jadewang has quit [Ping timeout: 255 seconds]
03:26
ArcTanSusan has joined #sandstorm
03:45
ArcTanSusan has quit [Quit: ArcTanSusan]
04:34
bb010g has joined #sandstorm
05:13
gopar has quit [Quit: Leaving]
05:30
ArcTanSusan has joined #sandstorm
05:49
ArcTanSusan has quit [Quit: ArcTanSusan]
05:55
jadewang has joined #sandstorm
05:59
jadewang has quit [Ping timeout: 246 seconds]
06:08
<
warren >
kentonv: see you tomorrow at 12:30 right?
07:03
<
kentonv >
warren: yep
07:03
jadewang has joined #sandstorm
07:03
joshbuddy has joined #sandstorm
07:14
jadewang has quit [Ping timeout: 246 seconds]
07:14
jadewang has joined #sandstorm
07:40
ArcTanSusan has joined #sandstorm
08:46
ArcTanSusan has quit [Quit: ArcTanSusan]
08:46
jadewang has quit [Remote host closed the connection]
08:50
joshbuddy has quit [Quit: joshbuddy]
08:59
joshbuddy has joined #sandstorm
09:11
tony123 has joined #sandstorm
09:55
joshbuddy has quit [Quit: joshbuddy]
10:15
mort___ has joined #sandstorm
10:20
mort___1 has joined #sandstorm
10:22
mort___ has quit [Ping timeout: 252 seconds]
10:53
mort___1 has quit [Quit: Leaving.]
11:23
amyers has joined #sandstorm
11:47
jadewang has joined #sandstorm
11:51
jadewang has quit [Ping timeout: 264 seconds]
12:48
YuviPanda is now known as YuviPanda|food
13:16
mort___ has joined #sandstorm
14:02
natea has quit [Quit: natea]
14:16
mort___ has quit [Quit: Leaving.]
14:20
natea has joined #sandstorm
15:08
_whitelogger has joined #sandstorm
15:16
natea has joined #sandstorm
15:29
natea has quit [Read error: Connection reset by peer]
15:30
natea has joined #sandstorm
15:33
pixelport has joined #sandstorm
15:36
YuviPanda|food is now known as YuviPanda
15:36
YuviPanda has quit [Changing host]
15:36
YuviPanda has joined #sandstorm
15:38
asmyers has quit [Remote host closed the connection]
15:38
asmyers has joined #sandstorm
15:43
natea_ has joined #sandstorm
15:43
natea has quit [Ping timeout: 276 seconds]
15:43
natea_ is now known as natea
16:09
natea has quit [Quit: natea]
16:33
jadewang has joined #sandstorm
16:33
phildini_ is now known as phildini
16:37
jadewang has quit [Ping timeout: 256 seconds]
16:38
mort___ has joined #sandstorm
16:43
joshbuddy has joined #sandstorm
16:49
pixelport has quit [Ping timeout: 252 seconds]
16:55
NOTevil has joined #sandstorm
17:20
pixelport has joined #sandstorm
17:33
jadewang has joined #sandstorm
17:38
jadewang has quit [Ping timeout: 264 seconds]
17:39
jadewang has joined #sandstorm
17:47
asmyers has quit [Write error: Broken pipe]
17:47
asmyers has joined #sandstorm
17:48
asmyers has quit [Read error: Connection reset by peer]
17:48
asmyers has joined #sandstorm
18:20
<
tdfischer >
paulproteus: there's a pile of sandstorm stickers here at noisebridge from the librarian conference
18:20
<
tdfischer >
I have no idea who brought them
18:21
<
paulproteus >
tdfischer: Presumably Jack Singleton
18:21
<
paulproteus >
Or Rosalie
18:21
<
tdfischer >
that is an amazing last name
18:22
<
paulproteus >
Tolentino
18:22
<
tdfischer >
obviously Jack has no parents
18:22
<
paulproteus >
Bizarrely there are multiple Jack Singletons.
18:22
<
tdfischer >
thats a bad code smell!
18:24
<
paulproteus >
tdfischer: Also hi how do I help you achieve the next Sandstorm-related thing you want to achieve?
18:25
<
tdfischer >
pay my rent for the next few months
18:25
<
tdfischer >
thats one way to do it
18:25
<
tdfischer >
you could also give a 5mof talk about sandstorm this month
18:25
<
tdfischer >
which would achieve my goal of getting more people to use it
18:26
<
tdfischer >
and also one less slot to fill
18:26
<
paulproteus >
Date?
18:27
YuviPanda is now known as SaaadPanda
18:27
<
paulproteus >
Sorry to hear it, SaaadPanda
18:28
<
SaaadPanda >
thanks paulproteus
18:28
<
SaaadPanda >
I just found some terrible perl code I will have to maintain
18:34
<
tdfischer >
paulproteus: third thursday
18:34
<
tdfischer >
so the 16th at 8p
18:44
SaaadPanda is now known as YuviPanda|zzz
18:49
jadewang has quit [Ping timeout: 265 seconds]
19:11
jadewang has joined #sandstorm
19:20
pixelport_ has joined #sandstorm
19:21
pixelport has quit [Read error: Connection reset by peer]
19:26
jadewang has quit [Ping timeout: 244 seconds]
19:26
joshbuddy has quit [Quit: joshbuddy]
19:27
jadewang has joined #sandstorm
19:29
joshbuddy has joined #sandstorm
19:41
natea has joined #sandstorm
19:45
<
dwrensha >
if `event` has a `data` field, why wouldn't it show up in the first JSON.stringify()?
19:46
<
mcpherrin >
dwrensha: I think properties can be non-enumerated, and there's also some deal with inheritence
19:46
<
mcpherrin >
data might be a member of event's prototype?
19:46
natea has quit [Quit: natea]
19:47
* mcpherrin
no expert at all
19:47
natea has joined #sandstorm
19:48
natea has quit [Client Quit]
19:52
<
dwrensha >
also, `"data" in event` evaluates to `true`
19:52
natea has joined #sandstorm
19:55
<
dwrensha >
ah, but `event.propertyIsEnumerable("data")` evaluates to `false`
19:58
<
dwrensha >
but "data" is indeed one of the enumerants if I do `for (var x in event) { ... } `
20:11
geofft has joined #sandstorm
20:12
pixelport_ has quit [Quit: Leaving]
20:17
asmyers has quit [Ping timeout: 264 seconds]
20:18
natea has quit [Ping timeout: 265 seconds]
20:31
natea has joined #sandstorm
20:44
natea has quit [Ping timeout: 256 seconds]
20:44
natea has joined #sandstorm
21:09
NOTevil has quit [Quit: ...]
21:27
jadewang has quit [Remote host closed the connection]
21:35
jadewang has joined #sandstorm
21:36
natea has quit [Quit: natea]
21:48
jadewang has quit [Ping timeout: 265 seconds]
21:50
jadewang has joined #sandstorm
22:00
jadewang has quit [Remote host closed the connection]
22:09
YuviPanda|zzz_ has joined #sandstorm
22:11
YuviPanda|zzz has quit [Read error: Connection reset by peer]
22:12
YuviPanda|zzz_ is now known as YuviPanda|zzz
22:32
<
dwrensha >
Hm. I guess Meteor.Error is maybe not actually intended to be thrown on the client side?
22:33
<
paulproteus >
Current Asheesh work queue:
22:35
<
dwrensha >
and I'm noticing that if they are thrown outside of methods on the client side, in Firefox you get a very unhelpful message
22:35
<
dwrensha >
"Error:" and that's it
22:36
<
kentonv >
dwrensha: I think Meteor.Error() exists mainly to allow you to set an HTTP status code when the error is transmitted from server->client
22:36
<
kentonv >
you can use it other places but there's no real reason to
22:37
<
dwrensha >
for me this is coming up because I want to use "check()"
22:37
<
dwrensha >
which seems to work the same way
22:37
<
kentonv >
you want to check() on the client side?
22:37
<
dwrensha >
i.e. it throws a Meteor.Error-like exception if the check fails
22:37
<
paulproteus >
* Figure out how to boot this Ubuntu 32-bit VM in libvirt/qemu so I can merge zarvox 's installer pull request
22:38
<
paulproteus >
* Figure out why my vagrant-spk gives me a shell script permission error, so I can package spacetalk
22:38
<
kentonv >
dwrensha: well, it seems like a Meteor bug if these errors print poorly in the console. There's no good reason it shouldn't work.
22:38
<
dwrensha >
kentonv: we are already calling check() on the client side in our postmessage eventListener
22:39
<
kentonv >
oh weird, Meteor.Error is documented as
_not_ taking a status code. I guess it changed at some point.
22:42
jadewang has joined #sandstorm
22:44
<
kentonv >
dwrensha: Arguably, the code which does check()s for postmessage inputs should be wrapped in try/catch and should return any error as a reply to the app.
22:50
<
dwrensha >
hm, yeah. It would be nice to know that postMessage requests always receive a response, and that's currently not the case.
22:59
jadewang has quit [Read error: Connection reset by peer]
22:59
jadewang has joined #sandstorm
23:07
jeffmendoza has quit [Remote host closed the connection]
23:47
<
zarvox >
2015-07-01 23:45:08 7f30387ca700 InnoDB: Error: Write to file (merge) failed at offset 0.
23:47
<
zarvox >
InnoDB: 1048576 bytes should have been written, only 880640 were written.
23:47
<
zarvox >
InnoDB: Operating system error number 0.
23:49
<
zarvox >
Umm. I have no idea how to further debug this, but it's blocking my attempt to see how hard packaging mattermost is.