[
https://issues.apache.org/jira/browse/MESOS-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15271364#comment-15271364
]
Alexander Rukletsov commented on MESOS-2013:
--------------------------------------------
Right, prioritization comes straight after naming ; ). I thought we fixed the
problem _partially_ with
https://github.com/apache/mesos/commit/58e273524318163684d96d618155a9d68d0de9fc#diff-f42c18b495fd39d2cef5d861cad9a1de,
didn't that help in your case? Also, I'm very pleased to hear that this is the
most unpleasant issue you have with Mesos so far ; )
> Slave read endpoint doesn't encode non-ascii characters correctly
> -----------------------------------------------------------------
>
> Key: MESOS-2013
> URL: https://issues.apache.org/jira/browse/MESOS-2013
> Project: Mesos
> Issue Type: Bug
> Components: json api
> Reporter: Whitney Sorenson
> Assignee: Anand Mazumdar
>
> Create a file in a sandbox with a non-ascii character, like this one:
> http://www.fileformat.info/info/unicode/char/2018/index.htm
> Hit the read endpoint for that file.
> The response will have something like:
> data: "\u00E2\u0080\u0098"
> It should actually be:
> data: "\u2018"
> If you put either into JSON.parse() in the browser you will see the first
> does not render correctly but the second does.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
