01:26:31  * ryan_ramagequit (Quit: ryan_ramage)
01:51:23  * barduquit (Quit: Leaving.)
01:51:41  * ryan_ramagejoined
03:55:45  * tilgovi_quit (Ping timeout: 248 seconds)
04:09:03  * bardujoined
04:15:22  * barduquit (Quit: Leaving.)
04:45:20  * tilgovijoined
06:18:46  * tilgoviquit (Ping timeout: 256 seconds)
06:39:59  * `3rdEdenjoined
06:40:24  * tilgovijoined
07:28:35  * ebrightjoined
08:53:30  * lmjabreuquit (Ping timeout: 264 seconds)
09:38:08  * julianduquequit (Quit: zZzZ)
10:01:02  * tilgoviquit (Ping timeout: 252 seconds)
10:09:36  * julianduquejoined
10:53:12  * lmjabreujoined
10:54:51  * vmxjoined
12:58:52  * Samuel_Roldanjoined
13:12:31  * Samuel_Roldanquit (Quit: Samuel_Roldan)
13:32:05  * Samuel_Roldanjoined
13:33:26  * Samuel_Roldanquit (Client Quit)
15:27:58  * `3rdEdenquit (Remote host closed the connection)
15:29:02  * d2dchatjoined
15:39:03  * bardujoined
15:42:16  * ebrightquit (Ping timeout: 276 seconds)
15:50:10  * Samuel_Roldanjoined
15:58:54  * Samuel_Roldanquit (Ping timeout: 264 seconds)
16:27:06  * IrishGringoquit (Ping timeout: 264 seconds)
16:40:10  * IrishGringojoined
17:20:26  * bardupart
17:21:40  <ryan_ramage>JasonSmith: hey remember that badarg error we would get once in a while (tended to be on kanso apps)…I have some people experiencing it, do you have any recollection of what is/was causing it?
17:22:03  <ryan_ramage>it ususually required a couch restart…and it tended to be related to shows/lists
17:48:06  * IrishGringoquit (Ping timeout: 264 seconds)
17:48:08  * Samuel_Roldanjoined
17:57:14  * tilgovijoined
18:01:40  * tilgoviquit (Remote host closed the connection)
18:15:18  * Samuel_Roldanquit (Quit: Samuel_Roldan)
18:15:54  <dch>ryan_ramage: any chance the list or show might be taking "too long" ?
18:17:20  <ryan_ramage>dch: maybe. This is really hard to pin down. It works than all of a sudden all shows return a badarg. Restart couch and then its fine
18:17:36  <ryan_ramage>no data changes
18:18:41  <dch>is this one of mandric's ones?
18:18:56  <ryan_ramage>yeah. Caolan has seen it, and so have I
18:19:26  <ryan_ramage>we saw it on iris at first with the kanso site (and garden20), but we are seeing it on 1.3 on a fresh build
18:20:30  <julianduque>dch: yt? npm registry being slow again
18:20:31  <ryan_ramage>granted the kanso js is a little crazy at parts, but not sure what is happening on the erlang side to show such stateful behaviour
18:20:55  <ryan_ramage>unless the js interpreter (rhino) gets botched or something
18:31:36  * d2dchatquit (Remote host closed the connection)
18:44:55  * Samuel_Roldanjoined
19:27:09  * IrishGringojoined
19:39:40  * dch_joined
19:49:47  * d2dchatjoined
19:53:30  * IrishGringoquit (Ping timeout: 264 seconds)
19:55:35  * dch_quit (Quit: how now brown cow?)
20:48:07  * tilgovijoined
21:09:34  * dchchanged nick to dch_
21:23:27  * julianduquequit (Quit: Rocking at MedellinJS)
22:24:46  * d2dchatquit (Remote host closed the connection)
22:49:18  * Samuel_Roldanquit (Ping timeout: 264 seconds)
22:55:46  * tilgoviquit (Read error: Connection reset by peer)
22:56:55  * IrishGringojoined
23:05:41  * vmxquit (Quit: Leaving)
23:51:17  * d2dchatjoined
23:56:36  * d2dchatquit (Remote host closed the connection)
23:57:42  * IrishGringoquit (Ping timeout: 264 seconds)