Bugzilla – Full Text Bug Listing
| Summary: | Cannot update my own patches | ||
|---|---|---|---|
| Product: | Community | Reporter: | Salome Maro <salomehonest> |
| Component: | Gerrit | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | ec, frederic.gurr, mikael.barbero |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X | ||
| Whiteboard: | |||
| Bug Depends on: | 530205 | ||
| Bug Blocks: | |||
|
Description
Salome Maro
This sounds like https://bugs.eclipse.org/bugs/show_bug.cgi?id=525553 . I'm going to close this as a dupe, but please reopen if you think it's different. -M. *** This bug has been marked as a duplicate of bug 525553 *** Hi, In bug 525553 the bug is fixed in version 2.13.9. I still experience the problem though. Does this mean that the gerrit version used by org.eclipce.capra is outdated? In bug 525553 the problem seems to occur only when draft changes have been made, but in my case I have no drafts. I am reopening the bug because I am still experiencing the issue. thanks, Salome. (In reply to Eclipse Webmaster from comment #1) > This sounds like https://bugs.eclipse.org/bugs/show_bug.cgi?id=525553 . > > I'm going to close this as a dupe, but please reopen if you think it's > different. > > -M. > > *** This bug has been marked as a duplicate of bug 525553 *** Hey, I am a committer on the same project and am now experiencing similar behaviour. I just pushed changes to a new branch jsteghofer/feature/marker-handler and cannot access them via Gerrit. When I navigate to https://git.eclipse.org/r/111765 I get the message that access is forbidden. Could this have to do something with the branch name? I am able to access Salome's changes. Best, Jan-Philipp This issue has not been solved for us. We still cannot access the patches we submitted ourselves to a personal feature branch on Gerrit. Here are some steps to reproduce this. 1. Branch an Eclipse project (in our case Eclipse Capra) and create a branch pre-fixed by username (e.g., jsteghofer/feature/test) 2. Make a commit and push it to Gerrit Expected behaviour: a) the change should show up in the dashboard of the submitter (https://git.eclipse.org/r/#/dashboard/self) b) it is possible to submit new patchsets to update the change by pushing to Gerrit Actual behaviour: a) the change does not appear in the dashboard and it's not possible to access the change directly (Error Message: "Code Review - Error The page you requested was not found, or you do not have permission to view this page.") b) git denies any pushes that update the change with a permission error We noticed that your commit message in https://git.eclipse.org/r/111765 does not contain a change-ID. This could be (part of) the reason why it does not work. Please try it again with a change-ID in your commit message. Hey Frederic, thank you for responding. Unfortunately, the change-ID in the commit message is not the cause of the problems. Even if the change-ID is contained in the commit to update a patchset (by amending the previous commit and changing the commit message), git rejects the commit because of a permission error. The other issue that is (I believe) related is that we can't access the changes in Gerrit, also with a permission error. I suspect it has something to do with the fact that we are pushing to user-branches which is AFAIK the preferred way to have feature branches for Eclipse projects. Thanks for the feedback. Does it work for you on non-user-branches and/or other repositories? Yes, I can see changes that I pushed to the develop branch and update those changes as well. Hi Frederic, Do you have any suggestions of how we can solve this issue? As Jan-Philipp mentioned, the problem only occurs on user branches and not our develop branch. Currently I'm at a loss here. I will try to look into it next week though. Do you still face the issue? We have not had a use case of updating patches to own beaches ever since we started having this problem. We will check and get back if the error still persists. However, we noticed that other people who are not eclipse committers but have an eclipse account and have signed an ECA are not able to create their own user branches. Could this be a related issue? Should non-committers be able to create user branches at all, or is this only possible for the project committers? (In reply to Salome Maro from comment #12) > Should non-committers be able to create user branches at all, or is this only > possible for the project committers? Branch creation(either public or in refs/for/$user) should be limited to project committers only. -M. I confirm that it is now possible to update one's own patches and this bug no longer exists. Therefore closing the issue. |