-
Additional information after more research: this (mostly, but not only) seems to happen when there's a branch protection rule that protects
.onedev-buildspec.ymlfrom modifications. -
Please check branch protection rule of branch of the file you are opening, and share value of reviewers property of all file protection rules.
-
Please use
group(Software-Devs):1instead. -
The error still persists (also still with the two different messages depending on how I open the page).
-
Oh, and I should probably say that it works if I use a user that is part of said group. Sorry for not mentioning that earlier.
-
Can not reproduce. Please attach a sample onedev directory zip demonstrating this issue (start OneDev via docker, and zip the onedev data directory on host).
-
Please reopen if there is more info. Also note that no any spaces are allowed in
group(Software-Devs):1 -
Previous Value Current Value Open
Closed
-
Hi Robin,
sorry for not replying earlier. We can not replicate this on a fresh install at the moment. Is there any (other) way how we can get more information about the issue? We assume it might be something with our local installation especially since we also get the first error every now and then when quickly going back to the previous page in the browser (like, open .onedev-buildspec.yml and immediately use the back button of the browser to go one page back).
Is there f. e. an option to get the full stack trace, possibly even with some context?
Thanks Sebastian
-
You may create a new instance by copying your current instance (database and the project experiencing the issue), delete all sensitive data to see if the issue can be reproduced. Then attach OneDev data directory here.
| Type |
Bug
|
| Priority |
Normal
|
| Assignee | |
| Affected Versions |
latest
|
| Labels |
No labels
|
Since the last update(s?), we get "An unexpected exception occurred" when opening certain
.onedev-buildspec.ymlfiles.When selecting the file through the Code-view of the project, we get forwarded to
/wicket/page?90and the following error details are shown:When directly accessing the file, for example by opening the link in a new tab, we are not forwarded and get this error instead: