|
Jerome St-Louis opened 1 month ago
|
|||||||||
|
What url you are accessing? |
|||||||||
|
|
||||||||||
|
|
@robin Interestingly (and this is reassuring for the issue data still being there), the mentioned object ID definitely is a commit that I still have in my local workspace. |
|||||||||
|
|
When displaying the issue, OneDev also checks git commit it associated with. Maybe that commit is missing. Please show me the full stack trace. |
|||||||||
|
|
@robin That is the only information that is displayed in the 500, not any other detail. I tried to push the commit again to a branch to the server and I can see the commit fine at: https://example.com/myproject/~commits/fbee0d4c1bd947315b0db3d81fa639525e34ed39 but I still get the error at the issue URL (with no details). Is there a way to get a more detailed stack trace? |
|||||||||
|
|
Please check the server log to see if there is more info there. |
|||||||||
|
|
@robin I don't see anything in the server log, but there seems to be nothing there for the last 5 days which is odd. I tried to restart the server, and it does write a new server.log, but it doesn't write anything there when trying to access the issue. |
|||||||||
|
|
Please make sure you are on 9.2.3, then copy attached file to |
|||||||||
|
|
|
|||||||||
|
|
Jerome St-Louis changed fields 1 month ago
|
|||||||||
|
|
Seems that this issue is referenced from a code comment on commit |
|||||||||
|
|
Robin Shen changed fields 1 month ago
|
|||||||||
|
|
@robin Thanks I didn't notice that the detailed error log had a different commit ID (I had pushed a branch with first lost commit). I pushed this new commit again (which luckily I still had locally) and that did solve the problem and my issue 238 is now back!! However, it is a major bug on a number of levels that compounded into completely losing access to the issue, and all of these should be fixed:
Code comments are almost always on draft commits that will not end up integrated, so when the branches are gone because the improved version gets merged (we started to try cleaning up branches upon merging), this will always happen, so this is a very common scenario, not a special rare one. However, the code comments are still useful documentation, so a setting could let the administrator decide to either:
How can I know which commit this is on: https://example.com/myproject/~code-comments/4/invalid ? I would like to see the commit ID so that I can revive it. But I don't really want to keep branches around only to keep those code comments alive. |
|||||||||
|
|
Filed an improvement request (#1624) to show code comment detail upon commit GC. As to an option to tag commit to avoid being GCed, it may bloat the ref database. |
|||||||||
|
|
Robin Shen changed state to 'Closed' 1 month ago
|
|||||||||
|
|
Replaced with #1625 which describes the problem more accurately. |
| Type |
Bug
|
| Priority |
Major
|
| Assignee | |
| Affected Versions |
9.2.3
|
| Labels |
No labels
|
Issue Votes (0)
Watchers (4)
I just noticed that an issue no longer exists on our instance. I get the 500 Panda:
This only happens for this specific issue, but it is worrisome, because this is already a significant loss of useful information in this one issue. We are using PostgreSQL as a backend. How could we assess what went wrong? I do suspect a critical OneDev bug.
The message mentions that it cannot find a commit.
Is the issue still there and fine, and it just has a reference to a commit that perhaps no longer exists, but as a result even the issue cannot be displayed? (this should not result in a 500).