| 27 Jul 2024 |
 Matt Sturgeon | 
Download image.png | 20:59:07 |
 magic_rb | In reply to @mattsturg:matrix.org
Should I still be seeing ~1000 status checks from buildbot now that #217 is merged? Depends on whether nix-community buildbot got bumped, that i dont know. But after that PR no if the limit is set right | 20:59:33 |
| Matt Sturgeon | Ah ok, the community buildbot probably hasn't been updated yet then I guess | 21:00:11 |
| Matt Sturgeon | Thanks for confirming | 21:00:20 |
| magic_rb | Probably not, ive managed to create a mess with the pydantic PR that me and mic92 tried to fix 3 times. I think we finally managed tho | 21:00:53 |
| magic_rb | (I had to make a truth table and then a boolean expression from that) | 21:01:19 |
 Mic92 | phaer: I think the database wasn't migrated after updating the server. | 21:02:40 |
| 28 Jul 2024 |
 zowoq | In reply to @mattsturg:matrix.org
Ah ok, the community buildbot probably hasn't been updated yet then I guess I've updated it. PRs with more than 100 builds/ status checks will only show a combined status. | 02:36:24 |
| zowoq | In reply to @mattsturg:matrix.org
Ah ok, the community buildbot probably hasn't been updated yet then I guess * I've updated it. PRs with more than 100 builds/status checks will only show a combined status. | 02:36:40 |
 Gaétan Lepage | Indeed it seems to work great ! | 08:14:52 |
| 29 Jul 2024 |
 DavHau | Does anybody have an idea, why I cannot configure a custom domain for my github pages deployment for nix-community/dream2nix.
Whenever I add the dream2nix.dev domain via the github settings, it works for a while, but then the setting silently gets removed.
I already tried this around 5 times and the result is consitant. | 06:42:07 |
| zowoq | Maybe CNAME file? | 08:22:19 |
| Mic92 | DavHau: have you tried using a CNAME record instead of AAAA/A records? | 08:34:50 |
| DavHau | I was using a CNAME record all along, but now noticed, that my deployment action removed the CNAME file from github. Thank you guys! | 10:32:52 |
 phaer | Ah, that makes sense! Guess it's worth one extra API call to figure out the project id by name is worth it anyway ;) | 13:48:27 |
| phaer | * Ah, that makes sense! Guess it's worth one extra API call to figure out the project id by name anyway ;) | 13:48:38 |
 Jonas Chevalier | Yeah, the UI doesn't make it obvious that when you change the setting, it actually pushes a git commit in the gh-branches page with that CNAME file. | 16:17:11 |
| 30 Jul 2024 |
|  varvir joined the room. | 08:31:41 |
| varvir | Hi! I want to get some help about nix-direnv. I followed the installation guide at flake support. But I encountered the error error: path '/nix/store/0fzhpkbnbbc0ywb2hp4l8bxfpqxr2fjc-source/flakedirenv/flake.nix' does not exist. | 08:33:22 |
| varvir | Only using nix method works fine. | 08:34:09 |
 K900 | Add flake.nix to git | 08:35:26 |
| varvir | oh Thanks! it works. | 08:37:39 |
| 1 Aug 2024 |
|  @thescientiac:matrix.org left the room. | 05:16:06 |
|  Vika (she/her) changed their profile picture. | 11:50:13 |
| 2 Aug 2024 |
|  @travis-staton:matrix.org joined the room. | 15:45:53 |
| Matt Sturgeon | Just tried using nix-direnv for the first time; it seems it doesn't work with git worktrees?
$ cd nixvim/docs_raw_submodule/
direnv: error /home/matt/nixvim/docs_raw_submodule/.envrc is blocked. Run `direnv allow` to approve its content
$ direnv allow
direnv: loading ~/nixvim/docs_raw_submodule/.envrc
direnv: using flake
error:
… while fetching the input 'git+file:///home/matt/nixvim/docs_raw_submodule'
error: '/home/matt/nixvim/docs_raw_submodule' is not a Git repository
direnv: nix-direnv: Evaluating current devShell failed. Falling back to previous environment!
direnv: export +NIX_DIRENV_DID_FALLBACK ~PATH
In this example ~/nixvim is a "bare" git repo and docs_raw_submodule is a worktree created using git worktree add
| 20:38:22 |
| 3 Aug 2024 |
| Matt Sturgeon | Seems to be working now after a reboot | 15:09:55 |
 toonn | StackOverflow recommends against using bare repos like that, FYI. I checkout an empty commit instead. | 15:31:58 |
| Matt Sturgeon | I used to have the default branch checked out at the top-level and then have feature branches checked out in nested worktrees, but I found it annoying how the nested worktrees showed up as untracked files in the top-level worktree, figured a bare repo was cleaner.
Do you recall why someone on stackoverflow recommended against using a bare checkout? Was it just because some tooling might be expecting a .git dir? I find most tools use libgit or something similar, so it usually isn't an issue.
| 15:44:36 |
| toonn | MattSturgeon: This answer has the reasoning at the end, https://stackoverflow.com/a/54408181 | 15:56:44 |
