sphalerite changed the topic of #nixos-dev to: NixOS Development (#nixos for questions) | NixOS stable: 20.03 ✨ | 20.09 ZHF: https://discourse.nixos.org/t/nixos-20-09-zero-hydra-failures/8928 | https://hydra.nixos.org/jobset/nixos/trunk-combined https://channels.nix.gsc.io/graph.html | https://r13y.com | 20.03 RMs: worldofpeace, disasm; 20.09: worldofpeace, jonringer | https://logs.nix.samueldr.com/nixos-dev
hexa- has joined #nixos-dev
Havelock has joined #nixos-dev
<Havelock> Hi all, I believe I found a bug in the vscode extension builder: it assumes the extension archive contains only one directory. This is however not the case for all extensions, which makes the install fail with a "unpacker produced multiple directories" in that case. I would like to solve that, and I'm looking for help?
<V> Havelock: set sourceRoot
<Havelock> Could you elaborate a bit?
_ris is now known as ris
justanotheruser has joined #nixos-dev
ris has quit [Ping timeout: 260 seconds]
teto has quit [Ping timeout: 244 seconds]
cole-h has quit [Ping timeout: 260 seconds]
tilpner_ has joined #nixos-dev
tilpner has quit [Ping timeout: 272 seconds]
tilpner_ is now known as tilpner
justanotheruser has quit [Ping timeout: 244 seconds]
hexa- has quit [Quit: WeeChat 2.9]
hexa- has joined #nixos-dev
Scriptkiddi has quit [Quit: killed]
ajs124 has quit [Quit: killed]
das_j has quit [Quit: killed]
Scriptkiddi has joined #nixos-dev
ajs124 has joined #nixos-dev
das_j has joined #nixos-dev
alp_ has joined #nixos-dev
alp_ has quit [Ping timeout: 272 seconds]
orivej has joined #nixos-dev
justanotheruser has joined #nixos-dev
saschagrunert has joined #nixos-dev
cole-h has joined #nixos-dev
Cale has quit [Ping timeout: 246 seconds]
Cale has joined #nixos-dev
alp_ has joined #nixos-dev
saschagrunert has quit [Read error: Connection reset by peer]
saschagrunert has joined #nixos-dev
cole-h has quit [Quit: Goodbye]
teto has joined #nixos-dev
matthewbauer has left #nixos-dev ["Kicked by @appservice-irc:matrix.org : Idle for 30+ days"]
alp_ has quit [Ping timeout: 272 seconds]
alp_ has joined #nixos-dev
orivej has quit [Ping timeout: 260 seconds]
orivej has joined #nixos-dev
<domenkozar[m]> I wonder much much negative narinfo cache really saves time
<domenkozar[m]> niksnut: do you remember the motivation?
<JJJollyjim> A lot more if you live on the other side of the world from the origin server
<domenkozar[m]> but I wonder how useful it is, how often do you want to build something twice but you don't?
<niksnut> all the time
<niksnut> e.g. queryMissing
<domenkozar[m]> queryMissing?
<niksnut> or printMissing
<domenkozar[m]> niksnut: what do you mean by all the time?
<niksnut> so any nix-build will first query what needs to be built/downloaded, and then it will do it again
<domenkozar[m]> so really we need a negative cache that would live inside one Nix invocation?
<niksnut> so if you don't cache negative lookups, all the negative lookups will be done twice
<domenkozar[m]> I understand that within Nix that might be cached either way, but beyond two nix-build calls I don't see any reason
<domenkozar[m]> either way == positive+negative
<domenkozar[m]> I've opened https://github.com/NixOS/nix/issues/4028
<{^_^}> nix#4028 (by domenkozar, 9 seconds ago, open): NarInfo negative binary cache lookups should be in-memory
<domenkozar[m]> managed to reach birthday paradox on my nix store
<domenkozar[m]> do I get a cookie?
<gchristensen> the other birthday person got the cookie :(
<gchristensen> what fs?
<domenkozar[m]> ext4
<domenkozar[m]> /nix/store/009ldwn83d5mp14wx9p0lg0fm6v4d7vz-lens-family-core-lib-lens-family-core-2.0.0/lib/x86_64-linux-ghc-8.8.4/lens-family-core-2.0.0-7VYghidBzxz1fJVkkHxuW6/Lens/Family: copyFile: resource exhausted (No space left on device)
<gchristensen> not inodes?
<domenkozar[m]> nope
<gchristensen> nice
<domenkozar[m]> 1TB SSD considered harmful :P
<gchristensen> how about legacy filesystems considered harmful :P
<domenkozar[m]> heh
<domenkozar[m]> legacy options on legacy filesystems
<domenkozar[m]> wait, I actually have btrfs
<domenkozar[m]> What has happened is that the filesystem has allocated all of the available space to either data or metadata, and then one of those has filled up (usually, it's the metadata space that does this). For now, a workaround is to run a partial balance:
alp_ has quit [Ping timeout: 260 seconds]
<domenkozar[m]> modern fs considered harmful
* domenkozar[m] pets ext4
<gchristensen> this doesn't make sense
<tokudan> btrfs has some logical issues like that. still not production ready, i think
<domenkozar[m]> https://btrfs.wiki.kernel.org/index.php/Problem_FAQ#I_get_.22No_space_left_on_device.22_errors.2C_but_df_says_I.27ve_got_lots_of_space
<gchristensen> how are you hitting the birthday problem on a filesystem which supposedly supports 18,446,744,073,709,551,616 files
<domenkozar[m]> seems like it's not that, but that metadata took a lot of space
<gchristensen> seems completely wild to me
<gchristensen> domenkozar[m]: disappointing, at any rate :)
<tokudan> btrfs needs regular rebalances if it's heavily used
<gchristensen> gotcha
orivej has quit [Ping timeout: 272 seconds]
lewo has joined #nixos-dev
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 264 seconds]
alp_ has joined #nixos-dev
arianvp has quit [Quit: WeeChat 2.7.1]
arianvp has joined #nixos-dev
<domenkozar[m]> I should really not rely on df :)
<gchristensen> the fancier your fs, the more df lies
<cransom> preach.
cole-h has joined #nixos-dev
<Ox4A6F> Hey garbas: In [nixos-homepage#506] the asciinema-demo lines starting with "[nix-shell]$" aren't typed but appear instantly. Is there a way to type these lines as intended?
<gchristensen> nobody types those lines
orivej has joined #nixos-dev
puckipedia has joined #nixos-dev
puck has quit [Ping timeout: 256 seconds]
puckipedia is now known as puck
alp_ has quit [Ping timeout: 272 seconds]
saschagrunert has quit [Quit: Leaving]
alp_ has joined #nixos-dev
ris has joined #nixos-dev
immae_ has quit [Quit: WeeChat 2.9]
immae has joined #nixos-dev
alp has joined #nixos-dev
alp_ has quit [Ping timeout: 272 seconds]
rajivr has quit [Quit: Connection closed for inactivity]
bennofs has quit [Ping timeout: 264 seconds]
bennofs has joined #nixos-dev
<samueldr> do we want to adopt a policy for version numbers for stable packages that gets updated through patches?
<samueldr> #98171 for reference
<{^_^}> https://github.com/NixOS/nixpkgs/pull/98171 (by superherointj, 53 minutes ago, open): dmidecode version bump to 3.2.8
<samueldr> dmidecode, from upstream, does not release updates to software, but they recommend patches
<samueldr> see the "Download" section to the right https://www.nongnu.org/dmidecode/
<samueldr> AFAIUI the issue for this particular user is that `nix-env` does not upgrade the package in that situation
jtojnar has joined #nixos-dev
<jtojnar> can we just make nix-env always update when the derivation changes?
<jtojnar> if we cannot let it die altogether
<gchristensen> tbh it probably should always update, since an update to run-time deps might fix a serious security issue and go unfixed
<jtojnar> 👍️
<samueldr> that's what I think too
<samueldr> so should we move this PR forward by rejecting it stating that for the time being they need to work around their issue by re-installing dmidecode explicitly?
__monty__ has joined #nixos-dev
<ris> am i the only one that can't push to github ATM?
<puck> ris: are you using https or ssh?
<ris> ssh
<gchristensen> I can push
<cole-h> Anybody familiar with the Nix codebase (or maybe this is a C++ style thing): if I'm adding a `std::set<std::string>` of something, do I just declare it in the header, or do I make it `extern` and declare it in the .cc file?
<cole-h> Oh, maybe it needs to be extern to be usable in the different libraries...
<ris> hmmmmmmmmmmmmm maybe just my connectivity
ris has quit [Read error: Connection reset by peer]
alp has quit [Ping timeout: 272 seconds]
__monty__ has quit [Quit: leaving]
alp has joined #nixos-dev
<hexa-> with systemd, is there a way to run a service as non-root when the service wants to set sysctls?
<julm> hexa-: maybe using the right capabilities
<julm> using CapabilityBoundingSet= and AmbientCapabilities=
<julm> CAP_SYS_ADMIN, if this is up to date: https://lwn.net/Articles/284185/
<cole-h> make
<cole-h> oops
<cole-h> Wrong window :D
<hexa-> julm: yeah, I'm wondering if thatn is worth it
<hexa-> julm: hm no, that's not doing it
alp has quit [Ping timeout: 272 seconds]
<hexa-> julm: that change is not upstream … sad.
orivej has quit [Ping timeout: 256 seconds]
<julm> hexa-: is it just a one time change at startup or is it changing many times during the runtime of the service?
<hexa-> one time, but it's not a dealbreaker
<hexa-> i'm not going to patch it downstream
<julm> because for the sysctl you linked, maybe you could just set them yourself in boot.kernel.sysctl or in a preStart
<hexa-> yeah
<hexa-> it compares was and want
<hexa-> so if I preset them I can get around that, true
alp has joined #nixos-dev
<julm> maybe setting */conf/default/* also
<hexa-> indeed that works
<hexa-> presetting them
<hexa-> onto the next issue :)
<julm> :D
<hexa-> nay, can't do it without upstream support :)
<hexa-> that mis-indented upstream portion doesn't chheck has/want
<hexa-> I had a dream
<hexa-> → Overall exposure level for babeld.service: 2.3 OK 🙂
<julm> nice score
<hexa-> finish at 2.2
<hexa-> yeah, talked about selinux tonight
<hexa-> decided to invest more in secure systemd units for now
<julm> so do I
<{^_^}> #93457 (by ju1m, 8 weeks ago, open): apparmor: fix and improve the service
<{^_^}> #97740 (by ju1m, 6 days ago, open): nixos/tor: improve type-checking and hardening
<hexa-> \o/
<hexa-> was hoping we'd get the postfix/dovecot/rspamd services locked down in 20.09
<hexa-> but they're tough jobs to finish
<julm> oh, I haven't looked into that yet, cool
<{^_^}> #93305 (by tnias, 9 weeks ago, open): nixos/postfix: systemd sandbox
<{^_^}> #93293 (by tnias, 9 weeks ago, open): nixos/rspamd: add sandbox