{^_^} has quit [Remote host closed the connection]
{^_^} has joined #nixos-chat
gchristensen has joined #nixos-chat
<gchristensen>
...oops. nixops deploy --force-reboot without an `--include` statement :D
<gchristensen>
,botsnack
<{^_^}>
Oh thanks, have a cookie yourself
<infinisil>
gchristensen: Another thing about --include: If you use `--include foo --include bar`, one of them is ignored
<infinisil>
Silently
<pie_>
oh no i dont know what that does but it sounds bad
<ldlework>
So I got one of those new Oculus Quests. I just took it out to an open field and played with the max play-area. Incredible. So crazy being wireless and never even encountering the game boundries as you run around shooting robots.
<ldlework>
I didn't think the freedom would be all the important as in most games you usually just stand in one spot. But turns out you stand in one spot because you're tethered!
<ldlework>
It actually took me a good 20 minutes for my brain to truly accept my ability to walk and even jog around.
<pie_>
well, this seems like one of those things thats "duh" in hindsight :p <ldlework> I didn't think the freedom would be all the important as in most games you usually just stand in one spot. But turns out you stand in one spot because you're tethered!
<ldlework>
You get so used to turning around with the controller I really had to force myself to stop doing that.
<pie_>
very jealous right now trying not to think about it :P
<pie_>
didnt get into vr because $$$ and time
<ldlework>
I got my girlfriend and I both one and we played poker last night for like 3 hours :D
<ldlework>
met all sorts of strange folk, mostly young people
<pie_>
xD
<pie_>
ldlework, how much does it cost
<ldlework>
399 or 499 depending on if you want 64 or 128 GB
<pie_>
what does that...even mena
<ldlework>
huh?
<pie_>
*mean
<pie_>
why do vr goggles have storage
<samueldr>
another one of those android-based entirely locked-down platform from oculus... pass :/
<ldlework>
pie_: the Quest is a wireless standlone HMD
<ldlework>
it doesn't use your PC, hence the playing out in an open field
<pie_>
wait they can do whatever heavy-ass processing vr needs on the headset???? :O
<pie_>
how does that work i thought vr was heavy
<ldlework>
it has a snapdragon inside
<ldlework>
pie_: the graphics are not as good as you can get with a beefy PC
<pie_>
though now that i think about it vr probably just needs 2x the processing for two cameras?
<ldlework>
But it runs smooth and not all games require photorealism
<ldlework>
Yeah
<pie_>
reasonable
<samueldr>
realistic graphics apparently aren't as important as one might think to be engrossed
<samueldr>
main thing is good tracking
<ldlework>
nope, it feels like you're in...
<samueldr>
then you can belive that big blue blob is real
<pie_>
samueldr, also kind of "duh"
<ldlework>
how do you put it..
<ldlework>
it's like
<pie_>
samueldr, but i never had the opportunity to game much so i wouldnt know :C
<ldlework>
a big carnival fun house?
<Ralith>
realistic graphics aren't important at all
<Ralith>
a steady framerate is
<ldlework>
it's hard to describe
<samueldr>
couldn't say from first hand perspective, never VR'd like the cool kids
<pie_>
inb4 my eyes suck anyway and adjustable optics ends up "more real" :p
<ldlework>
my eyes are real bad too
<ldlework>
luckily it comes with an insert so you can wear your glasses no prob
<Ralith>
ldlework: if you were doing artificial turning, you've been doing it wrong from the start :P
<samueldr>
was interested in one of those last generation oculus self-contained headsets, but once I saw it's all locked down the interest fluttered away :(
<ldlework>
wrt to being locked down i was already able to load my Unity VR game on the thing
<samueldr>
I mean complete control of the device
<ldlework>
yeah but not sure what you need that for
<samueldr>
not whatever they want to allow
<pie_>
also yeah wtf locked down? >:I
<samueldr>
well, whatever!
<pie_>
well, platforms are all the rage
<ldlework>
Ralith: even with Vive mounted to your ceiling as you turn it twists so you're incentivized to not do so
<samueldr>
progress isn't helped by locked down devices
<Ralith>
for tethered play the HTC gear is great (there are even open source drivers for it!), and Valve's new gear is better yet
<pie_>
probably because it makes you money
<ldlework>
that's silly -- we've solved a lot of VR problems with the current generations of devices
<Ralith>
ldlework: I use my Vive heavily and I only think about twists between gameplay sessions
<samueldr>
I won't buy a phone or a tablet where I can't change the OS
<ldlework>
so at least as a principle it doesn't work out :)
<samueldr>
so won't do the same for a VR headset or a TV either
<Ralith>
ymmv on oculus with those stubby little cables
<ldlework>
Ralith: you're braver than me I guess
<ldlework>
When I have to unwind the cable a bunch of times it makes me cringe. The thing is so expensive.
<Ralith>
I hold it over my couch and just let it spin!
<pie_>
shouldve given it replaceable cables
<ldlework>
pie_: indeed
<Ralith>
they are replacable
<pie_>
oh
<Ralith>
(though again, lol if you're on oculus)
<ldlework>
Ralith: what you playing?
<pie_>
thats very positive of them that its replaceable
<Ralith>
if it dies at this point I'll be replacing it with an Index anyway
<ldlework>
for PC VR it's pretty much Onward for me
<pie_>
cant have people not buying a new device
<Ralith>
ldlework: pavlov and beat saber mostly
<ldlework>
right on
<ldlework>
Ralith: you ever try Stand Out?
<Ralith>
used to do competitive pavlov but I got fed up with the culture
<Ralith>
gamers are shitty people on average
<Ralith>
everything by the stand out devs is a shameless cash-in
<Ralith>
stay away
<ldlework>
shame, reviews are ok and battle royale sounds fun in VR
<Ralith>
pavlov has some BR mods which are decent
<ldlework>
You ever try Neos VR?
<drakonis>
competitive pavlov?
<Ralith>
ldlework: idk what that is
<ldlework>
My top games are probably Onward, Neos VR and Hotdogs Horseshoes and Handgrenades
<ldlework>
Basically the guy rebuilt the unity inspector and scene editor, in game, then figured out networked assembly reloading.
<ldlework>
So you can basically code the game from inside the game in multiplayer.
<ldlework>
Second-life, but with a networked simulation core I can get behind. And in VR \o/ It's actually crazy interesting...
<Ralith>
sounds liable to be a complete mess
<ldlework>
I've started building little state machine frogs but I haven't finished.
<Ralith>
unity is the opposite of a strong technical foundation even for the most trivial of projects
<ldlework>
eh
<ldlework>
there are plenty of successful competently made Unity games. And it has improved in a lot of important ways in the last 5 years or so.
<Ralith>
"successful games" and "built on a strong technical foundation" are practically orthogonal
<ldlework>
if you say so
<Ralith>
every developer of a remotely decent looking unity game consistently complains of having to replace large portions of the engine, which is complicated by not even having access to the engine code
<ldlework>
i don't know what you're talking about, having used unity for a good long while. ECS? The physics engine updates? Nested prefabs? The shader graph? These are all huge features that everyone was asking for for a long time.
<ldlework>
Mechanim before that.
<ldlework>
Anyway, Neos VR seems to be doing the thing.
<Ralith>
they're also notorious for spending all their time on new feature work and ignoring maintenance :P
<ldlework>
Oh I forgot uGUI, UIElements, and the blueprint clone coming.
<Tasqa>
Colo hoster had unstable network the past 3 months -.-
<arianvp>
Yolocolo
<Tasqa>
Is there a armv7 build of Ceph for Nix?
__monty__ has joined #nixos-chat
<gchristensen>
sphalerite: you 'round?
<arianvp>
Tasqa: there is currently no build for ceph for nix
<arianvp>
At all
<arianvp>
Rocksdb is a bitch to cross compile so I gave up trying to get it to work on arm
<arianvp>
:/
<arianvp>
Also we're using their 'cmake build which they do not officially support anymore I think
<gchristensen>
nix-shell -p ceph seems to work though?
<arianvp>
gchristensen: yeh but we marked it broken on master recently I think
<arianvp>
In 19.03 it still works
<gchristensen>
ouch
<arianvp>
They switched to buck based build system. Not sure if we have buck support in nix yet
<eyJhb>
Have anybody ever tried getting Maple to work on NixOS?
<Tasqa>
Ceph builds are a shit show :x
<etu>
lejonet: What happened to your ceph shuff you worked on? :D
<arianvp>
q
<arianvp>
I really wish systemd would reference to units by absolute path :/
<arianvp>
then you could just do nix-copy-closure /nix/store....-/default.target and it would copy over all dependent units
<arianvp>
hmm Maybe i could add a X-Requires field or something to cheat
<gchristensen>
oh cool arianvp
<arianvp>
yeh we manually curate upstreamSystemdUnits now, but that sounds a bit error prone to me
<arianvp>
meh, this won't gain us a lot, as all the upstream units are in the same derivation
<arianvp>
this would only help if each unit was a derivation by itself I think
jasonrm has quit [Ping timeout: 248 seconds]
sdier has quit [Ping timeout: 264 seconds]
sdier has joined #nixos-chat
Twey has quit [Ping timeout: 248 seconds]
Twey has joined #nixos-chat
cransom has quit [Ping timeout: 252 seconds]
gchristensen has quit [Ping timeout: 252 seconds]
NinjaTrappeur has quit [Ping timeout: 252 seconds]
gchristensen has joined #nixos-chat
NinjaTrappeur has joined #nixos-chat
jasonrm has joined #nixos-chat
cransom has joined #nixos-chat
Jackneill has quit [Remote host closed the connection]
Jackneill has joined #nixos-chat
Jackneill has quit [Read error: Connection reset by peer]
kgz has quit [Ping timeout: 252 seconds]
Jackneill has joined #nixos-chat
Jackneill has quit [Remote host closed the connection]
kgz has joined #nixos-chat
Jackneill has joined #nixos-chat
Jackneill has quit [Ping timeout: 252 seconds]
Jackneill has joined #nixos-chat
Jackneill has quit [Remote host closed the connection]
Jackneill has joined #nixos-chat
eyJhb is now known as eyJhb
Jackneill has quit [Remote host closed the connection]
Jackneill has joined #nixos-chat
Jackneill has quit [Remote host closed the connection]
Jackneill has joined #nixos-chat
<gchristensen>
NixOS is so nice. a customer had a problem with their network config, I was able to send them a new Nix expression for their network config and it just solved it.
<aanderse>
:)
<ar>
the predictability and repeatability of nixos is just too good. it spoiled all other distros and all "traditional" configuration management systems
<etu>
ar: Yep... It's cool and stuff like that :D
<aanderse>
there is a downside though...
<aanderse>
it makes being a sysadmin on debian and redhat boxes at work horrible :S
<aanderse>
ha ha ha
<gchristensen>
truth
<etu>
aanderse: Yeah... That has happened to me :D
<joepie91[m]>
okay, this is beginning to get a little scary. my cat is now starting to eat her snacks by sitting on her hind legs, picking it up with her paws, and feeding it into her mouth...
* aanderse
keeps chipping away at converting more and more servers to nixos
<joepie91[m]>
is there a point where cats become human
<aanderse>
joepie91[m]: planet of the cats
__monty__ has quit [Quit: leaving]
<pie_>
whatever you do dont give them thumbs
<joepie91[m]>
lol
<joepie91[m]>
I am becoming increasingly convinced that they don't /need/ thumbs...
<joepie91[m]>
usecase: piles of user-definable code in an application that need to run in their own isolated environment
<gchristensen>
joepie91[m]: I was able to get standard NixOS to boot in about 4s under firecracker
<joepie91[m]>
gchristensen: standard NixOS is bulky, though
<gchristensen>
in what way?
<joepie91[m]>
gchristensen: requires quite a bit of disk space, no?
<joepie91[m]>
and afaik it'd use more memory too
<gchristensen>
I see no reason why
<joepie91[m]>
I'm really going for a more Alpine-esque footprint here :P
<joepie91[m]>
hm
<joepie91[m]>
do you have an example of a minimal build then?
<joepie91[m]>
also, 4s is still quite a lot...
<joepie91[m]>
my objective is really <1s, ideally less
<gchristensen>
aye the root filesystems was 400M
<joepie91[m]>
right, that's nearly 10x the size of a not-os build, according to the repo :)
<gchristensen>
might be further prunable
<gchristensen>
4s is a bit slow, indeed
<gchristensen>
but brings a lot of advantages -- like being able to use standard nixos everything
<joepie91[m]>
these are very short-lived environments, so I probably don't need that
<gchristensen>
yeah
<joepie91[m]>
my only objective, really, is for it to boot, start a single daemon, let it accept one or more inputs producing corresponding outputs, and killing it at some point afterwards
<joepie91[m]>
potentially after a single input
<gchristensen>
yeah, same
<gchristensen>
my use case is bursty, so I keep a pool of them running and waiting and then the 4s isn't a big deal. if it was sustained, the 4s would be a big deal
<joepie91[m]>
right, a pre-warmed pool is not an option for me, due to multi-tenancy requirements
<joepie91[m]>
I need to actually start them up on demand :)
<joepie91[m]>
and as far as I can tell, not-os is the closest thing to Alpine that we have for Nix-y stuff
<gchristensen>
does not-os use the musl work?
<joepie91[m]>
dunno
* gchristensen
is super interested in firecracker + nixos being awesome
<eyJhb>
*sigh* another community that uses slack
<joepie91[m]>
yep...
<joepie91[m]>
corporate open-source whee
<gchristensen>
.....yay.
<eyJhb>
joepie91[m] send your cat to them, and cause total chaos!
<eyJhb>
*knocking all the things to the ground
<tilpner>
joepie91[m]: It's not firecracker, but with qemu I used live migration to start VMs in <0.2s
<joepie91[m]>
tilpner: you have my interest..
* gchristensen
perks up
<joepie91[m]>
please continue :)
<joepie91[m]>
lol
<ar>
tilpner: you "migrated" a VM from a serialized state?
<tilpner>
joepie91[m]: You start a VM up to some point, init what you can but try to keep this state small, migrate to a file on disk
<tilpner>
joepie91[m]: Then you can repeatedly "instantiate" this migrated VM, giving it different commands
<gchristensen>
:o
<joepie91[m]>
that sounds like an interesting approach
<ar>
tilpner: that kind of sounds like what aws lambda could do
<joepie91[m]>
tilpner: do you happen to have any docs on this?
<tilpner>
joepie91[m]: Here's a PoC with Nix, intended to be used for the RCE-as-a-service bot I ran a while ago: https://github.com/tilpner/qeval
<joepie91[m]>
organized or otherwise
<joepie91[m]>
ar: lambda uses firecracker :P
<gchristensen>
I don't know how they boot so fast
<joepie91[m]>
tilpner: excellent, thanks!
<tilpner>
joepie91[m]: I was also investigating firecracker/crosvm for quick sandboxed application on NixOS, but am waiting on virtio-fs
<joepie91[m]>
tilpner: for store sharing, or?
<joepie91[m]>
(virtio-fs can handle overlays, iirc?)
<tilpner>
Yes, for sharing closures of whatever I want to run. qeval builds squashfs', but that's not fun if you have a large closure, or a lot of them
<joepie91[m]>
right, yeah, that makes sense
<joepie91[m]>
that was another of my concerns
<tilpner>
On the upside, squashfs is fast, doesn't open the box of FUD that is 9p-fs
<joepie91[m]>
I assume that this works fine with your QEMU-based approach?
<ar>
tilpner: 9p virtio isn't enough?
<tilpner>
ar: No, that was too scary
<ar>
also, what's scary about 9p-fs?
<tilpner>
In the end I discontinued the bot, it was too risky with hardware vulnerabilities popping up every few weekks
<ar>
i haven't tried using it yet, but i did consider it
<gchristensen>
tilpner: I sort of suspect you could stymie any sort of hardware vulnerabilities (like we've been seeing) by running everything under strace
<tilpner>
ar: I just didn't trust it much. There were reports it was unreliable and brittle, bad comments about its code. Handing a squashfs to qemu is much safer just by having entirely different code-paths that could have bugs
<tilpner>
gchristensen: I don't follow. Run strace inside or outside the VM? How would that help?
<gchristensen>
tilpner: most of those vulns require having the ability to very carefully setup the execution environment and timing
<gchristensen>
and I'm suspecting strace would screw with stacks and timing sufficiently to spoil it
<ar>
but strace would only slowdown syscalls?
<gchristensen>
derp
<gchristensen>
you're right
* gchristensen
has no idea what he's talking about
<ar>
maaaaaaybe sotruss + seccomp (to prevent, for example, exec()) would do the trick
<ar>
but that's still rather wishful thinking
<gchristensen>
:)
<tilpner>
Yeah, there's a lot of uncertainty around this
<tilpner>
And everything ran as root, because the kernel didn't know what a user is
<tilpner>
And this was on my main server with sensitive data. So...
<gchristensen>
lol
<tilpner>
gchristensen: Then in-VM kernel was configured to be as minimal as possible. Users were disabled
<gchristensen>
nice
<tilpner>
It also didn't know what IP was, that confused a lot of people
<gchristensen>
I went that route once and spent while debugging why init wasn't working
<tilpner>
Yeah, it's quite frustrating
<gchristensen>
it was because (first) shebang execution wasn't included, and (second) ELFs weren't supported
<tilpner>
"Which features do I need to get X working?" where X might be ghc or rustc
<tilpner>
Then I tried to rewrite the control process and init with Rust, to reduce closure size
<tilpner>
But carnix didn't like cross-compilation, and I eventually gave up on that
<eyJhb>
Grats to my laundry provider, the password they used aren't in Rockyou, at least not uppercase...
<gchristensen>
,ifd
<{^_^}>
import-from-derivation (IFD) is when you evaluate nix from a derivation result, for example `import (pkgs.writeText "n" "1 + 1")` will evaluate to 2. This is sometimes problematic because it requires evaluating some, building some, and then evaluating the build result.
drakonis has joined #nixos-chat
endformationage has joined #nixos-chat
drakonis has quit [Quit: WeeChat 2.4]
gchristensen has quit [Quit: WeeChat 2.4]
gchristensen has joined #nixos-chat
<eyJhb>
Btw. whoever asked if command injection is still a thing, and via. web. It isss.. The above thing is a webinterface being stupid
Jackneill has quit [Remote host closed the connection]
<sphalerite>
gchristensen: I'm still around sometimes :p
<gchristensen>
:) I ended up sorting it. I was gonig to ask about socat. I couldn't figure it out. I ended up using openssl enc and netcat.
<sphalerite>
gchristensen: I tend to close IRC at work now because of its potential for distraction, and then forgetting to reopen it :p
<sphalerite>
gchristensen: hehe fair enough
<sphalerite>
what about socat couldn't you figure out though?
<gchristensen>
I wanted to use a pre-shared key for encrypting / validating the connection, and I didn't sort out how
<sphalerite>
hm yeah, looks like it doesn't support that
<gchristensen>
socat is such a powerful tool that I can never remember how to use it :P
<sphalerite>
yeah I always use the manpage
<sphalerite>
although by now I think I've more or less memorised how to serve a command via TCP
<gchristensen>
you might enjoy playing with eyJhb's CTF server which allows command injection :)
<sphalerite>
oooh
<sphalerite>
where cna I find out more?
<gchristensen>
eyJhb: ^
<pie_>
gchristensen, i can help a little with socat i think
* pie_
needs to remember to catch up with scroll before sending new messages
drakonis has joined #nixos-chat
<LnL>
whoa, you get emails for gist comments now!
<joepie91[m]>
what does the -f flag mean for nix-build? I am using it somewhere, but it's not in the manpage...
<joepie91[m]>
LnL: whoa, really? finally!
<LnL>
seems so, just received one :)
<joepie91[m]>
hmmm. -f is meant to point at nixpkgs?
<samueldr>
joepie91[m]: nix-build or nix build?
<joepie91[m]>
nix-build
<gchristensen>
nice: $ nixos-rebuild-switch -I nixpkgs=./path/to/nixos-unstable -> trace: Warning: direnv-2.20.0 downgraded by overlay with direnv-2.19.2.
<gchristensen>
trace: Warning: alacritty-0.3.2 downgraded by overlay with alacritty-0.3.0.
<samueldr>
error: unrecognised flag '-f'
<joepie91[m]>
(I'm trying to figure out how to do a not-os build)
<joepie91[m]>
samueldr: ... wha?
<joepie91[m]>
OH
<joepie91[m]>
sorry
<samueldr>
right?
<samueldr>
:)
<joepie91[m]>
it was `nix build`
<joepie91[m]>
I was looking at the wrong line lol
<samueldr>
--help on nix build will show
<joepie91[m]>
the one that *does* use `nix-build`...
<joepie91[m]>
but not -f
<samueldr>
no worries, easy to mistake
<samueldr>
I looked at the source of nix-build since there _are_ some parameters not documented
<joepie91[m]>
aha :P
<samueldr>
other orer of idea joepie91[m], but you seem likely to have faced the issue... within a JS web app, errors from end-users are being aggregated to a service, but we're flooeded with useless or unactionable errors. Some are from third-party crap that is forced down on the devs, other from third-party APIs, and a good chunk are things like the users losing internet connectivity
<samueldr>
other order of*
<samueldr>
any tips for dealing with that?
<joepie91[m]>
samueldr: is this an off-the-shelf system a la sentry?
<samueldr>
(also had for a while errors from internal stuff from the iOS version of chrome being logged since it's apparently implemented as injected JS in the dang webview...)
<samueldr>
yeah
<joepie91[m]>
then I would expect the dashboard to have functionality for ignoring particular (types of) errors
<samueldr>
right, so I didn't miss anything from the language allowing to discriminate against "boundaries" in the errors
<samueldr>
good to know
<joepie91[m]>
that having been said, errors are usually errors :P
<joepie91[m]>
and need resolution of some sort
<samueldr>
can't really do anything when the user lost internet connectivity while browsing a site!
<samueldr>
:)
<joepie91[m]>
samueldr: nope; JS doesn't define anything in terms of error semantics other than a) an Error type, b) throw/try/catch semantics
<samueldr>
yeah
<joepie91[m]>
all the actual error capturing logic is generally custom code from whatever tool you're using
<samueldr>
exactly
<joepie91[m]>
best you can do is wrap stuff in a catch, but that's assuming that it is sanely handling errors internally, which from the sounds of it is probably not the case
<samueldr>
I was mostly looking for confirmation or non-obvious tricks :)
<joepie91[m]>
right, but why is lost internet connectivity an error
<samueldr>
because it's raised from the .catch end of a promise
<joepie91[m]>
samueldr: elaborate...
<samueldr>
the app was made with unhandled rejection being used to treat any "Exception" type errors as stopping the application (though it was found that firefox did not support it)
<samueldr>
it's not a pet project so I can't say much more
<joepie91[m]>
I mean, that is a correct approach in principle, unhandled rejections are just async uncaught throws
<samueldr>
and in case you're thinking "but if it 4xx it won't be handled?" the wrapper for the API treats then as non-exceptional kind of errors
<joepie91[m]>
but in that case you should be able to use .catch to selectively absorb errors
<eyJhb>
Sent you a pm sphalerite ;)
<joepie91[m]>
either a) a filtered catch, if using Bluebird, or b) a general catch and rethrowing the non-filtered errors
<eyJhb>
And now to catch the sunset
<samueldr>
though, they don't implement a common sub-classed error types IIRC (I'm not looking at the code or errors right now)
<samueldr>
so would it really be implemented by filtering on the messages?
<samueldr>
if so, then there's the whole i18n issue which kinda stinks
<samueldr>
like, if the browser is in spanish, the message is different than the one in french or english
<joepie91[m]>
samueldr: are these browser errors or application errors?
<samueldr>
browser
<joepie91[m]>
samueldr: then they should have identifiable types and/or properties
<joepie91[m]>
emphasis on 'should'
<joepie91[m]>
error handling culture is a bit... problematic in JS :)
<samueldr>
yes :(
<joepie91[m]>
samueldr: don't worry though, it's one of the hills I'm dying on
<joepie91[m]>
:P
<joepie91[m]>
I am confused
<joepie91[m]>
`nix build -f .`
<joepie91[m]>
run in the not-os repo, this builds the runner
<joepie91[m]>
but... default.nix evaluates to a rec object (err, whatever it's called)
<joepie91[m]>
with three properties
<joepie91[m]>
test1, runner, and config
<LnL>
nix-build ./. -A foo = nix build -f ./. foo
<joepie91[m]>
why is it seemingly building specifically the 'runner' property when I haven't specified that?
<joepie91[m]>
I... don't think so? `result` directly points at the runner
<LnL>
without installables it builds everything just like nix-build ./. would
<joepie91[m]>
then why does `result` point specifically at the runner? does it filter out things that aren't derivations or something?
<joepie91[m]>
(because I think only `runner` is a derivation out of those three)
<LnL>
possibly, otherwise there should be result-2, etc. for the other attributes
<joepie91[m]>
hmm.. moment.
<LnL>
yeah config is a set I think, it won't recurse everything
<samueldr>
oh, joepie91[m], just for fun, not asking for help. we have errors logged because a user saved the page as an HTML file with all assets (CTRL+S) and opened it... the API location is programatically derived from the app's location so it tried to access files and hit a SecurityError :)
<joepie91[m]>
also, are these semantics documented somewhere?
<joepie91[m]>
it feels really magic
<joepie91[m]>
and not the good kind :)
<joepie91[m]>
samueldr: lol
<samueldr>
I might say that there was a moment of confusion when we saw the location of the file
<LnL>
possibly but I'd be surprised if it's described somewhere
<joepie91[m]>
samueldr: time to filter out file:/// URLs? :P
<joepie91[m]>
LnL: that sounds like a bug :D
<LnL>
I have too many open nix prs already :/
MichaelRaskin has joined #nixos-chat
<joepie91[m]>
lol
<joepie91[m]>
I'll file a bug some time soon
Guanin has quit [Remote host closed the connection]
<eyJhb>
Considered playing or looking at the challenges.. But... Start in a couple of hours, and it is 23.40 here..
<pie_>
eyJhb, one does not simply sleep during a ctf :I
<samueldr>
so, that's not a race, but a points accumulation thing, right?
<eyJhb>
pie_ getting too old for that shit (21)!
<eyJhb>
samueldr basically. No first blood etc. in this
<samueldr>
too old, 21? I must be close to retirement then :/
<samueldr>
dunno, would be fun, but not sure how much I can actually _do_ on a real CTF, but that would surely be edifying
<samueldr>
or educamating
<eyJhb>
Does it help if I state that my body has somewhat just given up on life?
<pie_>
tell me about it
<eyJhb>
pie_ don't you tease me about that, I've got loooads of shit to tell. Couldn't open my damn mouth for a year after I got my wisdom tooth pulled.
<pie_>
Dx
<pie_>
i kept telling myself last time i did university that i dont want to pull any more allnighters, yet to keep my word
<pie_>
maybe this time around lol
<eyJhb>
I only do that at CTFs... - Last time I even had enough energy for fitness! Was awesome
drakonis has quit [Ping timeout: 244 seconds]
<pie_>
i have a cough that removes my enjoyment of eating food
<pie_>
its really annoying
<pie_>
xD
<colemickens>
cool, just realized my spot instance script was changed to remove the hour limit.
<colemickens>
and I guess the spot price for the x2.large never went above 50c/hr? Still a lot of compute that could've been building nix pkgs...
<colemickens>
$81 for 28cores +384GB for a week, not too shabby packet
<gchristensen>
you can do a lot on the x2 :)
<colemickens>
libdrm,mesa,chromium is on the build list for today :)
<gchristensen>
:D
<colemickens>
well, and that sort of implies a lot of the rest of the world too
<gchristensen>
-j56
<joepie91[m]>
gchristensen: so I have a basic not-os build working, but it's producing a kernel, a squashfs, and an initrd. it *seems* that firecracker expects the initrd to be embedded into the kernel, and does not allow specifying it separately. given that you've booted NixOS under Firecracker before, how do I solve this?
<gchristensen>
ah
* joepie91[m]
has a vague idea of how it all ties together, at best
ajs124 has joined #nixos-chat
<gchristensen>
I ... don't know
<joepie91[m]>
gchristensen: how did you get NixOS to boot then? :P or is it just a matter of not remembering anymore?
<joepie91[m]>
(afaik NixOS by default produces the same)
<gchristensen>
I don't remember and reading the soucre doesn't hint
<clever>
gchristensen: i think you didnt use the initrd at all in firecracker?
<gchristensen>
that alone took a loooong time to sort out
<joepie91[m]>
gchristensen: any pointers at all on where to look to answer this question? because I have _no idea_ how the kernel stuff ties together within NixOS
<joepie91[m]>
(input from other people obviously also welcome :P)
<gchristensen>
ohhh
<gchristensen>
ehh
<pie_>
eyJhb, i may or may not be pulsing you with requests im not sure