#8042 pagure is using python2 again?
Closed: Fixed 3 years ago by pingou. Opened 3 years ago by zbyszek.

  • Describe the issue
zbyszek@krowka ~/fedora/catfish (git)-[master] % git push
Total 0 (delta 0), reused 0 (delta 0)
remote: Emitting a message to the fedmsg bus.
remote: * Publishing information for 1 commits
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 279, in post_receive
remote:     session, project, repodir, username, refname, commits, forced
remote:   File "/usr/lib/python2.7/site-packages/pagure/hooks/default.py", line 72, in send_notifications
remote:     name = pagure.lib.git.get_author(rev, repodir)
remote:   File "/usr/lib/python2.7/site-packages/pagure/lib/git.py", line 1317, in get_author
remote:     ["log", "-1", '--pretty=format:"%an"', commit], abspath
remote:   File "/usr/lib/python2.7/site-packages/pagure/lib/git.py", line 1261, in read_git_lines
remote:     args, abspath, keepends=keepends, **kw
remote:   File "/usr/lib/python2.7/site-packages/pagure/lib/git.py", line 1246, in read_git_output
remote:     **kw
remote:   File "/usr/lib/python2.7/site-packages/pagure/lib/git.py", line 1227, in read_output
remote:     out = out.rstrip("\n\r")
remote: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc4 in position 10: ordinal not in range(128)
remote: Sending to redis to log activity and send commit notification emails
To ssh://pkgs.fedoraproject.org/rpms/catfish
   8600b4d40a..c470bd56d4  master -> master

This seems to be a regression, I think I reported something like this in the past.

I believe this has been fixed, could you try again?

Metadata Update from @pingou:
- Issue assigned to pingou

3 years ago

I've received confirmation on IRC from @lsedlar that this issue is fixed :)

Metadata Update from @pingou:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

3 years ago

I don't have anything to push atm, so I can't test. But thanks for the quick response.

Login to comment on this ticket.