waleee-cl has quit [Quit: Connection closed for inactivity]
<bqv>
ashkitten: wh are some bugs?
tsruser has joined #nixos-chat
tsruser has quit []
tsruser has joined #nixos-chat
tsruser has quit [Client Quit]
tsruser has joined #nixos-chat
<bqv>
philipp[m]: Discount donald knuth
worldofpeace_ has joined #nixos-chat
tsruser has quit []
tsruser has joined #nixos-chat
tsruser has quit []
worldofpeace_ has quit [Quit: worldofpeace_]
evanjs has quit [Read error: Connection reset by peer]
evanjs has joined #nixos-chat
<philipp[m]>
bqv: > Discount Van Gogh
<philipp[m]>
Still pretty good
evanjs has quit [Read error: Connection reset by peer]
evanjs has joined #nixos-chat
tsruser has joined #nixos-chat
tsruser has quit [Ping timeout: 264 seconds]
drakonis has joined #nixos-chat
<eyJhb>
If any Thrips crawls under my NEW SCREENS and dies, I will be soo pissed ( https://en.wikipedia.org/wiki/Thrips - Tordenfluer / Thunder Flies in Danish)
tsruser has joined #nixos-chat
drakonis1 has joined #nixos-chat
<eyJhb>
Can't even remember who hosts my VPS infinisil
<infinisil>
lol
<eyJhb>
Ahh. Had to run a wtfismyip.com for the ISP
<eyJhb>
My hardware config has detected hyper-v, but ...
<eyJhb>
Not sure if that is of any importance to me
<eyJhb>
,ping
<{^_^}>
pong
<eyJhb>
Lets see if the router survives
<eyJhb>
,ping
<{^_^}>
pong
<eyJhb>
YAY! :D
drakonis1 has quit [Quit: WeeChat 2.8]
<bqv>
> disorderfs.meta.description
<{^_^}>
"An overlay FUSE filesystem that introduces non-determinism into filesystem metadata"
<bqv>
For why?!
<joepie91>
bqv: chaos monkey>
<joepie91>
?*
<joepie91>
"disorderfs is an FUSE-based filesystem that introduces non-determinism into metadata, for example randomising the order in which directory entries are returned. This is useful for injecting and then detecting non-determinism in build processes."
<joepie91>
yep, chaos monkey
<bqv>
Lol
drakonis1 has joined #nixos-chat
drakonis has quit [Ping timeout: 265 seconds]
<eyJhb>
bqv: I want a FS that sends alert for writes/read outside of X specefied locations
<eyJhb>
vulnix returns so many vuls on a new 20.03 system
FRidh has quit [Ping timeout: 256 seconds]
FRidh has joined #nixos-chat
<bqv>
eyJhb: could do that with apparmor/selinux
<eyJhb>
Uhhhh
<eyJhb>
tmpfs + apparmor
<eyJhb>
/selinux
<eyJhb>
,locate bin dot
<{^_^}>
Found in packages: graphviz, graphviz-nox, graphviz_2_32
cole-h has joined #nixos-chat
iqubic has joined #nixos-chat
iqubic` has joined #nixos-chat
iqubic has quit [Ping timeout: 244 seconds]
iqubic` has quit [Ping timeout: 246 seconds]
iqubic` has joined #nixos-chat
iqubic` has quit [Remote host closed the connection]
iqubic has joined #nixos-chat
tsruser has quit [Ping timeout: 240 seconds]
tsruser2 has joined #nixos-chat
drakonis1 has quit [Ping timeout: 264 seconds]
tsruser2 has quit [Ping timeout: 256 seconds]
tsruser has joined #nixos-chat
drakonis has joined #nixos-chat
<ashkitten>
bqv: bugs in pipewire?
<bqv>
Yeah
<ashkitten>
sometimes an audio stream gets real crumbly
<ashkitten>
also, it doesn't seem to allow setting a default input device yet - only output
<ashkitten>
and its session manager only automatically connects one channel of a stereo device to a mono application
tsruser has quit [Ping timeout: 260 seconds]
<colemickens>
and apparently it can't do a2dp
<ashkitten>
also, sometimes it won't let you delete the connection an application started off with
<ashkitten>
they added bluetooth support somewhat recently
<colemickens>
heh the work around is to disable BT support, allegedly
<ashkitten>
oh
tsruser has joined #nixos-chat
<ashkitten>
anyways yeah. i'll be waiting a while to try pipewire again
<colemickens>
good thing screensharing in wayland is tied to it :P
<ashkitten>
heh
<ashkitten>
well, i can always use v4l2loopback and obs
<bqv>
A2dp is the call mode isn't it
<bqv>
Cause I could live without that
<bqv>
Might test it too
<hexa->
no, it's the media mode
<bqv>
The high quality one?
<hexa->
hfp is the call mode
<hexa->
yes
<bqv>
Oh yikes
<hexa->
also there is no high quality call mode
<bqv>
That's ungood
<colemickens>
it's bad, yeah, you don't want to listen to BT headphones over whatever it does support.
<hexa->
listen to music over bt headphones is fine, calls mostly aren't
<bqv>
I can't decide if thats a dealbreaker or not
<colemickens>
(I meant with the current pipewire state, sorry :s. It works great with regular pulseaudio, for me and my current headphones anyway)
<bqv>
Yeah I know
<adisbladis>
Tbh the bt audio situation is really bad
<adisbladis>
Even on pulseaudio
<adisbladis>
It only has SBC support out of the box
<adisbladis>
Ewww
<worldofpeace>
lol, I just played with nixUnstable and the new errors... I could've swore I heard like an angel singing 😂
FRidh has quit [Quit: Konversation terminated!]
<colemickens>
I accidentally downgraded, then re-upgraded and got to experience the joy a second time.
<worldofpeace>
colemickens: exactly. it's sorta like I've been living my nix life with a serious debugging handicap for a while
<worldofpeace>
and now I don't need a wheelchair
* colemickens
really needs to improve habits about updating master /before/ implementing the change instead of after and realizing someone else merged it hours ago :P
<samueldr>
colemickens: what about checking open PRs?
<samueldr>
*and* closed PRs :)
<colemickens>
bad habits. to be fair, it wasn't in master last night (though the PR was open at that point). just bad habits.
* colemickens
there's probably like `hub pr search` or something I could use
<bqv>
Errors in glorious technicolour
<joepie91>
worldofpeace: new... errors....?
<joepie91>
please tell me more
<joepie91>
do we finally have actually-actionable output?
<srhb>
They're prettier at least! Haven't tried getting "unknown undefined at undefined" yet, but I bet it's still doable with some effort.
<samueldr>
>
<{^_^}>
error: syntax error, unexpected ')', at (string):321:1
<samueldr>
hm
<srhb>
:P nice try
<samueldr>
not the one I hoped for
<samueldr>
> 1 + 1
<{^_^}>
error: syntax error, unexpected $undefined, expecting ')', at (string):320:2
<srhb>
Glorious.
<samueldr>
(though the bot obivously isn't using the new messages)
<joepie91>
lol
<joepie91>
can I have some screenshots?
<srhb>
I don't know, I find it so hard to make errors on purpose...
<samueldr>
basically, recent PRs from bburdette on the nix project are the work
* colemickens
is curious how many people have custom channels with custom sets of nixos tests enabled.
<srhb>
colemickens: Must it be channels?
<joepie91>
this makes me very happy \o/
<colemickens>
I switched to -small recently, and today seems like a number of things are broke. If I had hydra running on the ones I cared about I could pick them off during long builds, etc.
<joepie91>
this is already in nixUnstable, you say? what's the risk of switching Nix versions?
<srhb>
colemickens: Yeah, that works well :)
<colemickens>
srhb: no, I shouldn't have used that word :P
<srhb>
joepie91: Recently, segfaults. But as long as you're comfortable digging out an old nix you can recover :)
<colemickens>
I have been channel-less for very long, I guess --keep-going and a regular one of my builds.sr.ht jobs would work fine.
<srhb>
colemickens: Right. I used to have a local hydra that picked tests that I care for. :)
<colemickens>
(I love writing CI jobs for Nix stuff, btw, like another multiplier of my love for Nix)
<srhb>
I think some people still do that.
<colemickens>
srhb: lost interest or just moved back to unstable or why did you stop, just curious?
<samueldr>
I said it previously, nix is a force multiplier; and colemickens saying the word reminded me of it
<srhb>
colemickens: It was actually because I switched jobs to a non-nix one for half a year in a misguided moment.
<joepie91>
srhb: hmm, right. gonna wait for it to land in stable then I guess :P
<srhb>
joepie91: (fwiw it's fine here :P)
<srhb>
Since it's all merged with flakes now, I find it hard to believe it'll land before 21.03 at the earliest.
<srhb>
Then again, experimental features...
<joepie91>
I'm okay with that
<srhb>
My main gripe was how long it took me to find --print-build-logs
<srhb>
Speaking of which, I need to set that as default..
<colemickens>
wait what
<colemickens>
I had given up
<srhb>
lol
<srhb>
Well, I'm glad to share then ;-)
<samueldr>
I think you can get the new errors while still keeping the stable nix daemon, right?
<srhb>
Yep.
<bqv>
cheeky
<srhb>
Oh bother, it's not a nix.conf-setting? Bah.
rajivr has quit [Quit: Connection closed for inactivity]
<srhb>
colemickens: It's actually nicer than what we used to get from nix-build, it prefixes things beautifully.
<srhb>
huh, according to the release notes this was even in 2.3. I'm blinder than I thought.
<samueldr>
(I want "nix log $the_last_drv_that_failed_in_this_terminal", and I know it's not a trivial thing)
<srhb>
same :/
<colemickens>
okay, here's a question, what is everyone doing about the out paths not being written to stdout
<srhb>
Relying on result links like god intended.
<srhb>
Someone could sneak up on you and gc your thing!
<srhb>
:P
<bqv>
might be easier to just have nix log to the syslog, so you can just journalctl
<colemickens>
someone could sneak up on you and build two drvs at the same time in the same flake dir too though
<srhb>
I have permissions to guard against that :P
<samueldr>
bqv: doesn't help in getting the logs for the last .drv that failed for that terminal :)
<samueldr>
(but I don't disagree it would be a neat option)
<colemickens>
lol and you trust yourself more than I trust myself? lol
<srhb>
colemickens: Okay, point taken...
<samueldr>
--out-link $(some mktemp thingy)
<colemickens>
It's a real thing I hit while working on nixos-{cloud} where I was doing a really long image build and then started hacking on packages agian
<samueldr>
there, scripted in a safe* way
<colemickens>
samueldr: that's what I went with yeah
<colemickens>
out="$(nix-build ...)" still felt easier.
<bqv>
colemickens: nix shell and `echo $PATH`, normally
<bqv>
which is terrible, i know
<colemickens>
and to add to that, nix build .#some-flake-output is guaranteed to be a single out path!!
<samueldr>
definitely, using its stdout to get the out path felt like things just slid in place
<colemickens>
anyway, I guess it bothered me more before, seems not so bad after spitballing aloud.
<bqv>
there's .outPath
<bqv>
could nix eval it after
<bqv>
(i don't think nix eval'ing it is enough to build it)
<colemickens>
I don't do that anywhere.
<colemickens>
I do have this though: drv="$(set -euo pipefail; nix --experimental-features 'nix-command flakes' --pure-eval \
<colemickens>
there's no nix-instantiate equivalent AFAICT
<bqv>
what's that pipefail thing btw
<bqv>
i see it a lot in horrifying bash code
<colemickens>
cargo culted boilerplate that breaks things every once in a while but breaks more often when I don't have it
<colemickens>
tbf
<colemickens>
I think without it, `false | true` will silently succeed.
<bqv>
oh, hah
<colemickens>
you know, since I've bough into nix everywhere, maybe I could experiment with ion. I wonder if it pushes through some of the things I dislike about bashing.
<bqv>
what does ion have to do with nix?
<cransom>
isn't that one the wm's that requires recompiling rather than use a config file? i'd wager that's less painful on nix than most other things.
<colemickens>
bqv: nix -> nix-shell -> easy availabilty of ion -> safe usage of it in random projects that I'll be using nix in otherwise
<colemickens>
aka, I could use it for internal shell script tasks without anyone noticing/caring/etc
<colemickens>
if I were a better something I'd write python I guess.
* colemickens
actually got a github edit in before the email went out
<colemickens>
Screenshare in a firefox-pipewire build seems to just work if you have enable the existing xdg/pipewire options! woo
<bqv>
well, i have it installed
<bqv>
perhaps i'll try it
<eyJhb>
Just waiting for Firefox 80...
<eyJhb>
gchristensen: was there any way, we could inclue the patch for FF to be build on Hydra regarding policies, so that it could actually be useable? Would be nice if we could discuss that :) Or anyone for that matter, that has a opinion on it etc.
<drakonis>
i tried playing deltarune once and it was weird and bad
<bqv>
lmao
<drakonis>
adisbladis: i dunno m8 i wanna do that sometimes and not find out things broke
<bqv>
colemickens: yeah
<bqv>
i was missing the portals
<bqv>
oh
<colemickens>
bqv: mine maxes out at 20fps :|
<bqv>
also that
<bqv>
(the env vars)
<bqv>
Aug 06 22:53:24 delta pipewire[279028]: [E][000073689.744133][impl-module.c:281 pw_context_load_module()] "/nix/store/f8m3yrwxzmjwpcz8nkafdxwrw260pqaz-pipewire-0.3.7-lib/lib/pipewire-0.3/libpipewire-module-portal.so": failed to initialize: Cannot allocate memory
<bqv>
Aug 06 22:53:24 delta pipewire[279028]: [E][000073689.744145][daemon-config.c:202 pw_daemon_config_run_commands()] could not run command load-module: could not load module "libpipewire-module-portal": Cannot allocate memory
<bqv>
Aug 06 22:53:24 delta pipewire[279028]: [E][000073689.744148][main.c:123 main()] failed to run config commands: Cannot allocate memory
<drakonis>
relevant
<drakonis>
collabora has written its own pipewire components