!djTaTBQyWEPRQxrPTb:nixos.org

Nixpkgs Architecture Team

233 Members
https://github.com/nixpkgs-architecture, weekly public meetings on Wednesday 15:00-16:00 UTC at https://meet.jit.si/nixpkgs-architecture53 Servers

Load older messages


SenderMessageTime
1 Dec 2022
@growpotkin1:matrix.orggrowpotkin1Or be in on those discussions. I use that a lot.21:11:48
@growpotkin1:matrix.orggrowpotkin1( related: I have a long list of pitfalls to avoid ) lol21:12:20
@roberthensing:matrix.orgRobert Hensing (roberth)
In reply to @infinisil:matrix.org
It could be a setting where the repository could configure whether sharding should be on or not, depending on size
When the time comes. Making glue code properly reusable is hard, and it's possible to half-ass it, so the outcome may not be what you want...
21:14:05
@infinisil:matrix.orginfinisil
In reply to @ncfavier:matrix.org
FWIW i don't have strong opinions about this PR anymore
I'm tending towards merging it. It makes a lot of sense with lib.extend existing, which in of itself makes at least some sense, it's like a lib-level overlay system, and it is used a bunch already.
21:14:12
@ncfavier:matrix.orgncfavieri guess i should rebase it21:15:43
@infinisil:matrix.orginfinisil Would love to reach consensus with John Ericson on this 21:17:02
@Ericson2314:matrix.orgJohn EricsonThe polyfil thing might convince me21:18:54
@Ericson2314:matrix.orgJohn EricsonBut I am too busy today to think much about it :(21:19:07
@infinisil:matrix.orginfinisilSounds good, I'll link to this convo from the PR for future reference21:21:08
@raitobezarius:matrix.orgraitobezarius joined the room.21:30:01
@dwarfmaster:dwarfmaster.netDwarfMaster joined the room.23:46:46
2 Dec 2022
@srid:matrix.org@srid:matrix.org changed their profile picture.02:19:44
4 Dec 2022
@ronnypfannschmidt:matrix.org@ronnypfannschmidt:matrix.orgSomething where I'm under the impression that something is missing is the state version concept For some reason it's bound to the release cadence of nixos instead of matching the granularity of services, which may have migrations (i recently hit this when a failed system update broke my nextcloud by running migrations at update time in turn destroying any chance to run nextcloud after the update) 17:51:55
@rick:matrix.ciphernetics.nlRick (Mindavi)It makes sense migrations are related to upgrades, no?19:21:11
@rick:matrix.ciphernetics.nlRick (Mindavi)The other channel is called unstable for a reason :)19:21:25
@rick:matrix.ciphernetics.nlRick (Mindavi)No but I agree that it'd be nice if services handled migrations more gracefully sometimes19:23:17
@ronnypfannschmidt:matrix.org@ronnypfannschmidt:matrix.org

Mindavi: it's kinda necessary to have local state versions and tools around them to contril versions to archive graceful migration

Not just app schema updates, also database versions & more

19:50:04
@toonn:matrix.orgtoonn That's a good point. Migrations being tied to stable releases in the sense of "No migrations until the next release," makes sense. But having to migrate everything all at once if you want to keep up could be harsh. 19:51:48
@ronnypfannschmidt:matrix.org@ronnypfannschmidt:matrix.orgAlso on occasion Patch releases ship database migrations that break the world Happened to my nextcloud unstable, it was most surprising 19:58:44
@raitobezarius:matrix.orgraitobezarius
In reply to @ronnypfannschmidt:matrix.org
Also on occasion Patch releases ship database migrations that break the world

Happened to my nextcloud unstable, it was most surprising
Do you know if there's an upstream issue on that?
23:01:18
@raitobezarius:matrix.orgraitobezariusSupposedly, they do a shit ton of testing to avoid pushing broken database migrations to everyone23:01:30
@raitobezarius:matrix.orgraitobezariusIf we cannot do this assumption, this is really problematic because, I am not absolutely certain that state versioning patch-level version is a good idea, esp. wrt to security fixes23:01:55
@rick:matrix.ciphernetics.nlRick (Mindavi)We'll always depend on upstream to do it right23:02:40
@raitobezarius:matrix.orgraitobezariusWe could be very extreme and perform additional testing like an enterprise / system integrator distribution would do it, but we do not have the means IMHO23:03:11
@raitobezarius:matrix.orgraitobezarius(otherwise we would need to invent some nice trick to do it "nicely")23:03:22
@rick:matrix.ciphernetics.nlRick (Mindavi)Maintainers could also setup their own testing with multiple versions of nixpkgs etc23:06:03
@rick:matrix.ciphernetics.nlRick (Mindavi)But yeah, it is a lot of work to do it properly23:06:17
@raitobezarius:matrix.orgraitobezariuseven if we do so, we cannot get the exact same environment as everyone23:06:22
@raitobezarius:matrix.orgraitobezariusI mean, I also run on nixpkgs unstable for my NC with nixos-upgrade (thug life), and I did not have any breakage with the patch level :'(23:06:44
@raitobezarius:matrix.orgraitobezarius(and I can see a log on 4th Dec for a NC unattended upgrade)23:07:32

Show newer messages


Back to Room ListRoom Version: 9