| 17 Mar 2025 |
 jade_ | we have been doing different types of things wrt such fixing: soon getting rid of fork() from the builder | 00:18:32 |
 hexa | not sure if the "not empty" part is accurate at this point | 00:18:40 |
| hexa | * not sure if the "not empty" part is still accurate at this point | 00:19:26 |
 John Ericson | it would be very nice to have some reference C++ that was sufficiently decoupled from the rest that we both could use it | 00:19:47 |
| jade_ | another couple changes i would be fairly happy if they got yoinked directly into cppnix:
- https://gerrit.lix.systems/c/lix/+/2801
- https://gerrit.lix.systems/c/lix/+/2800
| 00:19:48 |
| jade_ | that's what deleting the fork() is about | 00:20:04 |
| jade_ | makes it much easier to riir the sandbox setup | 00:20:12 |
| jade_ | since it no longer knows what a "store" is | 00:20:21 |
| John Ericson | oh you don't mean get rid of the sub process, you mean exec something | 00:20:34 |
| jade_ | yes, fork() -> posix_spawn() with explicit inputs | 00:20:49 |
| John Ericson | OK | 00:21:01 |
| John Ericson | I have been making 0 behavior/algorthimic changes right now | 00:21:14 |
| John Ericson | just moving code around | 00:21:17 |
| John Ericson | but yes no fork sounds good too, of course | 00:21:28 |
| John Ericson | in more ways than one ;) | 00:21:35 |
| jade_ | can't easily magick away the differences in priorities or views to trunk based development. but if some of the stuff like post mortem debugging winds up on both sides it would be very good. | 00:23:18 |
| jade_ | i would not wish debugging nix protocol bugs on my worst enemy | 00:23:52 |
| jade_ | and we all have much better things to be doing than protocol debugging (especially if a consistent repro is always necessary) | 00:24:28 |
| jade_ | also you might want to take our release notes generator, tbh. it would make changes a lot more portable, and ours both has more features and is simpler :) | 00:26:10 |
| jade_ | oh um. https://github.com/nixos/nix/blob/eb7d7780b18bce679639336cfd8ba6af1fe6139d/doc/manual/source/release-notes/meson.build#L9 thats really funny. this code is for calling our release notes generator and i don't think actually works on changelog-d | 00:36:17 |
| John Ericson | I'll defer that to Robert Hensing (roberth) who wrote the old one | 00:36:59 |
| John Ericson | It appears to be working? | 00:37:42 |
| John Ericson | at least manual build is not failing | 00:37:51 |
| jade_ | (i mean the real reason we rewrote it was that we wanted haskell out of our closure) | 00:42:00 |
| jade_ | * (i mean the real reason we rewrote it was that we wanted haskell out of our closure and we wanted our release notes generator to be in tree) | 00:42:48 |
| jade_ | but one of the notable differences is that ours has contributor credits built in | 00:44:53 |
 aidetechbot | hi, i forked nixpkgs but I can't seem to do git fetch upstream locally. I seem to get this error:
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
I know it's not related to my access rights to github because doing ssh git@github.com authenticates me fine. (and i can clone and fetch other repos fine) Anyone know what could be up? I
| 04:20:37 |
| aidetechbot | * hi, i forked nixpkgs but I can't seem to do git fetch upstream locally. I seem to get this error:
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
I know it's not related to my access rights to github because doing ssh git@github.com authenticates me fine. (and i can clone and fetch other repos fine) Anyone know what could be up?
| 04:20:55 |
| aidetechbot | * hi, i forked nixpkgs but I can't seem to do git fetch upstream locally. I seem to get this error:
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
I know it's not related to my access rights to github because doing ssh git@github.com authenticates me fine. (and i can push and fetch other repos fine) Anyone know what could be up?
| 04:21:27 |
| aidetechbot | another detail: it hangs for a while before giving me this error so i'm thinking it might be timing out somewhere and obfuscating the error. | 04:22:08 |
