-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
The latest version gitea. terminate abnormal #16290
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
Comments
please fill out the full details of the issue template. |
Run with docker:
Description... Screenshots |
random occurrence, then the docker container restarted. |
This suggests that a nil TreeEntry snuck into the map here:
Which suggests that a path was missed in:
Are you able to work out which repository was being cached at the time? It will have been a repository that was just recently pushed to? Would you be able to check your repository on the web ui and if there is an error rendering it give me the logs - or better push it up to try.gitea.io for me to try to figure out what's happened. |
There is a bug with last commit cache recursive cache where the last commit information that refers to the current tree itself will cause a panic due to its path ("") not being included in the expected tree entry paths. This PR fixes this by skipping the missing entry. Fix go-gitea#16290 Signed-off-by: Andrew Thornton <[email protected]>
There is a bug with last commit cache recursive cache where the last commit information that refers to the current tree itself will cause a panic due to its path ("") not being included in the expected tree entry paths. This PR fixes this by skipping the missing entry. Fix #16290 Signed-off-by: Andrew Thornton <[email protected]> Co-authored-by: 6543 <[email protected]> Co-authored-by: techknowlogick <[email protected]>
There is a bug with last commit cache recursive cache where the last commit information that refers to the current tree itself will cause a panic due to its path ("") not being included in the expected tree entry paths. This PR fixes this by skipping the missing entry. Fix go-gitea#16290 Signed-off-by: Andrew Thornton <[email protected]> Co-authored-by: 6543 <[email protected]> Co-authored-by: techknowlogick <[email protected]>
The latest version gitea. terminate abnormal
`2021/06/29 11:26:51 .../queue/workerpool.go:93:zeroBoost() [W] WorkerPool: 14 (for repo_stats_update-channel) has zero workers - adding 1 temporary workers for 5m0s
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0xa11e63]
goroutine 17332 [running]:
code.gitea.io/gitea/modules/git.(*TreeEntry).IsDir(...)
/go/src/code.gitea.io/gitea/modules/git/tree_entry_nogogit.go:66
code.gitea.io/gitea/modules/git.(*LastCommitCache).recursiveCache(0xc004c1d650, 0x3d94d68, 0xc0020bcfc0, 0xc003c15e00, 0xc003c15e10, 0x0, 0x0, 0x1, 0x1a, 0x25e8780)
/go/src/code.gitea.io/gitea/modules/git/last_commit_cache_nogogit.go:97 +0x4e3
code.gitea.io/gitea/modules/git.(*LastCommitCache).CacheCommit(...)
/go/src/code.gitea.io/gitea/modules/git/last_commit_cache_nogogit.go:68
code.gitea.io/gitea/modules/repository.CacheRef(0x3d94d68, 0xc0020bcfc0, 0xc005d7c000, 0xc004079aa0, 0xc003e1bcb0, 0x11, 0x76, 0xc00409f180)
/go/src/code.gitea.io/gitea/modules/repository/cache.go:47 +0x325
code.gitea.io/gitea/services/repository.pushUpdates(0xc00630cc30, 0x1, 0x1, 0x0, 0x0)
/go/src/code.gitea.io/gitea/services/repository/push.go:212 +0x1a18
code.gitea.io/gitea/services/repository.handle(0xc0011312c0, 0x1, 0x14)
/go/src/code.gitea.io/gitea/services/repository/push.go:32 +0x91
code.gitea.io/gitea/modules/queue.(*WorkerPool).doWork(0xc003cd0980, 0x3d94dd8, 0xc00558e240)
/go/src/code.gitea.io/gitea/modules/queue/workerpool.go:408 +0x9a9
code.gitea.io/gitea/modules/queue.(*WorkerPool).addWorkers.func1(0xc003cd0980, 0x3d94dd8, 0xc00558e240, 0xc005e17b00)
/go/src/code.gitea.io/gitea/modules/queue/workerpool.go:261 +0x45
created by code.gitea.io/gitea/modules/queue.(*WorkerPool).addWorkers
/go/src/code.gitea.io/gitea/modules/queue/workerpool.go:260 +0x65
Received signal 15; terminating.`
The text was updated successfully, but these errors were encountered: