dimagi / couchforms

51%

master: 64%

LAST BUILD ON BRANCH nonascii

branch: nonascii

CHANGE BRANCH

x

Reset

• nonascii
• 1.0.1
• 3.0.2
• 500-to-404
• 90086
• assert
• authcontext
• autostaging
• autostaging-newdbs
• autostaging-olddbs
• ax-by-user
• build-id
• case_file_name_error
• clean-up-form
• cleanup
• comment_on_view
• convert_xform_to_json
• dead-views
• disable-restore
• django-1.5
• django-TestCase
• encodings
• es-p
• explicit-form-properties
• extract-receiver-request
• fix-conflict-handling
• fix-download-attachments
• fix-error-handling
• fix-tests
• fix-unicode-form-fail
• form-archival
• form-locking
• get_forms_by_user
• gps
• handle-conflicting-id
• headers-default
• jsonobject
• locking
• master
• memoize-instance
• meta-dates
• meta_fixes
• move-form_data-into-commcarehq
• no-timezones
• parse_date-tz
• post-tests
• psu_fix
• refactor
• remove-receiver
• remove-w=3
• rename-get
• replace-update
• show-auth-user
• simplify-error-logging
• single_form_view
• staging2
• streamline
• test-meta
• ui-fail-gracefully
• unicode-error-message
• unicode-fix
• unicode-test
• unicoding
• unknown-users
• up-lock-timeout
• url-future
• url-hotfix

Build # 22

Build Type

push

travis-ci

Committed by mwhite

Commit Message

handle error with invalid unicode strings (Case:60590)

A device log was submitted containing a string that causes an error when
trying to decode to UTF-8, an invalid diacritical mark (the string was
an error message for CommCare's inability to decode this string!).

Rather than fail here we choose Python's 'replace' error-handling
method, which seems to just keep the invalid diacritic in a way that it
still gets displayed by browsers, etc.

Run Details

5 of 5 new or added lines in 1 file covered. (100.0%)

288 of 570 relevant lines covered (50.53%)

0.51 hits per line