jkprg

Activity Graph

Page 1 of 1

2018-10-05

[09:07:49] jkprg: has joined #ruby
[09:07:49] jkprg: has joined #RubyOnRails
[09:17:18] jkprg: Quit: jkprg

2018-10-04

[10:06:59] jkprg: has joined #ruby
[10:06:59] jkprg: has joined #RubyOnRails
[16:53:29] jkprg: Quit: jkprg

2018-09-06

[00:36:56] jkprg: Quit: jkprg
[00:50:25] jkprg: has joined #ruby
[00:50:25] jkprg: has joined #RubyOnRails
[01:51:46] jkprg: Quit: jkprg
[02:01:38] jkprg: has joined #ruby
[02:01:38] jkprg: has joined #RubyOnRails
[03:15:16] jkprg: Ping timeout: 246 seconds
[03:16:56] jkprg: has joined #ruby
[03:16:56] jkprg: has joined #RubyOnRails
[03:25:21] jkprg: Ping timeout: 252 seconds

2018-09-05

[16:56:31] jkprg: has joined #RubyOnRails
[16:59:13] jkprg: hi! any actioncable genius around? I have problem with message processing in AC. It seems to me messages are not processed in the same order as they arrived ftrom client.
[17:00:42] jkprg: moreover messages are not started to be processed in the same order. Is there any way how to serialize message processing for particular channel?
[17:18:07] jkprg: Quit: jkprg
[18:07:30] jkprg: has joined #RubyOnRails
[18:49:11] jkprg: Quit: jkprg
[19:25:34] jkprg: has joined #ruby
[19:25:34] jkprg: has joined #RubyOnRails
[19:52:31] jkprg: Quit: jkprg
[20:06:55] jkprg: has joined #ruby
[20:06:55] jkprg: has joined #RubyOnRails
[20:22:30] jkprg: Quit: jkprg
[20:24:40] jkprg: has joined #ruby
[20:24:40] jkprg: has joined #RubyOnRails
[20:31:49] jkprg: Quit: jkprg
[23:01:41] jkprg: has joined #ruby
[23:01:41] jkprg: has joined #RubyOnRails

2018-01-28

[00:05:10] jkprg: has joined #ruby
[00:13:16] jkprg: Quit: jkprg

2018-01-27

[23:51:52] jkprg: has joined #ruby
[23:52:33] jkprg: has left #ruby: ()

2017-05-31

[08:23:55] jkprg: Client Quit
[08:23:55] jkprg: has joined #ruby

2016-07-05

[08:07:09] jkprg: has joined #ruby
[08:07:09] jkprg: has joined #RubyOnRails
[09:42:01] jkprg: Quit: jkprg
[09:49:43] jkprg: has joined #ruby
[09:49:43] jkprg: has joined #RubyOnRails
[09:57:20] jkprg: Remote host closed the connection
[09:57:46] jkprg: has joined #ruby
[09:57:46] jkprg: has joined #RubyOnRails
[11:18:10] jkprg: Quit: jkprg
[12:24:30] jkprg: has joined #RubyOnRails
[12:24:31] jkprg: has joined #ruby
[13:19:21] jkprg: Quit: jkprg
[13:21:37] jkprg: has joined #ruby
[13:21:37] jkprg: has joined #RubyOnRails
[15:11:30] jkprg: Quit: jkprg
[15:19:57] jkprg: has joined #ruby
[15:19:57] jkprg: has joined #RubyOnRails
[15:31:22] jkprg: Quit: jkprg
[16:26:33] jkprg: has joined #ruby
[16:26:33] jkprg: has joined #RubyOnRails
[16:54:03] jkprg: Quit: jkprg

2016-01-20

[06:51:49] jkprg: has joined #RubyOnRails
[09:12:10] jkprg: Quit: Be back later ...
[09:51:27] jkprg: has joined #RubyOnRails
[09:52:43] jkprg: Read error: Connection reset by peer
[09:53:01] jkprg: has joined #RubyOnRails
[11:35:06] jkprg: Ping timeout: 240 seconds

2015-11-23

[12:46:35] jkprg: has joined #RubyOnRails
[12:46:58] jkprg: Client Quit