<gchristensen>
just to confirm -- you understand the importance of having a high confidence in these IDs?
<infinisil>
gchristensen: Cool thanks, this might be helpful as another source
<infinisil>
gchristensen: Yeah
<gchristensen>
cool, I trust you, then, to make sure the added IDs are good :)
<gchristensen>
I added personal access token support to rf39: cargo run -- --credentials ./credentials-token.nix --maintainers ../nixpkgs/maintainers/maintainer-list.nix --metrics-delay 0 blame-author 2>&1 | tee blame-author (tee is important, lots of output ... ... some of which is wrong, you'll know it when you see it)
<infinisil>
the listing below is all handles and github usernames of people that don't have a githubId
<infinisil>
(generated by some nix code)
<infinisil>
I should also compare against the github id directly gotten from the github username via api..
<infinisil>
Basically: Looks for when $handle was first seen in the maintainer list, gets the commit of that, queries the github api for the author of the commit and the author of any associated PR, checks if they match, checks if the login matches the one in the maintainer file
<gchristensen>
nice!
<gchristensen>
beautiful!
<infinisil>
Ehhh I wouldn't call it beautiful, but it seems to work okayish lol
<infinisil>
(I wish you can copy paste with escape codes (when you forgot to tee to a file))
<infinisil>
About half of them are green, the other half I might have to do some manual work
<samueldr>
imagine the monkey paw wish: your terminal emulator copies as RTF
<samueldr>
(though in reality would be helpful!)
<infinisil>
Oh no
<abathur>
terminal on macos can copy with color
<samueldr>
shh, we don't say that word here
<abathur>
:]
<samueldr>
it's colour ;)
<abathur>
oh, fair
<samueldr>
(pulling your leg)
<abathur>
I prefer the british spellings myself
<danderson>
is there a process for bug triage when there's no PR associated? Have a thing I'd like to get input on, but I don't know if the best way to do that is to just send a PR and discuss there.
<infinisil>
Ugh it's already almost 4am, how long would it take me to go through the ~60 maintainer handles manually?
<infinisil>
Maybe not that long if I automate showing the commit/opening it in firefox
<gchristensen>
abathur: this is the coolest thing ever
<abathur>
heh
<abathur>
<3
ash_ has quit [Ping timeout: 265 seconds]
<abathur>
everyone's going to think you're talkingn about copying and pasting color escapes if you aren't careful
<gchristensen>
haha
<gchristensen>
for everybody else, abathur heard my call for a bash script linker and ... well
andi- has quit [Remote host closed the connection]
andi- has joined #nixos-dev
bhipple has quit [Remote host closed the connection]
abathur has quit [Ping timeout: 258 seconds]
orivej has quit [Ping timeout: 255 seconds]
abathur has joined #nixos-dev
cole-h has quit [Ping timeout: 255 seconds]
drakonis has quit [Ping timeout: 272 seconds]
abathur has quit [Ping timeout: 260 seconds]
<colemickens>
Thanks I hate it?
<lovesegfault>
colemickens: have you debugged Rust code in NixOS
<lovesegfault>
I am losing my mind
<colemickens>
I have stepped through some of the coed I'm working on from VS Code, yeah?
<colemickens>
Took some work though, I built the LLDB debugger extension I'm using from source (since, NixOS)
<colemickens>
From the other room there's some C? My projects inevitably have OpenSSL inside, but I've not debuged through that, so not sure if my limited experience can help?
<lovesegfault>
yeah, the thing is I want to step into some C code that is being called from Rust
<lovesegfault>
but then Nix is like "hah, no you can go die"
<jtojnar>
gnome terminal can save the buffer as HTML
<jtojnar>
s/save/copy/
<jtojnar>
I would expect other VTE-based terminals to support that as well
<jtojnar>
s/terminals/terminal emulators/
Emantor has quit [Ping timeout: 265 seconds]
Emantor has joined #nixos-dev
<tilpner>
gchristensen: Îs it okay for this (^) packet machine to have 7GB free in the root FS? It's been decreasing slowly for a while. Is it going to auto-GC and free up some space?
teto has joined #nixos-dev
<gchristensen>
good question :)
<gchristensen>
thanks for looking in to that, let's see ...
<gchristensen>
infinisil: bignaux was banned yesterday for being intentionally disrespectful to people in our community
<infinisil>
Ahh :o
cole-h has joined #nixos-dev
FRidh has quit [Quit: Konversation terminated!]
drakonis has joined #nixos-dev
<bhipple>
What do people's workflows look like for hacking on the NixOS manual and reading the docs from the cmdline/emacs/vim?
<bhipple>
So far I've come up with: `emacsclient $(nix-build nixos/release.nix -A manual.x86_64-linux)/share/doc/nixos/index.html
<bhipple>
and then running `shr-render-buffer` in emacs
<bhipple>
Previously I was trying firefox, but I prefer to have my normal navigation/regex search/buffer swap keybindings available so I don't have to context switch when reading/writing documentation vs. editing code
<bhipple>
just wondering if there's a treasure trove of tips somewhere
justanotheruser has quit [Ping timeout: 272 seconds]
justanotheruser has quit [Ping timeout: 272 seconds]
orivej has joined #nixos-dev
<infinisil>
Phew, I think I got partially typed modules to work!
<cole-h>
👀
<infinisil>
Lets you declare options when necessary, which then get type checked, but also lets you declare a fallback option for option paths that don't have an associated option