** Changed in: php-json (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1287726
Title:
Wrong evaluation whether json is valid or not
To manage notification
(and I'm unsubscribing ~ubuntu-sponsors for now)
** Changed in: php-json (Ubuntu Trusty)
Status: Triaged => Incomplete
** Changed in: php-json (Ubuntu Wily)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
@Mathew,
I see that you subscribed ~ubuntu-sponsors. But I don't think Nish
intended an upload yet. The SRU paperwork is not done yet, and there are
outstanding questions as to whether his proposed fix works.
I think this is awaiting someone affected to report back, so I'm marking
this Incomplete
This is Fix Released in Xenial and Yakkety by virtue of PHP 7 not using
php-json any more I presume?
** Also affects: php-json (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: php-json (Ubuntu Wily)
Importance: Undecided
Status: New
** Changed in: php-json (
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1287726
Title:
Wrong evaluation whether json is valid or not
To manage notifications about this bug go to:
https://bugs.launchpad.
Note that in PHP7.0, the provided test behaves slightly differently, I
would appreciate any insight into understanding if it is correct:
var_dump(bin2hex(json_decode($json, true, 2)));
returns string(0) ""
$t = json_decode($json, true, 2); for the Index and Property cases
returns NULL.
--
You
@shankoa Thank you for notifying us that the fix has occurred upstream!
@anyone affected: I have backported that fix and the test to Trusty and
WIly versions of php-json, available at:
https://launchpad.net/~nacc/+archive/ubuntu/lp1287726. Could you please
test and confirm if these resolve the iss
** Changed in: php-json (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1287726
Title:
Wrong evaluation whether json is valid or not
To manage notifications abo
** Bug watch added: Debian Bug tracker #801962
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801962
** Also affects: php-json (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801962
Importance: Unknown
Status: Unknown
--
You received this bug notification because
This seems to have been recently fixed in upstream json-c: see last
comments in https://github.com/remicollet/pecl-json-c/issues/9
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1287726
Title:
Wrong
On a fundamental level, the provided replacement doesn’t match PHP
Documentation about behaviour.
Json_decode() is described to return NULL on invalid UTF-8 sequence, and set an
error message of JSON_ERROR_UTF8.
Current behaviour with json-c is returns JSON_OK, and returns an invalid string
that
On Tue, Apr 22, 2014 at 11:31:36AM -, Mads Martin Jørgensen wrote:
> 3) Move all servers that use JSON away from Ubuntu and on to something
> with a JSON standard conforming php-json.
For other readers, I would point out that AIUI Fedora (and thus RHEL and
CentOS) and Debian (and thus Ubuntu)
I cannot specify it further, since it's our own API that communicates
via JSON that broke, due to php-json in Ubuntu not conforming to the
JSON standard. Time will tell how many will get hit by this bug. Might
be zero, might be thousands. Fact of the matter is still that it accepts
JSON input that
On Mon, Apr 14, 2014 at 06:10:31PM -, Mads Martin Jørgensen wrote:
[...]
> ...All of
> the services provided on a Ubuntu system will potentially break, since
> it does not conform to the json standard that everyone else does.
That d
Problem is that the old php-json package conforms to the json standard,
and the new one does not. If someone went through the effort (we do not
have the resources, unfortunately) to make json-c conform to the json
standard with said flag, then yes - you could simply compile the package
with that fl
Thank you for following this up.
14.04 is just round the corner now, so it seems unlikely that any
further changes can be made now.
It sounds like json-c upstream are willing to have the behaviour in the
presence of the flag. Does this mean that php-json could use the flag by
default, and thus re
This also means, that unless the Ubuntu maintainer fixes it either way,
then php-json has a rather important change in behaviour between 12.04
LTS and 14.04 LTS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
So the upstream json-c developers don't consider this a bug:
"Oh, I see. You want json-c to validate that the input being parsed actually is
UTF-8. While that might seem reasonable to do at first glance, json-c has
historically supported something closer to exact, uninterpreted bytes for
string
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Looks like this is upstream bug https://github.com/remicollet/pecl-
json-c/issues/9, and it is suggested that the problem needs to be fixed
in libjson-c which is at https://github.com/json-c/json-c
This bug will p
19 matches
Mail list logo
