waleee-cl has quit [Quit: Connection closed for inactivity]
<colemickens>
does AWS protect their spot data aggressively or something? I'm surprised there's not a website where I can go eyeball what the ARM machine prices are like
drakonis is now known as drakonis-
<danderson>
colemickens: no, you can see the history of spot prices in the EC2 console
<{^_^}>
#98917 (by lovesegfault, 1 day ago, open): klipper: init at 0.8.0
<cole-h>
o, I forgot to follow up, oops
<cole-h>
lovesegfault: And the `settings` stuff works as expected, yes? That's really my only source of hesitation lol
<cole-h>
(Even though I did suggest it...)
<lovesegfault>
let me do a final test to make sure
<cole-h>
lovesegfault: also, is there any reason for /etc/klipper.cfg to exist, rather than just pointing klippy to `${format.generate ...}` in the serviceConfig?
<cole-h>
e.g. are other, related tools expecting it to be there?
<lovesegfault>
Ah, I guess not!
<lovesegfault>
let me change that
<cole-h>
My only point for keeping it is that "it would be nice to be able to see the contents", but in that case, just open the file you define your settings in...
<lovesegfault>
Right, I just went through the same line of thought :D
<lovesegfault>
"maybe it's nice to... ah... nah"
<lovesegfault>
pushing changes...
<lovesegfault>
done
<lovesegfault>
testing
<cole-h>
I mean, it might be easier to `nvim /etc/klipper.cfg` rather than `nvim ~/.config/nixpkgs/...../klipper.nix`, but meh.
<cole-h>
lovesegfault: And my only nitpick with the derivation itself is: that `+ "/klippy"` looks janky -- does it (try to) build unrelated stuff if that is left off?
<lovesegfault>
So, here's the thing. Klipper is actually two projects under one repo and one name. Part of it is firmware you build and flash on a board. This is not being packaged because it's a weird derivation that needs to take in a config and spits out a binary. I packaged it externally here: https://github.com/lovesegfault/voronix/blob/master/klipper.nix
<lovesegfault>
the second part of klipper is a daemon that talks to the klipper-flashed board via serial and actual does all of the commanding, configuring etc. This is what the above PR packages
<lovesegfault>
I thought by making source be _only_ the daemon's dir within klipper's source it'd avoid confusion by future readers
<cole-h>
I see. Then maybe it would be more descriptive to package it as `pname = "klipper-daemon"` and `description = "The Klipper 3D printer daemon"`?
<cole-h>
Though this is getting really nitpicky lol
<lovesegfault>
I thought it was better to call it klipper since I think it's the only part of klipper that makes sense to be packaged _at all_
<lovesegfault>
I really don't see the firmware build being packaged, and if it ever is then I think it ought to be `klipper-firmware`
<cole-h>
Fair, but an idea for packaging the other one is something like we do for vim: allow it to be overridden to add plugins and whatnot (add configuration in this case)
<cole-h>
`klipper-daemon` and `klipper-firmware`... ;)
<lovesegfault>
alright, I'll change it after/if the test goes well
<cole-h>
And last question: should that `buildInputs` really be a `nativeBuildInputs`? Does this compile on aarch64 if not, do you know?
<lovesegfault>
will test as well
<cole-h>
Heh, don't mean to bully you into it -- it's totally up to you. That's just how I'd do it.
<lovesegfault>
hm, I'm in the right commit but it says the module doesn't exist
* lovesegfault
is confused
<lovesegfault>
oh
<lovesegfault>
I'm silly
<lovesegfault>
forgot to add it to the modules list
<cole-h>
Heh
<cole-h>
That'll do it
<cole-h>
lovesegfault: I'd also check the manpage to see if that description rendered properly -- not familiar with docbook so I can't tell
<lovesegfault>
looks like lib.formats isn't a thing?
<lovesegfault>
it's pkgs.formats?
<cole-h>
Another reason to love fish: alt+left and alt+right change historical pwds. e.g. cd /tmp, cd /, cd /etc, cd /lib and alt+left/right will switch between those in order :o
<cole-h>
lovesegfault: Yep, indeed.
<cole-h>
(Well, except /lib doesn't exist on NixOS, but whatever)
<lovesegfault>
testing...
f0x has quit [Ping timeout: 260 seconds]
flokli has quit [Ping timeout: 260 seconds]
f0x has joined #nixos-chat
flokli has joined #nixos-chat
<cole-h>
lovesegfault: Ping me again tomorrow and I'll r+ :) (Then it's on you to find someone to merge :P) Heading to bed.
cole-h has quit [Quit: Goodbye]
<sphalerite>
zfs yesterday: 585G resilvered, 10.41% done, 2 days 11:41:52 to go; zfs today: 933G resilvered, 16.59% done, 4 days 18:04:59 to go
<lovesegfault>
cole-h all tested and working :)
<sphalerite>
t/j #systemd
cjpbirkbeck has quit [Quit: Goodbye, take care]
f0x has quit [Quit: killed]
joepie91 has quit [Quit: killed]
<eyJhb>
lovesegfault: any images of the printer?
tilpner has joined #nixos-chat
tilpner has quit [Remote host closed the connection]
tilpner has joined #nixos-chat
tilpner has quit [Remote host closed the connection]
tilpner has joined #nixos-chat
tilpner has quit [Remote host closed the connection]
__monty__ has joined #nixos-chat
Guest27852 has joined #nixos-chat
f0x has joined #nixos-chat
<steveeJ>
spacekookie: FYI, I'm attempting to upgrade wally-cli to v2: https://github.com/zsa/wally/issues/72 I'm messaging you so you don't also attempt it and spend redundant time on it. I'll happily figure it out and will create a PR on nixpkgs once I'm ready
<{^_^}>
zsa/wally#72 (by steveeJ, 1 minute ago, open): Trying to build the CLI for v2 on Linux
<spacekookie>
steveeJ: go ahead, I don't really have the energy anyway
karolus has quit [Quit: karolus says ciao]
karolus has joined #nixos-chat
<eyJhb>
Is there any way I can get a dir relative to my shell.nix file? `something = ./something` will copy it into the store
<immae>
eyJhb: in the shellHook?
<immae>
Like adding `export something=$(pwd)/something` at the top of the shellHook
<eyJhb>
That would not be relative to the shell.nix, as I can do `nix-shell some/path/to/shell.nix`
<eyJhb>
Right?
<immae>
Hmm good question
<immae>
But: `something = builtins.toString ./something` also works
<immae>
"That would not be relative to the shell.nix," -> right
<eyJhb>
Uhh nice, that works :)
Guest27852 has joined #nixos-chat
Guest27852 has joined #nixos-chat
Guest27852 has quit [Changing host]
Guest27852 is now known as joepie91
<eyJhb>
Thanks immae :)
<immae>
you’re welcome!
<eyJhb>
Now I just need to figure out if I should spend my time using Jupyter! :p
<eyJhb>
ALso, my first real mkShell!
<eyJhb>
immae++
<{^_^}>
immae's karma got increased to 26
<eyJhb>
Also, wrong channel :|
obadz has quit [Quit: WeeChat 2.9]
<steveeJ>
has the idea been explored to allow new packages against a branch that is cached on hydra?
<steveeJ>
I'm currently packaging something that requires webkitgtk which takes a long time to build locally.
<steveeJ>
or am I just missing to configure cache lookups to hydra? :-D
julm has quit [Quit: leaving]
<__monty__>
I think the closest thing is the community builder, but that's arm only iirc.
<gchristensen>
I'm not sure what you're asking, steveeJ
<__monty__>
I interpreted it as having PRs built by CI and then cached for local testing/installation.
julm has joined #nixos-chat
tilpner has joined #nixos-chat
waleee-cl has joined #nixos-chat
<steveeJ>
gchristensen: my original question was if we could allow new packages into unstable or a similar branch that is reasonably covered by a publicly available binary cache
<gchristensen>
unstable gets new packages continuously
<steveeJ>
and are we allowed to introduce new packages and versions there without going through master?
<gchristensen>
no, but unstable tracks master
<steveeJ>
but see that doesn't help my issue ;-)
<gchristensen>
nixpkgs-unstable is based off of master's commit from 15 hours ago, and nixos-unstable is based on master's commit from 3 days ago
<gchristensen>
then I'm not understanding :x
<steveeJ>
well maybe we have to tie in the second part of my question
<gchristensen>
master is also continuously built by hydra and put in to cache.nixos.org
<steveeJ>
I'll elaborate a bit. I'm in the situation now where adding a new package requires me to build a large package. I think this could be improved. either I need to configure my system to make use of a cache, or something else needs to happen
<gchristensen>
you could check out the revision of a recent channel and add your patch, then PR from there?
<eyJhb>
Public builders!
<steveeJ>
yes I could, but we could also try to allow the reverse
<gchristensen>
steveeJ: how? you need to evaluate nixpkgs at a revision which has what you want built
<steveeJ>
I think I misread. are you saying I can PR to a channel branch?
<__monty__>
steveeJ: What do you think that would achieve? For all intents and purposes master *is* a channel branch.
<gchristensen>
no, you can check out the revision of nixpkgs-unstable, and add your package, and then PR to master
<gchristensen>
strictly speaking {nixpkgs/nixos}-unstable is always a commit which is a member of the history of master, and master is always ahead of the channel. so you can check out that revision, add your patch, build it based on the channel, and then PR to master and it'll apply cleanly (caveat for if someone changed the same thing you did)
<steveeJ>
__monty__: what I want to achieve is building locally on a revision that likely has all the build inputs cached
<__monty__>
Ah, then gchristensen's advice sounds like exactly what you want?
<steveeJ>
and then be able to create a PR without manually merging it ;-)
<gchristensen>
I mean
<gchristensen>
presumably you have made a PR before where your branch wasn't based on the exact commit you're merging in to, this is the same thing
<steveeJ>
I understand that part. I think what I'm missing is simply configuring hydra as a binary cache on my system
<gchristensen>
hydra.nixos.org doesn't provide a binary cache itself, everything it builds is immediately uploaded to cache.nixos.org
<steveeJ>
I remember taking it out of my system config at one point. so my system should have access to everything that CI went through already?
<gchristensen>
yea
<steveeJ>
this reminds me too much of my gentoo days :-)
<steveeJ>
is there an effort to have a community shared cache?
<gchristensen>
I don't usually like to hand out root access like that
<gchristensen>
I get the impression you're not quite understanding how easy this could be :/ like, checking out a channel revision, hacking, PRing, should all be pretty trivial
<gchristensen>
1. status.nixos.org/ 2. copy the commit hash for nixpkgs-unstable 3. git checkout that-hash 4. git checkout -b my-cool-package 5. do your thing 6. commit, and PR to master
<__monty__>
steveeJ: Maybe you're expecting intermediate build artifacts to be cached?
<steveeJ>
gchristensen: thanks. that really wasn't necessary :-D
<steveeJ>
gchristensen: besides that, I'm surprised you'd instruct me to use a browser and so I'm curious to clarify. assuming I have a git remote configured for upstream named upstream, wouldn't `git fetch upstream nixpkgs-unstable && git checkout upstream/nixpkgs-unstable && git checkout -b my-cool-package ..` be quicker, and especially not require me to use the brwoser? :-D
<gchristensen>
sure
<steveeJ>
__monty__: I think what I mistakenly expected is that every package in master is also cached by hydra. but I understand that rebuilding every package on every change to master _and_ caching the result would be unnecessarily expensive
<steveeJ>
btw, yes, branching out from nixpkgs-unstable gave me a cached webkitgtk. so thanks gchristensen and __monty__ ;-)
<sphalerite>
steveeJ: "rebuilding every package on every change to master _and_ caching the result" that's basically what's done
<__monty__>
Well pretty much every package is cached just not at every revision yeah.
<gchristensen>
every 4h
<sphalerite>
steveeJ: though not everything actually needs to be built, because a lot of packages will typically be unaffected, and nix allows recognising that situation
<steveeJ>
nice, some lessons learned here!
<steveeJ>
is somenone aware of an strace parser to figure out which shared objects failed to load? if not, I may start to write one
<gchristensen>
I was griping about that recently... 1308040676295221248
<steveeJ>
I'd start with analyzing `openat` and `stat` falls to paths whose filename matches `.*so.*`, and follow the ones who weren't eventually found
<steveeJ>
s/falls/calls
<steveeJ>
gchristensen: reading through that thread it's not obvious you found a solution, did you?
<gchristensen>
no
<sphalerite>
badblocks: Value too large for defined data type invalid end block (7814026584): must be 32-bit value
<sphalerite>
Does anyone know an alternative to badblocks that can deal with big disks? :D
<sphalerite>
gchristensen: as for lining up fds, do you know of strace's -e decode-fd options?
<gchristensen>
yeah
<sphalerite>
lol ok giving badblocks a bigger block size will apparently make it happy
<steveeJ>
so the block counter is 32-bits?
ninjin_ has quit [Remote host closed the connection]
ninjin_ has joined #nixos-chat
<sphalerite>
steveeJ: yep.
julm has quit [Quit: leaving]
julm has joined #nixos-chat
manveru has quit [Ping timeout: 260 seconds]
manveru has joined #nixos-chat
tilpner has quit [Quit: tilpner]
tilpner has joined #nixos-chat
cole-h has joined #nixos-chat
<cole-h>
lovesegfault: Ping
<abathur>
energizer: ha; stumbled on this while running a completely unrelated search about bash: https://github.com/t00n/8Bip
<gchristensen>
abathur: holy hell
<abathur>
yes, I meant something quite different by "instrumented bash"
<cole-h>
Hahahaha
<joepie91>
lol
maxdevjs has joined #nixos-chat
<abathur>
for context, on Sunday energizer asked: "is there a cli tool that'll play musical notes like `play-note A4`"
<lovesegfault>
cole-h: pong
<cole-h>
lovesegfault: You think klipper is g2g now?
<cole-h>
It works for you?
<lovesegfault>
Yep, it's ready
<lovesegfault>
I got it working locally
<cransom>
klipper? :swoon:
<lovesegfault>
and the generated config file looks good
<cole-h>
Noice. And everything is pushed? ;)
* lovesegfault
nods
<cransom>
the raspi3s attached to the printers running octopi are looking very nervous right now.
<cransom>
hot. my v0 has been in process for a while but i've been slacking. the v2.2 however has been good for a year.
<lovesegfault>
Nice, a v2.4 will be my next project
<lovesegfault>
well, pending wife approval
johanot has quit [Ping timeout: 260 seconds]
cbarrett has quit [Ping timeout: 260 seconds]
kalbasit has quit [Ping timeout: 260 seconds]
sorear has quit [Ping timeout: 258 seconds]
betawaffle has quit [Ping timeout: 260 seconds]
feepo has quit [Ping timeout: 260 seconds]
steveeJ has quit [Ping timeout: 272 seconds]
claudiii has quit [Ping timeout: 240 seconds]
pasukon has quit [Ping timeout: 240 seconds]
liszt has quit [Ping timeout: 240 seconds]
Guest88372 has quit [Ping timeout: 240 seconds]
waleee-cl has quit [Ping timeout: 246 seconds]
rajivr has quit [Ping timeout: 246 seconds]
sdier has quit [Ping timeout: 272 seconds]
elvishjerricco has quit [Ping timeout: 272 seconds]
raboof has quit [Ping timeout: 244 seconds]
jared-w has quit [Ping timeout: 240 seconds]
mudri has quit [Ping timeout: 240 seconds]
aria has quit [Ping timeout: 260 seconds]
emilazy has quit [Ping timeout: 246 seconds]
rizary has quit [Ping timeout: 260 seconds]
davidtwco has quit [Ping timeout: 260 seconds]
Cynthia has quit [Ping timeout: 260 seconds]
rizary has joined #nixos-chat
kalbasit has joined #nixos-chat
waleee-cl has joined #nixos-chat
manveru has quit [Ping timeout: 260 seconds]
liszt has joined #nixos-chat
manveru has joined #nixos-chat
jared-w has joined #nixos-chat
steveeJ has joined #nixos-chat
cbarrett has joined #nixos-chat
sdier has joined #nixos-chat
Cynthia has joined #nixos-chat
claudiii has joined #nixos-chat
rajivr has joined #nixos-chat
sorear has joined #nixos-chat
emilazy has joined #nixos-chat
feepo has joined #nixos-chat
pasukon has joined #nixos-chat
johanot has joined #nixos-chat
davidtwco has joined #nixos-chat
betawaffle has joined #nixos-chat
cjpbirkbeck has joined #nixos-chat
aria has joined #nixos-chat
Guest88372 has joined #nixos-chat
mudri has joined #nixos-chat
elvishjerricco has joined #nixos-chat
raboof has joined #nixos-chat
<energizer>
abathur: niiiiice
<abathur>
:)
rajivr has quit [Quit: Connection closed for inactivity]
<bqv>
Anyone remember my noise complaint issue from a few months ago? Some developments!
<bqv>
The noise is ongoing, but one of the houses its coming from was drug raided a few weeks back, broke the door
<bqv>
I was just verbally accosted by the landlady for being an "asshole" and starting a witchhunt for something she herself aggrees is my right to complain about
<bqv>
Got that conversation recorded, and also recorded the noise itself just as I called to update the police!
<cole-h>
lol
<energizer>
bqv: the noise is related to drugs?
<bqv>
Sent the recordings to the council so now maybe theyll get off their belligerent asses, and if not, the police will :)
<bqv>
energizer: landlady says its their "boiler"
<bqv>
I don't believe her
<bqv>
I reckon it could be drugs, but I'm not making any accusations without proof
<bqv>
Hey there it is again
<bqv>
I hope they keep it up, the more it happens, the more likely this finally gets solved
<bqv>
Got another recording now
noonien has joined #nixos-chat
<bqv>
Might send that one to the council too, I guess
<bqv>
This is satisfying a.f., after months and months and months I have a source, and a recording
<abathur>
glad you've got some hope of redress now; that whole thing sounded like a frustrating mess
<bqv>
Maybe what I'll do then, I'll keep the recording going, and every time I hear it (which as a semi-constantly triggered autist, is every time), I'll send it to the council
<bqv>
Yeah, thanks :D
steveeJ has quit [Ping timeout: 260 seconds]
steveeJ_ has joined #nixos-chat
steveeJ_ is now known as steveeJ
raboof has quit [Ping timeout: 240 seconds]
raboof_ has joined #nixos-chat
<bqv>
And again!
<abathur>
how often is it happening, now? (generally, not today specifically?) I wonder, if the frequency is generally increased, if it's practical to get someone to come out and observe
<bqv>
it's increased, but only after a decrease. like the lady said, it hasn't happened that often for the last month or two
<bqv>
though that's probably the only honest thing she said
<bqv>
i got the feeling that visit of theirs was an attempt to either reason with or threaten me
<bqv>
one of the tenants turned up with dogs, god knows why
<energizer>
scary dogs?
<bqv>
no, tiny ones, that was the weirdest part.
<bqv>
this is the same guy that called me an asshole and told me to get the fuck off his property before i even said anything to him, and i've never seen him with dogs before
cjpbirkb1 has joined #nixos-chat
<__monty__>
Hasn't the past month been warmer? (At least I think you were in west EU.) That'd be in line with the boiler story.
<bqv>
yes, that'd be a fair point
cjpbirkbeck has quit [Ping timeout: 260 seconds]
<bqv>
it's entirely possible it is the boiler, I'm just reasonably skeptical since that same house got busted for having a weed farm in it
<bqv>
and i know ventilation can be noisy too
<bqv>
i suppose that would be extraordinarily dumb, but i'm not sure anything else they've done isn't
<bqv>
and again...
<bqv>
and sent
<bqv>
i wonder if i can automate this...
<bqv>
Wow, they aren't relenting, again
<bqv>
lucky for me i'm now recording the exact time and sound of them, so i can just send them in batches
<bqv>
i'm curious how many times i can catch it tonight alone. we're on 6 or 7 now
<bqv>
i have a terabyte of storage available and a lot of free time
<bqv>
should be even better if i can get it with more background noise and/or household noise when my partner's back, for better comparison
raboof_ has quit [Ping timeout: 272 seconds]
<abathur>
bqv or if there's some other regular comparison noise you could catch; traffic, churchbells, train/ship horns
<bqv>
Yeah, I got birdnoise in the earlier ones
<bqv>
Just hard now cause it's 9:30pm
raboof_ has joined #nixos-chat
<abathur>
"If for any reason this doesn't seem like a good idea, the user is encouraged to drink until it does."
<bqv>
A+
<abathur>
https://github.com/zevweiss/booze "FUSE bindings for bash. If you, like me, have ever had the desire to create a FUSE filesystem from a shell script, this may be just the thing for you."
<__monty__>
Welp, thanks for the nightmares.
endformationage has joined #nixos-chat
<abathur>
I try
<abathur>
I'll be way too pleased with myself if I can get it working with osxfuse
<pie_>
i need this
<bqv>
i need booze, but i really don't think i need this.
<pie_>
didnt even notice it haha
<pie_>
drink this
__monty__ has quit [Quit: leaving]
noonien has quit [Ping timeout: 240 seconds]
pasukon has quit [Ping timeout: 244 seconds]
raboof_ has quit [Ping timeout: 260 seconds]
steveeJ has quit [Ping timeout: 240 seconds]
liszt has quit [Ping timeout: 240 seconds]
jackdk has quit [Ping timeout: 240 seconds]
johanot has quit [Ping timeout: 260 seconds]
aria has quit [Ping timeout: 260 seconds]
feepo has quit [Ping timeout: 260 seconds]
betawaffle has quit [Ping timeout: 260 seconds]
davidtwco has quit [Ping timeout: 260 seconds]
kalbasit has quit [Ping timeout: 272 seconds]
srhb has quit [Ping timeout: 272 seconds]
noonien has joined #nixos-chat
pasukon has joined #nixos-chat
aria has joined #nixos-chat
steveeJ has joined #nixos-chat
raboof_ has joined #nixos-chat
liszt has joined #nixos-chat
feepo has joined #nixos-chat
srhb has joined #nixos-chat
johanot has joined #nixos-chat
kalbasit has joined #nixos-chat
jackdk has joined #nixos-chat
<abathur>
"
<abathur>
oops; "Wavix is a POSIX system that uses WebAssembly's Software Fault Isolation to run the complete system in a single host OS process."
<colemickens>
If anyone wants a IOGear GCS1934, and wants to cover S+H, I'll send it to you. (that's a steep discount if you do the math). I figure someone around might want it. Ignore hte spam otherwise: https://www.iogear.com/product/GCS1934/