I have a repo on tangled that I push to with jj.
Every push ends with the line: remote: time=2025-06-07T11:00:09.042Z level=ERROR msg="unexpected status code: 404".
Despite the errorl, as far as I can tell, the push succeeds`
Since this is from the remote, I assume it's an issue with tangled.
$ jj version
jj 0.30.0
$ jj git push --debug --remote=tangled -b master
2025-06-07T11:00:08.314799Z INFO jj_cli::cli_util: debug logging enabled
Changes to push to tangled:
Move forward bookmark master from bb689eecdb54 to f2ed7749018f
2025-06-07T11:00:08.347671Z DEBUG run_command: jj_lib::git_subprocess: spawning a git subprocess cmd=LC_ALL="C" "git" "-c" "core.fsmonitor=false" "--git-dir" "/home/user/mono/.git" "push" "--porcelain" "--no-verify" "--progress" "--force-with-lease=refs/heads/master:bb689eecdb54ab3c5e968a768804fdd1bc6ae5c7" "--" "tangled" "f2ed7749018fc6924948b4054fd0cdac8efac0d4:refs/heads/master"
remote: time=2025-06-07T11:00:09.042Z level=ERROR msg="unexpected status code: 404"
2025-06-07T11:00:09.085175Z DEBUG run_command: jj_lib::git_subprocess: response #0: f2ed7749018fc6924948b4054fd0cdac8efac0d4:refs/heads/master bb689ee..f2ed774
2025-06-07T11:00:09.085243Z DEBUG run_command: jj_lib::git: push_stats=GitPushStats { pushed: [GitRefNameBuf("refs/heads/master")], rejected: [], remote_rejected: [] }
Hey, that's a known issue and is just some server-side logging leaking into the client. This has been fixed in recent commitsβjust needs a redeploy.