#4813 pagure.io: traceback in post_receive hook: "TypeError: unhashable type: 'list'"
Opened 2 years ago by decathorpe. Modified 2 years ago

I've set up a new project (pantheon-fedora/wingpanel-indicator-ayatana) and pushed an existing repository to pagure, and got this Traceback from the post_receive hook:

wingpanel-indicator-ayatana]$ git push -u origin master
Enumerating objects: 197, done.
Counting objects: 100% (197/197), done.
Delta compression using up to 16 threads
Compressing objects: 100% (92/92), done.
Writing objects: 100% (197/197), 90.43 KiB | 90.43 MiB/s, done.
Total 197 (delta 108), reused 188 (delta 103), pack-reused 0
remote: Has commit access: True
remote: Has commit access: True
remote: Traceback (most recent call last):
remote:   File "/usr/lib/python2.7/site-packages/pagure/hooks/__init__.py", line 394, in run_project_hooks
remote:     changes=changes,
remote:   File "/usr/lib/python2.7/site-packages/pagure/hooks/__init__.py", line 111, in runhook
remote:     changes=changes,
remote:   File "/usr/lib/python2.7/site-packages/pagure/hooks/default.py", line 425, in post_receive
remote:     oldrev,
remote:   File "/usr/lib/python2.7/site-packages/pagure/hooks/default.py", line 175, in send_notifications
remote:     auths.add(author)
remote: TypeError: unhashable type: 'list'
remote: Sending to redis to log activity and send commit notification emails
To ssh://pagure.io/pantheon-fedora/wingpanel-indicator-ayatana.git
 * [new branch]      master -> master
Branch 'master' set up to track remote branch 'master' from 'origin'.

Though the repository contents look fine at first glance.


Would you be able to point me to the git repo? https://pagure.io/pantheon-fedora/wingpanel-indicator-ayatana doesn't seem to exist (anymore?)

I found a copy of the repo in my backups. I re-created the original setup and was able to trigger the same issue again by just running git push in the newly re-created repo on pagure:

[deca@asusdora wingpanel-indicator-ayatana]$ git push -u origin master
Enumerating objects: 195, done.
Counting objects: 100% (195/195), done.
Delta compression using up to 16 threads
Compressing objects: 100% (104/104), done.
Writing objects: 100% (195/195), 92.21 KiB | 46.10 MiB/s, done.
Total 195 (delta 104), reused 165 (delta 89), pack-reused 0
remote: Has commit access: True
remote: Has commit access: True
remote: Traceback (most recent call last):
remote:   File "/usr/lib/python2.7/site-packages/pagure/hooks/__init__.py", line 392, in run_project_hooks
remote:     changes=changes,
remote:   File "/usr/lib/python2.7/site-packages/pagure/hooks/__init__.py", line 111, in runhook
remote:     changes=changes,
remote:   File "/usr/lib/python2.7/site-packages/pagure/hooks/default.py", line 425, in post_receive
remote:     oldrev,
remote:   File "/usr/lib/python2.7/site-packages/pagure/hooks/default.py", line 175, in send_notifications
remote:     auths.add(author)
remote: TypeError: unhashable type: 'list'
remote: Sending to redis to log activity and send commit notification emails
To ssh://pagure.io/pantheon-fedora/wingpanel-indicator-ayatana.git
 * [new branch]      master -> master
Branch 'master' set up to track remote branch 'master' from 'origin'.

repo is again available at https://pagure.io/pantheon-fedora/wingpanel-indicator-ayatana


If it helps, this git repo was originally imported from bzr (on launchpad), maybe that created some kind of artifact in the git history that pagure doesn't like to handle?

Hm, I can't reproduce this from a clone of that repo. Could you by any chance send me a tarball of the git repo you've pushed?

Did that work?

Looks like, but I still can't reproduce here. Maybe my setup is wrong

Or, now that I see it, maybe this is a py2 vs py3 thing.

Login to comment on this ticket.

Metadata
Attachments 1