DescriptorReader gets confused by files containing multiple descriptors if they contain non-ASCII characters
When parsing a file containing multiple server descriptors with DescriptorReader, the file content is first separated into parts starting with "router ", and these chunks are then parsed. However, it seems we have an encoding problem there:
If a server descriptor contains non-ASCII characters, like in its platform or contact line, we don't cut off at the right character, so that the next descriptor seems to start with "\nrouter ". Empty lines are not allowed, so we don't accept that descriptor.
What's funny is that this problem only happens on the console, not when run in Eclipse. Probably related to different locale settings.
Not sure what the right fix is. Maybe we should split input strings as long as they're contained in byte[].
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information