|
01:06
vendethiel joined
02:14
zakharyas joined
02:46
tadzik joined
06:51
Ven joined
07:18
brrt joined
07:20
Ven joined
09:00
harrow joined
11:04
Ven joined
11:08
Ven joined
11:22
brrt joined
11:32
Ven joined
12:23
Ven joined
12:32
harrow joined
12:39
brrt joined
12:50
Ven joined
14:03
Ven joined
14:16
harrow joined
14:20
Ven joined
14:31
Ven joined
14:55
Ven joined
|
|||
| hoelzro | o/ #moarvm | 15:10 | |
| timotimo | ohai hoelzro | 15:12 | |
| hoelzro | o/ timotimo | 15:15 | |
|
15:24
zakharyas joined
15:54
Ven joined
16:18
Ven joined
17:06
patrickz joined
|
|||
| hoelzro | if an async task being executed needs to delay its execution even further, is it safe to put a new async task on the queue? | 17:08 | |
| I guess what I mean to ask is if it's ok for the async thread to push something to the async queue, or if the queue will block when full and the async thread will deadlock itself | |||
| japhb | hoelzro: Two answers: 1. It should be. 2. It has historically been a problem when the task queue is longer than the thread pool is large | 17:09 | |
| I believe the latter is considered pure bug | |||
| hoelzro | hmm =/ | 17:10 | |
|
18:01
vendethiel joined
|
|||
| patrickz | libuv has moved their repository. github.com/joyent/libuv.git -> github.com/libuv/libuv I think that should be updated in .gitmodules (currently on wrong OS, thus can't create a PR or issue...) | 18:04 | |
|
18:34
Peter_R joined
18:38
vendethiel joined
19:48
brrt joined
21:18
colomon joined
22:07
TimToady joined
22:29
colomon joined
|
|||