-
Notifications
You must be signed in to change notification settings - Fork 205
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
added unescape for email text body to avoid encoded characters #517
Conversation
cc @amercader @avdata99 , this is due to data.gov email formatting problems. |
@jbrown-xentity , I think it's good for Python 3 but we need to cover Python 2 users (CKAN <= 2.9-py2) users |
Thanks @avdata99 , we'll push something with |
@jbrown-xentity, this repository takes care of the minutes to execute the GitHub actions. This is why it requires the authorization of a repository administrator user to run. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@amercader can you take a look? |
@amercader ping? |
The harvest report emails sent to users contains encoded characters, like
'
and"
This makes it hard for users to understand the error message. For example:
before
ERROR #1: 'description':'' is too short.
after
ERROR #1: 'description':'' is too short.