| 00:21:00 | * | amadaluzia quit (Quit: ZNC 1.10.1 - https://znc.in) |
| 01:04:16 | FromDiscord | <nasuray> In reply to @soicbr "I just copied the": Best of luck! I can try to help if you run into more NixOS based Nim problems. (There aren't many of us) |
| 01:05:36 | FromDiscord | <soicbr> ok ^^ |
| 03:02:30 | * | skippy8 joined #nim |
| 07:10:51 | * | xet7 joined #nim |
| 07:53:12 | * | nisstyre quit (Server closed connection) |
| 07:53:32 | * | nisstyre joined #nim |
| 08:49:59 | * | beholders_eye joined #nim |
| 10:26:53 | FromDiscord | <.tokyovigilante> Can anyone suggest a good test framework that respects build products being stored in `outDir`? |
| 10:34:14 | * | beholders_eye quit (Ping timeout: 258 seconds) |
| 11:57:50 | FromDiscord | <TӨMΛ ☠> Was something changed across Nim 2.0.0 and 2.2.4 that now makes Nimble's git error "too many arguments" if your directory has a space between?↵I've never had issues with 2.0.0, but setting 2.2.4 few minutes ago, it won't let me install anything now |
| 11:58:25 | FromDiscord | <nnsee> regression |
| 11:58:50 | FromDiscord | <nnsee> can you do a `git bisect`? |
| 12:00:06 | FromDiscord | <TӨMΛ ☠> I mean, it's not a repository issue, I just run the terminal to install a library after setting up proper PATH |
| 12:00:15 | FromDiscord | <TӨMΛ ☠> (edit) "I mean, it's not a repository issue, I just run the terminal to install a library after setting up proper PATH ... " added "for 2.2.4" |
| 12:00:15 | FromDiscord | <nnsee> i understand |
| 12:00:36 | FromDiscord | <nnsee> i meant a `git bisect` on the nim compiler, looking for the breaking change between 2.0.0 and 2.2.4 |
| 12:05:00 | FromDiscord | <nnsee> I would do it myself, but I cannot reproduce the issue myself |
| 12:05:07 | FromDiscord | <nnsee> seems to work fine for me on 2.2.4 and linux |
| 12:06:02 | FromDiscord | <TӨMΛ ☠> Oh. I'm not sure I know how to do it though, I'm somewhat green on how it works. And my Nim dirs are not git repos |
| 12:06:15 | FromDiscord | <TӨMΛ ☠> I have Windows, so probably this could be the reason |
| 12:10:20 | FromDiscord | <TӨMΛ ☠> I should finally make myself a repo where I will use git entirely through CLI, using IDEs for VCS really made me know only most basic stuff about git |
| 12:11:29 | FromDiscord | <nnsee> sent a long message, see https://pasty.ee/AwsqrBlX |
| 12:12:30 | FromDiscord | <nnsee> it sounds more complicated than it actually is. more than anything else it's just time consuming because you'll be building the compiler quite a few times |
| 12:15:49 | FromDiscord | <nnsee> you can automate the bisection by writing a script that builds the compiler and tries to reproduce the bug, and running `git bisect run [your script]` instead of manually marking commits good or bad, but that might be a bit too yak-shavy |
| 12:31:30 | FromDiscord | <nasuray> In reply to @toma400 "Was something changed across": Could also be a nimble specific issue... You might try installing v0.20.1 if that wasn't what already ships with 2.2.4 |
| 12:33:32 | FromDiscord | <nnsee> d'oh, i forgot this is likely a nimble-specific issue which is in its own repo |
| 12:33:45 | FromDiscord | <nnsee> so, do what i said, but replace "compiler repo" with "nimble repo" :p |
| 12:37:00 | * | nils` quit (Ping timeout: 256 seconds) |
| 13:08:18 | * | nils` joined #nim |
| 13:30:36 | FromDiscord | <TӨMΛ ☠> Thanks for detailed walkthrough anyway, it's really helpful 🙏 |
| 13:31:01 | FromDiscord | <TӨMΛ ☠> In reply to @nnsee "you can automate the": Also this sounds very much like me, I write scripts everytime for simplest tasks if this can save me even a small bit of time |
| 14:09:25 | * | amadaluzia joined #nim |
| 14:12:59 | FromDiscord | <lainlaylie> this bug is probably very common in nim code, as all the process spawning convenience functions in `os` and `osproc` encourage not properly quoting arguments |
| 14:21:53 | FromDiscord | <alehander92> In reply to @pmunch "Not quite sure what": ah just saw this answer now @pmunch 😄 |
| 14:22:22 | FromDiscord | <alehander92> wanted to genreate types from the DAP protocol json schema |
| 14:22:50 | FromDiscord | <alehander92> and wondered if you had some lib for that, but later i found out LSP's definitions are not published with json schema (like the DAP ones) |
| 14:23:48 | FromDiscord | <alehander92> (and since you worked on nim + lsp, you probably didnt have any common point with json schema in this case) |
| 14:26:59 | FromDiscord | <pmunch> JSON schema is a pretty loose definition though |
| 14:27:24 | FromDiscord | <pmunch> The LSP definitions are in TypeScript notation I believe |
| 14:27:35 | FromDiscord | <pmunch> So my jsonschema module is kinda based on that |
| 14:38:53 | * | beholders_eye joined #nim |
| 14:40:16 | * | yeti joined #nim |
| 15:16:10 | * | beholders_eye quit (Ping timeout: 248 seconds) |
| 15:27:42 | * | beholders_eye joined #nim |
| 17:23:04 | * | beholders_eye quit (Ping timeout: 248 seconds) |
| 17:45:15 | * | beholders_eye joined #nim |
| 17:50:05 | * | beholders_eye quit (Ping timeout: 258 seconds) |
| 18:12:52 | FromDiscord | <alehander92> @pmunch hm, maybe, but it works for me |
| 18:13:22 | FromDiscord | <alehander92> but i made a bit hacky custom generator script in javascript for several possible targets |
| 18:13:31 | FromDiscord | <alehander92> we might be able to produce some nim types soon |
| 18:13:40 | FromDiscord | <alehander92> (edit) "i" => "we" |
| 18:14:04 | FromDiscord | <alehander92> mostly focusing on a subset of things that are kinda sensible for our types |
| 18:14:27 | FromDiscord | <alehander92> it's kinda verbose so i agree it's best if the schema itself is produced by real types maybe? |
| 18:16:02 | * | beholders_eye joined #nim |
| 18:56:47 | * | xtr00 quit (Ping timeout: 258 seconds) |
| 19:01:26 | * | xtr00 joined #nim |
| 19:03:22 | * | beholders_eye quit (Ping timeout: 248 seconds) |
| 19:05:17 | * | beholders_eye joined #nim |
| 19:29:31 | * | beholders_eye quit (Ping timeout: 256 seconds) |
| 19:31:32 | * | beholders_eye joined #nim |
| 21:43:28 | * | xet7 quit (Remote host closed the connection) |
| 22:22:59 | FromDiscord | <pmunch> Real types are best types |
| 22:24:21 | FromDiscord | <pmunch> If you are writing JavaScript I would recommend just moving to TypeScript |
| 22:25:16 | FromDiscord | <pmunch> @alehander92 then you can look at jsonschema to interact with it |