01:00:32  * AtumTquit (Remote host closed the connection)
04:06:45  * plutoniixjoined
04:49:38  * Guest59quit (Quit: My Mac has gone to sleep. ZZZzzz…)
05:09:35  * Guest59joined
05:18:54  * Guest59quit (Quit: My Mac has gone to sleep. ZZZzzz…)
10:09:33  * AtumTjoined
10:25:08  * mylesborinsquit (Quit: farewell for now)
10:25:39  * mylesborinsjoined
11:18:32  * dagobert___quit
11:18:54  * dagobert___joined
12:50:48  * plutoniixquit (Quit: Leaving)
13:40:39  * musgravejw_quit
13:40:53  * musgravejw_joined
13:58:37  <trungl-bot`>Tree closed by buildbot@chromium.org: Tree is closed (Automatic: "configure node.js" on "V8 Linux64 - node.js integration" sigurds@chromium.org)
14:01:38  <trungl-bot`>Tree closed by machenbach@google.com: Tree is closed (looking)
14:11:44  <trungl-bot`>Tree closed by machenbach@google.com: Tree is closed (agrieve working on fix)
14:14:18  * paulfryzelquit
14:14:36  * paulfryzeljoined
14:16:55  * mmarchiniquit
14:17:07  * mmarchinijoined
14:35:56  <trungl-bot`>Tree opened by machenbach@google.com: open
15:17:39  * bradleymeck_quit
15:18:02  * bradleymeck_joined
16:23:46  * Amadirojoined
17:17:01  * seventhjoined
17:38:07  * RT|Chatzillaquit (Quit: ChatZilla 0.9.86.1 [Firefox 2.0.0.22pre/2010030309])
17:53:38  <devsnek>does the unhandled rejection callback get messed up by async/await?
17:53:50  <devsnek>i'm seeing it being called when something throws inside an async function
17:53:55  <devsnek>but the async function is handled
17:54:15  <devsnek>it gets called for each time it travels up a level of async function
17:54:47  <devsnek>https://gc.gy/🎍🍆🚆.png
17:54:59  <devsnek>module compilation happens sync and throws
17:55:12  <devsnek>bubbles up a level, rejection handler triggers
17:55:17  <devsnek>bubbles up another level, handler triggers
17:55:27  <devsnek>then finally reaches my `.catch(console.error)` and logs
18:00:37  <caitp>devsnek: I believe there's a known issue where it gets screwed up if the rejection happens after an await
18:00:53  <devsnek>as long as its known...
18:01:23  <caitp>like, when an async function is first entered, and throws, it should eb detected as handed there's an outer try/catch
18:01:40  <caitp>but it's a little bit more complicated than that too
18:02:27  <devsnek>the theory isn't complex
18:02:37  <devsnek>just the hundreds of lines of implementation 😉
18:08:32  <caitp>well, the theory doesn't really work, for a mixture of different reasons
18:09:26  <caitp>at some point me or someone else will spend time to fix it properly
18:56:02  <trungl-bot`>Tree closed by buildbot@chromium.org: closed (https://ci.chromium.org/buildbot/client.v8.ports/V8%20Arm%20-%20debug%20builder/13575 from 44ea425ab1ededf8776d0ada3fa694f3db64fa29)
19:22:33  * seventhquit (Remote host closed the connection)
19:27:17  * Guest59joined
20:14:38  <trungl-bot`>Tree opened by buildbot@chromium.org: Tree is open (Automatic: ♩‿♩)
22:34:30  * RT|Chatzillajoined
23:13:35  * AtumTquit (Remote host closed the connection)
23:41:56  * plutoniixjoined