It would be super useful if you could share the exact command you type and all the output. There may be a clue as to why that happens. A 10% failure rate may suggest the problem is unrelated to Gitea (just a hunch).
Yes I thought about that just after I closed the console only had that one line copied. And of course it hasn’t happen during the rest of this day. I will post all the console output as soon as it happens again probably tomorrow.
Since it happens rarely, could it be a something related to the automatic build? I can imagine the environment of the automatic build changing from one run to the other. I can’t quite figure out why a git push to Gitea would fail to perform 10% of the time when repeated in the exact same environment.
It’s a real mystery that’s why I posted it here. Sadly the problem doesn’t only occur in the automatic build system. Even pushing from the developer PC sometimes fails. It’s less of a problem there because a quick new push will fix it. On the build system it’s more annoying because it fails the build.
Gitea: Internal error
Seems to suggest it’s something on the server side. That’s why I’m expecting a configuration error. Maybe some timed period task Gitea executes that leaves the current working directory on some directory that is removed?
Thanks, I will keep an eye on it. Doesn’t seem to be completely equal but might be relevant.
In the mean time it’s been a day without any errors. Also a day where I had to database edit gitea to get access to certain repo’s again because of a bug in 1.17-rc1. Fun note the docker container upgraded it self to 1.17-rc1 instead staying on the actual release version 1.16.8
It is better to not use the “latest” tag but always use the precise version. There sometime are mistake in how Gitea releases are published. See the Hostea upgrade Guide for details. A warning was sent on the Hostea mastodon account on June 21st.
1.17 (none rc) didn’t fix the problem but does provide some additional information in the Gitea log.
2022/09/20 10:57:47 ...ers/web/repo/pull.go:1053:MergePullRequest() [E] Merge: git push: fatal: unable to get current working directory: No such file or directory
send-pack: unexpected disconnect while reading sideband packet
fatal: the remote end hung up unexpectedly
2022/09/20 10:57:52 ...ers/web/repo/pull.go:1053:MergePullRequest() [E] Merge: git push: fatal: unable to get current working directory: No such file or directory
send-pack: unexpected disconnect while reading sideband packet
fatal: the remote end hung up unexpectedly
2022/09/20 11:06:02 ...rvices/lfs/server.go:506:authenticate() [W] [6329827a-8] Authentication failure for provided token with Error: no token
2022/09/20 11:07:58 ...rvices/lfs/server.go:506:authenticate() [W] [632982ee] Authentication failure for provided token with Error: no token
2022/09/20 11:16:13 ...rvices/lfs/server.go:506:authenticate() [W] [632984dd] Authentication failure for provided token with Error: no token
2022/09/20 12:41:06 ...ers/web/repo/pull.go:1053:MergePullRequest() [E] Merge: git push: fatal: unable to get current working directory: No such file or directory
send-pack: unexpected disconnect while reading sideband packet
fatal: the remote end hung up unexpectedly
2022/09/20 13:34:10 ...rvices/lfs/server.go:506:authenticate() [W] [6329a532] Authentication failure for provided token with Error: no token
2022/09/20 13:34:10 ...rvices/lfs/server.go:506:authenticate() [W] [6329a532-2] Authentication failure for provided token with Error: no token
2022/09/20 16:26:06 ...s/repository/push.go:262:pushUpdates() [E] [6329cd7d-5] repo_module.CacheRef %!s(int64=88)/develop failed: exit status 128 - fatal: Unable to read current working directory: No such file or directory
- fatal: Unable to read current working directory: No such file or directory
Still unsure if this is a bug in Gitea or a configuration error.
