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

Fix Server response could not be decoded using UTF-8 #1623

Merged
merged 5 commits into from Feb 2, 2020
Merged

Fix Server response could not be decoded using UTF-8 #1623

merged 5 commits into from Feb 2, 2020

Commits on Nov 19, 2019

  1. Fix utf-8 decode error

    @rikonaka
    rikonaka committed Nov 19, 2019
    Configuration menu
    Copy the full SHA
    84a2a14 View commit details
    Browse the repository at this point in the history

  2. The final solution, no longer processing any data that cannot be proc… 

    …essed
    @rikonaka
    rikonaka committed Nov 19, 2019
    Configuration menu
    Copy the full SHA
    f52d805 View commit details
    Browse the repository at this point in the history

  3. no need to test the invalid json data now, because the decode('utf-8'… 

    …, 'replace') will nerver raise an error
    @rikonaka
    rikonaka committed Nov 19, 2019
    Configuration menu
    Copy the full SHA
    3fb8dbe View commit details
    Browse the repository at this point in the history

Commits on Feb 2, 2020

  1. restored test_request.py and make it sound

    @tsnoam
    tsnoam committed Feb 2, 2020
    Configuration menu
    Copy the full SHA
    7a84478 View commit details
    Browse the repository at this point in the history

  2. Merge remote-tracking branch 'origin/master' into pr1623 

     Conflicts:
	AUTHORS.rst
    @tsnoam
    tsnoam committed Feb 2, 2020
    Configuration menu
    Copy the full SHA
    ef336e0 View commit details
    Browse the repository at this point in the history