#1829: PBChangeSource loses string encodings
---------------------+--------------------
Reporter: dustin | Owner:
Type: defect | Status: new
Priority: minor | Milestone: 0.8.4
Version: master | Resolution:
Keywords: encoding |
---------------------+--------------------
Comment (by dustin):
I suspect that the right solution here is to allow the sendchange user to
specify an encoding for the command line (defaulting to the Python
filesystem encoding?), and decode from that encoding to unicode strings
before sending to PBChangeSource.
I don't recall how well PB handles unicode, so that should be tested in a
unit test that will detect any failures in older versions.
PBChangeSource should be resilient by trying to decode any raw bytestrings
it receives as ascii with replacement.
--
Ticket URL: <http://trac.buildbot.net/ticket/1829#comment:2>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
Index, Search & Analyze Logs and other IT data in Real-Time with Splunk
Collect, index and harness all the fast moving IT data generated by your
applications, servers and devices whether physical, virtual or in the cloud.
Deliver compliance at lower cost and gain new business insights.
Free Software Download: http://p.sf.net/sfu/splunk-dev2dev
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
