code logs -> 2020 -> Sat, 28 Mar 2020< code.20200327.log - code.20200329.log >
--- Log opened Sat Mar 28 00:00:35 2020
00:04 catalyst [catalyst@Nightstar-v6lb30.cable.virginm.net] has joined #code
00:04 catalyst [catalyst@Nightstar-v6lb30.cable.virginm.net] has quit [Connection closed]
00:17 catalyst [catalyst@Nightstar-v6lb30.cable.virginm.net] has joined #code
01:07 Kimo|autojoin [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has joined #code
01:07 mode/#code [+o Kimo|autojoin] by ChanServ
01:11 Kimo|autojoin [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has quit [Ping timeout: 121 seconds]
02:01 Degi [Degi@Nightstar-qhsd30.dyn.telefonica.de] has quit [Ping timeout: 121 seconds]
02:02 Degi [Degi@Nightstar-o245nf.dyn.telefonica.de] has joined #code
02:03 Kimo|autojoin [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has joined #code
02:03 mode/#code [+o Kimo|autojoin] by ChanServ
02:07 Kimo|autojoin [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has quit [Ping timeout: 121 seconds]
02:38 catalyst_ [catalyst@Nightstar-dpv1cv.dab.02.net] has joined #code
02:45 Kimo|autojoin [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has joined #code
02:45 mode/#code [+o Kimo|autojoin] by ChanServ
02:50 Kimo|autojoin [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has quit [Ping timeout: 121 seconds]
02:51 catalyst [catalyst@Nightstar-v6lb30.cable.virginm.net] has quit [Connection closed]
04:01 Derakon is now known as Derakon[AFK]
04:38 Vorntastic [uid293981@Nightstar-h2b233.irccloud.com] has joined #code
04:38 mode/#code [+qo Vorntastic Vorntastic] by ChanServ
04:58 celticminstrel [celticminst@Nightstar-80avij.dsl.bell.ca] has quit [[NS] Quit: And lo! The computer falls into a deep sleep, to awake again some other day!]
05:01 Kimo|autojoin [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has joined #code
05:01 mode/#code [+o Kimo|autojoin] by ChanServ
05:05 Kimo|autojoin [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has quit [Ping timeout: 121 seconds]
06:37 Kimo|autojoin [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has joined #code
06:37 mode/#code [+o Kimo|autojoin] by ChanServ
06:41 Kimo|autojoin [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has quit [Ping timeout: 121 seconds]
06:48 catalyst_ [catalyst@Nightstar-dpv1cv.dab.02.net] has quit [The TLS connection was non-properly terminated.]
06:51 catalyst [catalyst@Nightstar-dpv1cv.dab.02.net] has joined #code
06:59 * Vorntastic discovers a novel integer sequence!
07:01 * Vorntastic tries to figure out how to actually calculate it efficiently
07:09 VirusJTG [VirusJTG@Nightstar-42s.jso.104.208.IP] has quit [Connection closed]
07:10 VirusJTG [VirusJTG@Nightstar-42s.jso.104.208.IP] has joined #code
07:10 mode/#code [+ao VirusJTG VirusJTG] by ChanServ
07:13
<&McMartin>
gratz?
09:07 catalyst [catalyst@Nightstar-dpv1cv.dab.02.net] has quit [Ping timeout: 121 seconds]
09:50 catalyst_ [catalyst@Nightstar-is45pa.dab.02.net] has joined #code
10:55 Kimo|autojoin [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has joined #code
10:55 mode/#code [+o Kimo|autojoin] by ChanServ
10:56 Kimo|autojoin is now known as Kindamoody
11:05 Kindamoody is now known as Kindamoody|afk
11:11 Emmy [Emmy@Nightstar-9p7hb1.direct-adsl.nl] has joined #code
11:49 catalyst_ [catalyst@Nightstar-is45pa.dab.02.net] has quit [Connection closed]
14:07 Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has joined #code
14:07 mode/#code [+qo Vornicus Vornicus] by ChanServ
15:21 Kindamoody|afk is now known as Kindamoody
16:09 Vorntastic [uid293981@Nightstar-h2b233.irccloud.com] has quit [[NS] Quit: Connection closed for inactivity]
17:04 celticminstrel [celticminst@Nightstar-80avij.dsl.bell.ca] has joined #code
17:04 mode/#code [+o celticminstrel] by ChanServ
17:05 celticminstrel [celticminst@Nightstar-80avij.dsl.bell.ca] has quit [[NS] Quit: KABOOM! It seems that I have exploded. Please wait while I reinstall the universe.]
17:13 celticminstrel [celticminst@Nightstar-80avij.dsl.bell.ca] has joined #code
17:13 mode/#code [+o celticminstrel] by ChanServ
17:39 * [R] starts to figgure out how this library works, is a little horrified
17:40
<&[R]>
So the protocol is fairly simple, you send a JSON object with an id field, and you get a reply back that has an object with an id field
17:40
<&[R]>
This library can handle you sending multiple concurrent requests (though only to a single host, so maybe it's not that bad)
17:41
<&[R]>
The requests can be done over HTTP, in which case the connection is closed after a single transaction
17:41
<&[R]>
So, the library builds the request, sends it out, and then drops all the connection state (letting the lower-level stuff handle all that)
17:42
<&[R]>
In that process it attaches its global handler to the reply stream
17:42
<&[R]>
In the global handler it just checks the id field of the reply and uses that to figgure out which call it needs to send the reply to
17:43
<&[R]>
This seems pretty sketchy to me, since it's trusting the other end a little bit too much
18:00
<&[R]>
Holy fuck, async/await in JS is practically useless
18:00
<&ToxicFrog>
There is a reason I scream ragefully in here every time I have to use it
18:02
<&[R]>
Also apparently you can't return an async closure from a function?
18:06
<&ToxicFrog>
I don't think I've ever tried that, but I wouldn't be surprised
18:07
<&ToxicFrog>
Remember that async/await are a compile-time transformation into continuation-passing style and there a lot of constructs (like `if await foo()`) the compiler isn't smart enough to transform and just rejects outright.
18:10
<&[R]>
Ah
18:10
<&[R]>
That'd explain why `console.dir(await n(...))` failed
18:11
<&[R]>
Love how half-assed this entire feature is
18:14
<&ToxicFrog>
Yeah, I think the best you can do there is `let foo = await n(...); console.dir(foo)` -- each `await` is a split point.
18:16
<&ToxicFrog>
This is the reason when playing a browser game that expected you to script it in JS I ended up spending a week getting Lua running inside it so I could use coroutines >.<
18:16
<&[R]>
lol
18:20 Derakon[AFK] is now known as Derakon
18:51 catalyst [catalyst@Nightstar-v6lb30.cable.virginm.net] has joined #code
21:39 * McMartin fixes his code, then discovers that the bugs he was seeing were not the bugs he fixed, but rather bugs in the test code.
21:43
<&[R]>
Ouch
21:45
<&McMartin>
Those bugs were all still real though!
21:47
<~Vornicus>
gnrk
22:47
<&[R]>
Which key corresponds to ^D?
22:48
<&[R]>
Yoss managed to accidentally make a file using less
22:50
<&ToxicFrog>
[R]: ctrl-D
22:50
<&ToxicFrog>
The leading ^ means ctrl
22:50
<&[R]>
Yeah
22:52
<&[R]>
Yeah, that key sequence works [s] [ctrl+d] [enter]
22:52
<&[R]>
I figgure he might have hit a single key though
22:53
<&[R]>
https://termbin.com/4c7k <-- me finding and removing the file
22:53
<&ToxicFrog>
Oh
22:53
<&ToxicFrog>
You mean which character does ^D send in contexts in which it actually sends a character
22:53
<&ToxicFrog>
And the answer is \x04, EOT
22:54
<&ToxicFrog>
`man ascii` is convenient for this; the upper case letters in the right column are on the same rows as the corresponding control characters on the left column
22:54
<&[R]>
You're right on that, but I was also aware of that
22:54
<&ToxicFrog>
If you want to actually type one in the terminal, ^V^D will put an actual ^D character in stdin rather than sending EOF.
22:55
<&[R]>
That's new to me, neato
23:02
<&ToxicFrog>
^V is the general purpose keystroke for "take the next key literally rather than interpreting it as an escape sequence or hotkey"
23:02
<&ToxicFrog>
Try ^V and then an arrow key sometime
23:03
<&[R]>
Yeah, it gives the ugly ^[[C mess
23:03
<&[R]>
Which I can get by ssh'ing into an openbsd box
23:23
<&ToxicFrog>
Yeah, that's the escape sequence the arrow key sends that (under normal circumstances) is interpreted by libreadline to move the cursor around and stuff
23:37 Yossarian [yoss@Nightstar-d7h8ki.org] has joined #code
23:41
< Yossarian>
I was lost but now I am found. Also, configuring weechat.
23:42 Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has quit [Connection closed]
23:51 Emmy [Emmy@Nightstar-9p7hb1.direct-adsl.nl] has quit [Connection closed]
--- Log closed Sun Mar 29 00:00:37 2020
code logs -> 2020 -> Sat, 28 Mar 2020< code.20200327.log - code.20200329.log >

[ Latest log file ]