#2597 Pagure hook handling failure
Closed: Fixed 6 years ago Opened 6 years ago by rharwood.

Working with the gssproxy project, I pushed a new commit and it produced the following output

rharwood@seton:~/gssproxy.git/master$ git push upstream
Counting objects: 6, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (6/6), done.
Writing objects: 100% (6/6), 612 bytes | 306.00 KiB/s, done.
Total 6 (delta 5), reused 0 (delta 0)
remote: Sending to redis to log activity and send commit notification emails
remote: Emitting a message to the fedmsg bus.
remote: * Publishing information for 1 commits
remote: Sending notification emails to: gss-proxy@lists.fedorahosted.org
remote: Detailed log of new commits:
remote: 
remote: 
remote: * commit adb74c062e46363dfac99fabc674edcdef2de698
remote: * Author: Simo Sorce <simo@redhat.com>
remote: * Date:   Thu Aug 31 14:52:17 2017 -0400
remote: * 
remote: * Style fixes
remote: * 
remote: * Signed-off-by: Simo Sorce <simo@redhat.com>
remote: * Reviewed-by: Robbie Harwood <rharwood@redhat.com>
remote: * Merges: #210
remote: No user "simo@redhat.com" found
remote: No user "simo@redhat.com" found
To ssh://pagure.io/gssproxy.git
   60aee2c..adb74c0  master -> master
rharwood@seton:~/gssproxy.git/master$ 

It seems to have also not fully processed the "Merges" directive, which I assume is related. Thanks!


So the root cause of this is that we're using the author of the commit as the person doing the action and apparently Simo did not register his @rh email in pagure.io.

This also explains why the Merges did not get taken into account.

It's the same cause that would make you appear as doing a rebase if I rebase and push to your fork one of your commit.

Short term, you could just ask Simo to register that email address, long term I'm going to try fixing this in pagure itself.

Metadata Update from @pingou:
- Issue tagged with: bug

6 years ago

Metadata Update from @pingou:
- Issue assigned to pingou

6 years ago

Login to comment on this ticket.

Metadata