| 24 Jul 2021 |
 abathur | In reply to @jaen:matrix.org
Hello, is this the right place for "nix is behaving very weirdly when trying to build a package flake output and I don't know why"? #nix:nixos.org | 14:41:41 |
 balsoft | Or #flakes:nixos.org | 15:20:32 |
| abathur | In reply to @abathur:matrix.org
I'll at least aspire to find some time to read over the changeset and take some notes, as well ~publicly acknowledging that I've been through this at least once and have notes that I'm happy to discuss in private/ephemeral forms. I'm leery of posting them in the open since I'd rather not risk playing any role in exacerbating/prolonging the tension/frustration around this changeset. | 18:48:10 |
| abathur | But I don't think that changes the next-step: getting the conditions people are hoping it would fix under test | 18:55:44 |
| 26 Jul 2021 |
|  babbaj joined the room. | 00:13:56 |
 pamplemousse | Is there any library linked statically in nix? | 22:49:35 |
| 27 Jul 2021 |
| balsoft | Not in the default distribution, but there is static-nix | 09:10:03 |
 Alyssa Ross | Redacted or Malformed Event | 09:16:49 |
| pamplemousse | What's the consensus on languages to be used for scripts?
So far, I have a couple of bash scripts to easily build / run the fuzzers I have so far.
But as I am making diverse harnesses (one exercising only the parsing, other parsing and evaluation, and later maybe other components - daemon...), with different sanitizers, those scripts are growing, and I want them to take options.
Now, I feel like using python with https://docs.python.org/3/library/argparse.html is a really neat way of providing a nice interface for my script (and also more maintainable than bash).
| 17:32:59 |
 Regnat | In reply to @pamplemouss_:matrix.org
What's the consensus on languages to be used for scripts?
So far, I have a couple of bash scripts to easily build / run the fuzzers I have so far.
But as I am making diverse harnesses (one exercising only the parsing, other parsing and evaluation, and later maybe other components - daemon...), with different sanitizers, those scripts are growing, and I want them to take options.
Now, I feel like using python with https://docs.python.org/3/library/argparse.html is a really neat way of providing a nice interface for my script (and also more maintainable than bash).
As long as it’s not required for building Nix itself, I think python is totally fine | 18:17:26 |
 andi- | Does Nix assume that paths are valid utf-8 or could they be utf-16 or whatever weird jap character set there might be? | 18:20:41 |
 tomberek | andi-: these checks (https://github.com/NixOS/nix/blob/master/src/libstore/path.cc#L5-L29) seem to indicate a limited character set | 18:29:24 |
| andi- | but that only applies to names of derivations not files within a folder, right | 18:30:29 |
| andi- | * but that only applies to names of derivations not files within a folder, right? | 18:30:31 |
| tomberek | correct, i'd presume file names inside a store-path are not so restricted.... time to test it! | 18:31:12 |
| tomberek | [tom@tsurf:~/temp]$ ls /nix/store/mv1iw4cg27fnavhshiwk642s0dwr047a-unicode/
☺
| 18:32:42 |
| andi- | nix-repl> builtins.readDir ./.
{ "👍" = "regular"; }
| 18:33:08 |
 sterni | andi-: at least syntactically paths are quite restricted, i. e. only ascii alpha numeric characters, no spaces etc. but you can always get around that by concatenating a string | 18:33:40 |
| sterni | andi-: in that sense you can have arbitrary encoding since nix doesn't care about string encoding as long as they don't contain any NUL bytes | 18:34:28 |
| sterni | but valid store paths are an issue of course | 18:34:38 |
| andi- | I am concerned about handling of names in e.g. NAR files but since those names always start with a byte size u64 I guess it could go well most of the time? Perhaps utf-16 could be a challenge if there is a 0 byte inbetween chars.. | 18:34:40 |
| andi- | The string functions (e.g. builtins.split) work on bytes instead of characters so I guess that is one of the limitations. | 18:41:19 |
| sterni | not sure what split has to do with paths? | 19:18:37 |
| sterni | on unix paths are just byte sequences so there shouldn't be an issue wrt that | 19:19:12 |
| sterni | I guess at least as your encoding doesn't allow for anything non ASCII to be mistaken as ASCII | 19:19:27 |
| sterni | * I guess at least as your encoding doesn't allow for any (part of a) non ASCII char to be mistaken as ASCII | 19:19:42 |
| andi- | In reply to @sternenseemann:systemli.org
not sure what split has to do with paths? imagine a combination of builtins.readDir and postprocessing the paths | 19:22:10 |
| andi- | Yeah, I think thinking of paths and strings in nix in general (?) as byte sequences is probably the best. | 19:23:15 |
| sterni | Can an unix path contain a literal '/'? If not, builtins.split should at least always work to separate the path components correctly | 19:29:43 |
| 28 Jul 2021 |
|  stick changed their display name from prusnak to stick. | 15:09:45 |
