Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Manage non-ascii PG errors #167

Merged
merged 3 commits into from
Jan 28, 2016
Merged

Manage non-ascii PG errors #167

merged 3 commits into from
Jan 28, 2016

Commits on Dec 28, 2015

  1. Manage non-ascii PG errors 

    When PG is localized, error messages are not ascii and jobs are not postponed. Instead they are failed with a 'unicode decode error'.

Note: even if PG ```lc_messages``` is set to en_us.utf8 on a localized system, the error message prefixes (such as ```DETAILS:```) are still localized.
    @npiganeau
    npiganeau committed Dec 28, 2015
    Configuration menu
    Copy the full SHA
    ebb81b8 View commit details
    Browse the repository at this point in the history

  2. Removed trailing whitespace

    @npiganeau
    npiganeau committed Dec 28, 2015
    Configuration menu
    Copy the full SHA
    e66b0f2 View commit details
    Browse the repository at this point in the history

Commits on Jan 4, 2016

  1. Use tools.ustr() instead of unicode()

    @npiganeau
    npiganeau committed Jan 4, 2016
    Configuration menu
    Copy the full SHA
    6c32f93 View commit details
    Browse the repository at this point in the history