andi- has quit [Remote host closed the connection]
andi- has joined #nixos-chat
<cole-h>
colemickens: By any chance, is redshift working for you? I think something broke it for me recently -- trying to narrow down if it's an Arch problem or a sway/wlroots/nixpkgs-wayland problem
waleee-cl has quit [Quit: Connection closed for inactivity]
<colemickens>
It's been working for me. I've been stopping it's service a lot lately
<cole-h>
Harrumph :( Thanks for the sanity check.
drakonis has quit [Quit: WeeChat 2.8]
abathur has quit [Quit: abathur]
cole-h has quit [Quit: Goodbye]
endformationage has quit [Quit: WeeChat 2.6]
abathur has joined #nixos-chat
drakonis_ has quit [Read error: Connection reset by peer]
drakonis_ has joined #nixos-chat
drakonis_ has quit [Read error: Connection reset by peer]
drakonis_ has joined #nixos-chat
<eyJhb>
Ahh, thanks for riminding me. I can finally use that service. Before with the DisplayLink, their software did not support it. So it only worked on 2 out of the three monitors. Whcih isn't useful
KeiraT has quit [Ping timeout: 240 seconds]
KeiraT has joined #nixos-chat
cjpbirkbeck has quit [Quit: cjpbirkbeck]
cjpbirkbeck has joined #nixos-chat
cjpbirkbeck has quit [Remote host closed the connection]
parsley936 has joined #nixos-chat
__monty__ has joined #nixos-chat
__monty_1 has joined #nixos-chat
__monty__ has quit [Ping timeout: 272 seconds]
__monty_1 has quit [Read error: Connection reset by peer]
__monty__ has joined #nixos-chat
__monty__ has quit [Ping timeout: 260 seconds]
__monty__ has joined #nixos-chat
__monty__ has quit [Ping timeout: 258 seconds]
__monty__ has joined #nixos-chat
bqv has joined #nixos-chat
<bqv>
emacs insists on giving non-autojoin rooms a different naming scheme...
<Taneb>
bqv: I looked a bunch for remote work (because Italy isn't exactly famous for its functional programming) but I couldn't find anyone hiring who'd accept me
<Taneb>
I'm also applying for a PhD
<bqv>
i imagine that'd help quite a lot
<bqv>
remote work seems the way forward, i'm looking too
<bqv>
but i have the luxury(?) of planning to stay here for the forseeable future
turlando has joined #nixos-chat
__monty__ has quit [Ping timeout: 264 seconds]
__monty__ has joined #nixos-chat
__monty__ has quit [Ping timeout: 246 seconds]
__monty__ has joined #nixos-chat
drakonis_ has quit [Read error: Connection reset by peer]
drakonis1 has joined #nixos-chat
waleee-cl has joined #nixos-chat
drakonis has joined #nixos-chat
drakonis1 has quit [Ping timeout: 272 seconds]
<savanni>
Hey, y'all. I found a bug in a derivation that I wrote, one that I'm surprised didn't show up before since it actually prevents installation. It's in the derivation only, not in the app that I packaged. Should I open a bug before submitting a PR? Should I bump the version of the derivation or leave that matching the application?
<__monty__>
Take my advice with a grain of salt. An issue isn't necessary, it's mostly extra noise for maintainers if you have a fix ready anyway. Don't change the version because that's about the package, not the derivation.
<savanni>
Thanks. You contribute more than I do, so I'll just take your advice and other people can salt it. :D
drakonis1 has joined #nixos-chat
drakonis_ has joined #nixos-chat
drakonis has quit [Ping timeout: 260 seconds]
cole-h has joined #nixos-chat
<pie_>
gchristensen: what was that fancy data structure stuff you were doing yesterday with python
<pie_>
the one where I said for a second i thought it's alloy
<pie_>
savanni: to say that a different way, if youre making a PR anyway, add that information to the PR, or I suppose ideally to the commit message
<gchristensen>
pie_: NixOS options, but converted to Python type definitions
<pie_>
ahha
<pie_>
oh those were python type definitions
* pie_
still hasnt gotten around to looking at mypy
<cole-h>
colemickens: Figured out my problem with gamma. I hadn't updated in a while and it looks like there've been some wlroots changes to gamma stuff. Rolled back to the 1 May version from nixpkgs-wayland and all is well(ish) again.
<Gaelan>
srhb i mean surely there are some safety critical systems out there compiled with gcc
<srhb>
Surely not!
<srhb>
(Yes, of course. :P)
<MichaelRaskin>
Frankly, what's scary is not the amount of warnings inside GCC
<MichaelRaskin>
What's scary is the optimisations it makes…
evax has joined #nixos-chat
<andi->
Is anyone else failing to follow issues created for their packages since there is no way to query for them and no way for users to specify a package and thus notify (not manually mention...) maintainers? It is really upsetting that I do have to regulary search through our issues and manually filter because the search is just not good enough :(
turlando has quit [Remote host closed the connection]
<gchristensen>
andi-: yes definitely it is so hard
<andi->
I am tired of complaining about GH but it keeps on bugging me and the worst part is that I can't contribute to make it better besides writing the support more tickets. This isn't how (F)OSS development should look like :(
<MichaelRaskin>
It is also just in terms of scope not supposed to be a real issue tracking system
<andi->
Yeah and our community is stuck on the platform or add stuff to it since it is (very) hard to get that connection right.
<andi->
I can't recal what I thought when I wrote `or` there.. it mae so much sense
<emily>
andi-: yeah, it sucks. I think the best approach is to watch the nixpkgs repo, get all issues by email, and filter the relevant ones
<emily>
the problem I ran into doing that is that you can no longer subscribe to individual threads meaningfully in the GitHub UI
<emily>
maybe I should have a separate GitHub account just for catch-all notifications :|
<andi->
You can configure addresses per repository
<emily>
yeah, but there are a lot of nixpkgs issues I want to watch that wouldn't match my filters
<emily>
but if you're "watching" a repo, you can't watch an issue explicitly on top of that
<emily>
(if you could, you could distinguish the two via the github email headers for filters, but it won't let you)
<emily>
"subscribe" to an issue I guess I should say, that's the term used in the UI
<andi->
IIRC subscribed@noreply.github.com will be CC'ed on those
<andi->
That is what I use to filter through those mails
<andi->
But yeah that would then apply to all the mails :/
<emily>
hm, the last time I watched nixpkgs every issue showed as "Subscribed because you're watching this repo" with no way to hard-subscribe to it more than that
<emily>
maybe there's a twiddle in the UI I was missing
<andi->
usually you can ask users to contribute to fix an issue with the software they are complaining about.. Here I can't do much but invest in software that is useless outside of their proprietary garden
<cole-h>
emily: You could unsubscribe and then manually subscribe. I think that's worked for me before.
<emily>
I guess the most practical solution is maybe a GitHub bot that could automatically request review from people who signed up to match certain search terms
<emily>
the other issue I had was that there's no way to subscribe via email but not notifications interface
<emily>
so my github notifications UI would become completely useless as it fills with all of nixpkgs
<cole-h>
Does being assigned to an issue notify the assignee?
<cole-h>
If so, maybe that could be added to ofborg -- match on the specified components (if any) and assign maintainers?
<cole-h>
Just an idea, though I don't know if we would want that in borg...
<cole-h>
Since there's no way to attach them to specific files
<pie_>
wait wrong chan
<__monty__>
Hmm, true. Guess I was thinking if you linked to a section of a file but then, no one does that...
<cole-h>
Yeah, that's way too much effort
<cole-h>
Even asking people to fill in the affected components and ping maintainers doesn't always bear fruit..
<MichaelRaskin>
emily: you will be subscribed but not participating
<MichaelRaskin>
And you can mass-done all of Nixpkgs stuff
<MichaelRaskin>
Source: never nusubscribed from entire Nixpkgs
<qyliss>
Are you sure you can't subscribe email-only?
<qyliss>
I'm pretty sure I have that
<qyliss>
it even hides the bell in the navigation bar
<emily>
there seems to be a setting to for "Watching – Notifications for all repositories, teams, or conversations you’re watching."
<emily>
but I don't want to get rid of all the notifications for watched repositories, since I watch a lot of repositories specifically to get the notifications
<emily>
I don't see any per-repo settings
<qyliss>
I guess I do have it disabled globally
<gchristensen>
Argument 1 to "runtime_checkable" has incompatible type "Type[State[Any]]"; expected "Type[State[Any]]" cool cool cool
<cole-h>
🤔🤔🤔
<cole-h>
Actually wat
<andi->
a type of type?
<samueldr>
I see gchristensen has cloned mypy, is it types on mypy?
<MichaelRaskin>
gchristensen: well, in nix a function is not equal to itself, why cannot types do the same?
<cole-h>
Speaking of GH notifications, I'm a little angry I can't use the `-` operator to exclude something from a filter.........