supersandro2000 has quit [Disconnected by services]
teto has quit [Ping timeout: 264 seconds]
supersandro2000 has joined #nixos-dev
<supersandro2000>
Can we disable the pytorch tests by default? they take forever to build.
<samueldr>
I don't think so because the default is what runs in hydra
<supersandro2000>
I could do an overlay but then I always need to compile it
rajivr has joined #nixos-dev
orivej has quit [Ping timeout: 272 seconds]
kalbasit has joined #nixos-dev
<abathur>
curious if anyone has thoughts/experience on ~organizing people interested in a certain language packaging ecosystem? (I guess mostly toward the ends of keeping everyone in the loop while patterns and practices are shaking out?)
<supersandro2000>
try to contact the others and maybe organize a little meet if there is something to talk about
maljub01 has quit [Ping timeout: 258 seconds]
maljub01 has joined #nixos-dev
fuzzypixelz has joined #nixos-dev
justan0theruser has quit [Ping timeout: 264 seconds]
<pie_>
Bear and intercept-build from scan-build, are two tools from László Nagy, that collects the compile options by intercepting calls to the compiler during the build. To have a complete compilation database a full build is required.
<Ericson2314>
pie_: ah i think i remember meson can generate those tooo
<pie_>
also something called ldlogger but im not sure what that does. basically, if interesting, probably see rest of page
<pie_>
also mildly intriguing thought: running statistics on compilation databases generated for a whole machine or whatever. dunno if that would be interesting
<abathur>
uhrm, I understand all of these words separately but I'm not 100% sure what they mean in this arrangement
<abathur>
example maybe?
<supersandro2000>
I want to queue nixpkgs-review shells and want them to be automatically executed but in an interactive shell where I can inspect the reports and post them by hand
<supersandro2000>
imagine something like task-spooler but with an bash -i
<abathur>
hmm
<abathur>
would you distinguish that from, say, for pr in {id,id,id}; do nixpkgs-review pr $id; done?
<abathur>
are you wanting them to run parallel but block for inspection?
<abathur>
er, $pr
<supersandro2000>
I don't want to run them in parallel
<supersandro2000>
something like nixpkgs-review pr 1 2 3..n but I want to instead n while it is running
<supersandro2000>
not sure how to do that
<supersandro2000>
I could append it to a file and read from the beginning of it
<abathur>
maybe I can work around the other way; the main things I get out of bashup.events are: 1) it adds a legible abstraction for declaring a hook/event interface that lets one or more developers build modular code (so, for example, it's easy for a shell module/library to publish before-command/after-command events for consumers to hook onto without clobbering each other
<abathur>
and 2) it can do some fun currying stuff, (register a one-time event specifying some of the function's eventual call arguments at registration time and the rest at emit time)
<abathur>
so in some sense it's just sugar, but in another sense it does make it easy to have a queue (though I think maybe you want bashup-events32 if you care about order?)
<fuzzypixelz>
what are some tasks that an unitiated person like me can start off with? do you have anything in mind that could potentially invlove lots of work, but isn't very invloved as I'm not familiar with the ins and outs of nixos yet
<abathur>
so you could do like `event once "gotta run 'em all" nixpkgs-review pr 1` and then `event once "gotta run 'em all" nixpkgs-review pr 2` and then `event emit "gotta run 'em all" and it should go run them all in sequence
<cole-h>
fuzzypixelz: How most people start out is reviewing PRs (e.g. if they build, if they function properly, etc), updating a package you're interested in, or creating a new package for something you're interested in'
<abathur>
should have like eh, a documentation slot machine; pull the lever, get a doc section, rate how decipherable it is
<abathur>
that feeds a triage list of least-decipherable documentation sections :)
<fuzzypixelz>
I've been browsing the PRs for a while and they call look very intimidating haha
<abathur>
it takes a bit to find your sea-legs
sorki has joined #nixos-dev
srk has quit [Ping timeout: 240 seconds]
sorki is now known as srk
<fuzzypixelz>
what is your usual workflow like?
<fuzzypixelz>
how do you test prs for example?
<samueldr>
1. look at the PR changes through github... see if it's something I can't handle
<samueldr>
2. then scrutinize the changes, however, for glaring obvious issues
<samueldr>
3. test the changes, hopefully the contributor left instructions to test changes
<samueldr>
when testing, you should also run the affected programs, ideally, and not only compile them
<samueldr>
but for changes affecting loads of packages, it can be hard
<fuzzypixelz>
samueldr: I mean, how do you actually test the changes? do you just build it on your own machine? do you pull the changes into a local repo?
<samueldr>
4. scrutinize changes again
<samueldr>
yeah, checkout the PR locally, nix-build what it affects
<samueldr>
I'm sure there's about as many strategies to review as there are reviewers, which is both good (no monoculture!) and not ideal (blind spots?)
<{^_^}>
#56943 (by emmanuelrosa, 1 year ago, open): setup hook of gobject-introspection in nativeBuildInputs does not run with strictDeps
<symphorien[m]>
yes ! it helps inadvertently regressing cross
<symphorien[m]>
also it's the default for python and maybe rust and go, iirc
<qyliss>
all of those
<siraben>
I see
<siraben>
Do we have cross comp checked in hydra?
<qyliss>
no
<siraben>
I'd also imagine it's a N*M type of problem where you have N platforms and M packages
<siraben>
oh man if there was an easy way to automate this
<siraben>
the issue is with packages that break their inputs into separate lines
<qyliss>
I think we don't need to test _every_ cross combination, as long as we're testing one of them so the cross-compliation infra is actually tested at all
<siraben>
or let-bind their inputs
<siraben>
qyliss: right.
<qyliss>
I broke cross last week because I was just working through fixing Hydra failures, and didn't think to test cross because there was no automated test for it.
<siraben>
I hate having to recompile a cross GCC each time, anyone have a cachix with a cross GCC?
<siraben>
tangential but emulators feature of cross is undocumented #106375
<samueldr>
sorry, I don't really have anything on-hand
<samueldr>
I don't know either your level of comfort with web development
<samueldr>
but, you know how, let's say, bootstrap tells you to use specific elements with specific class names to use some of their "components" or "layouts"?
<ryantm>
My web development comfort is pretty high.
<samueldr>
if you were doing that, without providing a way to replace the template, it'd make things harder to work on when implementing without bootstrap
<samueldr>
hm
<samueldr>
(sorry if that sounded a bit patronizing then)
<asbachb>
Can I limit a package for linux 64/i86 only?
<ryantm>
Probably need to add styling for all the Markdown elements though.
<samueldr>
ryantm: I guess that since your comfort with web dev is pretty high there's not much fear from me
<asbachb>
samueldr: Got it. Thanks.
<ryantm>
samueldr: I guess I need to make a version that doesn't output a complete HTML page, so it can be better embedded.
<samueldr>
let's see how your mmdoc thing evolves then :) haven't looked deeply into it, but on the surface it sounds great
<samueldr>
yeah, as long as you keep provisions around for extensibility, things should be just right
<samueldr>
which, AFAICT currently it's about right
<ryantm>
I'm glad you like the general idea. I could probably use some help with the styling at some point and I know you've done a lot of great work on nixos.org. My experience with CSS is not as good as the HTML/Javascript side of things.
<samueldr>
would be glad to help as much as I can
<ryantm>
samueldr: Thanks! Let me look into man pages, and polish it a bit more then I'll ping you
<samueldr>
sure :)
asbachb has quit [Remote host closed the connection]
<samueldr>
I'm having some trouble figuring out why `disabledModules` seems to fail to disable a module
yuuki_ has joined #nixos-dev
yuuki_ has quit [Ping timeout: 264 seconds]
<samueldr>
now I'm confused about `config.assertions` not triggering
<samueldr>
oh right, forgot that it's only on `toplevel` use
<samueldr>
ah, disabledModules is relative to <nixpkgs/nixos/modules>, not to <nixpkgs> (or equivalent without NIX_PATH)
<samueldr>
samueldr++ for missing the obvious
<{^_^}>
samueldr's karma got decreased to 301
<hexa->
I have a rust package that during startup tries to find libvulkan.so.1, but doesn't look int the right path: https://paste.lossy.network/IBKQ
<cole-h>
samueldr++
<{^_^}>
samueldr's karma got increased to 302
<cole-h>
hexa-: Probably have to patchelf --set-rpath
<hexa->
:<
<hexa->
I feared as much
<cole-h>
Or wrap with LD_LIBRARY_PATH
<cole-h>
Both are kinda ugly
<hexa->
ok, patchelf it is then
<ekleog>
hexa-: you can also try autoPatchelfHook, maybe it'll solve the issue for you
<hexa->
ekleog: thx, checking
<hexa->
it found like 6 deps, not all :)
<ekleog>
sad :'(
<samueldr>
if the thing is doing dlopen, I don't know that patchelf would find it
<hexa->
just libvulkan missing now!
<hexa->
its doing openat, read, fstat
<hexa->
and in case it doesn't find it, just a bunch of openats
<samueldr>
could be the syscalls dlopen does
<samueldr>
hm
<ekleog>
oh right there's dlopen, I was about to say that autoPatchelfHook should be able to find all the things if it didn't have bugs, but I had completely forgotten about that ./