Intermittent 500-errors on displaying commit #20
Labels
No Label
Service
Buildbot
Service
Chat
Service
Gitea
Service
Translate
Type
Bug
Type
Config
Type
Deployment
Type
Feature
Type
Setup
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: infrastructure/blender-projects-platform#20
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We discovered that there is (at least) one commit which is giving intermittent 500-errors when loading it.
The commit in question is https://projects.blender.org/blender/blender/commit/05952aa94d
Correlating it with the gitea-log at the time of the request, it correlates with
Note that the range ([2:1]) varies..
Grepping logs for 'GetComputedInlineDiffFor' or 'slice bounds' in the log gets 110 hits , but sometimes the error is in 'repo/diff/section_unified', sometimes in 'repo/diff/section_split'
@dr.sybren was quick to give me the line of code in the template related to the error:
Reloading the page most often results in a success, but once in 8-10 reloads it results in a 500-error with the following log-line in gitea.log.
Just had the 500 on this commit as well https://projects.blender.org/blender/blender/commit/eae36be372a6
As far as I know this is not so much a problem anymore, at least not to the extent that we should be tracking it. It's always possible for some operation to take too long and time out, but I don't think there's any specific optimization here that is so important for us.