If you're using #ForgeJo and are experiencing the error
`fatal: the remote end hung up unexpectedly` when doing "git push", the problem is the client buffer size for HTTP pushes. In my case I have just fixed it by doing the following:
`$ git config http.postBuffer 157286400`
I've found the solution here:
🔧 YAML frontmatter converts directly to CLI flags: model: opus becomes --model opus, mcp-config: ./mcp.json becomes --mcp-config ./mcp.json, dangerously-skip-permissions: true becomes --dangerously-skip-permissions
🔄 Full Unix philosophy support: Pipe data in and out with stdin/stdout, chain agents together like git diff | review.claude .md or plan.claude .md | implement.codex .md, transparent logging shows what runs
I finally beefed up my :nix: #nix derivation for the :gitannex: #gitAnnex standalone builds so the download process of the non-predictable version url is automated. It now uses git annex itself to retrieve the tarball from a matching commit in @…
Is there sandbox weirdness going on with :nixos: #nix fixed-output-derivations (i.e. when you specify outputHash) that some tcp connections are disallowed? I can git clone in runCommand, but down the line a 'git annex get' (which internally just downloads another file via http) fails with this weird message 'no such protocol name: tcp'. With `--option sanbox false` everything is fine, …
git config --global alias.pfusch 'push --force-with-lease'