jbauer
opened 2 years ago
-
Is this the first time you encounter the issue?
-
No, it was the third time. The first time was right after upgrading from 9.1.2 to 9.1.5. The second time was after restoring 9.1.5 after the failed upgrade to 9.1.9. The third time happened yesterday because I did some docker maintenance and OneDev had to restart. So the only common thing was a restart of OneDev and that I visited the files view, switched the branch and clicked the build spec in that newly selected branch.
Since it happened now 3 times I reported it.
-
/opt/onedev/is a mounted Docker NFS volume so reading repository files might be a little slower than having files locally stored.volumes: onedev: driver_opts: type: "nfs" o: "addr=<nfs-server-ip>,nolock,soft,rw,nfsvers=4,sync" device: ":/published/nfs/path/to/onedev"Maybe that helps.
-
Name Previous Value Current Value Priority
Normal
Minor
-
OneDev
changed state to 'Closed' 2 years ago
Previous Value Current Value Open
Closed
-
State changed as code fixing the issue is committed (51add1c1)
-
OneDev
changed state to 'Released' 2 years ago
Previous Value Current Value Closed
Released
-
State changed as build #4129 is successful
-
Hehe, amusing fix. Looks like you could not reproduce it?
-
I can not reproduce it. But such error is possible with Wicket when component state is not updated in time, and generally do not do any harm. So I just suppress it.
| Type |
Bug
|
| Priority |
Minor
|
| Assignee | |
| Affected Versions |
9.1.5
|
| Labels |
No labels
|
I opened project files, then changed the branch from default branch to a feature branch and then opened the
.onedev-buildspec.ymlfile. The UI appeared for a second and then the error page appeared.Then I hit the "go back" button on the error page and did the above again but no exception occurred. Might be difficult to reproduce. I am pretty sure that the above order of actions has been done the first time after a OneDev restart. So maybe the error occurs if caches are not filled and code is a little slower.