CT export fails if non-ASCII in protocol

Issue #644 resolved
Ed McDonagh created an issue

As reported by Kari Slyngstad Helland

Comments (5)

  1. Ed McDonagh reporter

    Remove attempt to convert series acquisition protocol to string as it gets done safely later. Refs #644. Remove two uses of str() for cid lookups (although they are safe as we know the contents are ASCII).

    → <<cset 75b682060121>>

  2. Ed McDonagh reporter

    Modified CT RDSR to enable testing of issue with ref #644 with export with non-ascii protocol name at acquisition level. Modified import test to suit.

    → <<cset ff2e81b82da4>>

  3. Log in to comment