-
-
Notifications
You must be signed in to change notification settings - Fork 14.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gitea: 1.19.4 -> 1.20.0 #243883
gitea: 1.19.4 -> 1.20.0 #243883
Conversation
Fix for Gitea 1.20.0. Without this being set, e.g. a `git push` (or `ssh` to `git@` in general) fails like this: 2023/07/17 09:27:05 ...s/setting/setting.go:109:LoadCommonSettings() [F] Unable to load settings from config: unable to create chunked upload directory: /nix/store/yna9nf66wl2n9hlnhxi2g7fdgawk2kxl-gitea-1.20.0/bin/data/tmp/package-upload (mkdir /nix/store/yna9nf66wl2n9hlnhxi2g7fdgawk2kxl-gitea-1.20.0/bin/data: read-only file system) Connection to git.mbosch.me closed.
* Since Gitea 1.20 the request to `/commits` requires at least one retry because it appears to take a moment until Gitea actually knows that this repo isn't empty anymore (previously on 1.20 this failed with HTTP 409 which occurs when the requested repo is empty). * Remove `*.shutdown()`, for some reason they hang regularly for unknown reasons.
@techknowlogick pushed to more fixes that were necessary to fix the app itself and the tests. PTAL. Otherwise, LGTM 👍 |
Sounds like a good idea! @techknowlogick would you mind adding that to this PR? Not sure, my personal instance is now running with 1.20 and I haven't spotted any issues so far. In fact, I had to do a similar fix, though: For some reason, |
I think we already have that: If the instance comes up, we don't need the patch. An earlier release candidate crashed for me on startup without it (because it tried to write to |
What else needs to be done before merging this PR? |
I added If everybody is fine with my hackery for the CHUNKED_UPLOAD_PATH we can merge IMHO. |
And I would have preferred that |
Description of changes
https://blog.gitea.com/release-of-1.20.0/
Closes #241497
Things done
sandbox = true
set innix.conf
? (See Nix manual)nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)