On Fri, Feb 27, 2015 at 5:33 PM, Lydia Pintscher
lydia.pintsc...@wikimedia.de wrote:
Those were empty in the UI as well. I deleted them. This should
hopefully fix it. We need to investigate if adding those empty
references is still possible.
For reference: The edits that introduced them were
On Thu, Feb 26, 2015 at 2:52 PM, Markus Kroetzsch
markus.kroetz...@tu-dresden.de wrote:
Hi,
It's that time of the year again when I am sending a reminder that we still
have broken JSON in the dump files ;-). As usual, the problem is that empty
maps {} are serialized wrongly as empty lists [].
On 27.02.2015 17:47, Lydia Pintscher wrote:
On Thu, Feb 26, 2015 at 2:52 PM, Markus Kroetzsch
markus.kroetz...@tu-dresden.de wrote:
Hi,
It's that time of the year again when I am sending a reminder that we still
have broken JSON in the dump files ;-). As usual, the problem is that empty
maps
On 2015-02-27 09:11, Markus Kroetzsch wrote:
Since the JSON dumps and EntityData exports are (largely) free of
errors, there is already code for fixing this problem. Maybe we could
just use this.
Tracked in: https://phabricator.wikimedia.org/T64188 Replace old
serialization code in lib with
On Fri, Feb 27, 2015 at 10:38 AM, Markus Kroetzsch
markus.kroetz...@tu-dresden.de wrote:
Hi,
In my previous post, I mentioned that there are very few empty-map issues
remaining in the JSON dumps as well. I think there are only two right now:
Lydia, I think the serializer should just drop empty references. Shall we make a
ticket for that?
I'm confused though why we still see issues in the XML. We *should* be
re-serializing all output now. But it's hard to find out what's actually going
on on the dump servers...
Am 27.02.2015 um 17:35
Am 27.02.2015 um 12:33 schrieb Dimitris Kontokostas:
Standard XML MW format exists for long time and is supported by existing
software.
IMHO both XML and Json dumps should be treated with the same priority
They should, in fact, be using the same code
--
Daniel Kinzler
Senior Software
Am 27.02.2015 um 15:33 schrieb Jan Zerebecki:
On 2015-02-27 09:11, Markus Kroetzsch wrote:
Since the JSON dumps and EntityData exports are (largely) free of
errors, there is already code for fixing this problem. Maybe we could
just use this.
Tracked in:
AFAIK there is no php involved in the dump process (python?)
There was a mail that announced a switch to the new serialisation format
in July 2014
[https://lists.wikimedia.org/pipermail/wikidata-l/2014-July/004225.html]
And some other mails adressing the JSON-Problem in Sep. 2014
Hi Stas,
Since the JSON dumps and EntityData exports are (largely) free of
errors, there is already code for fixing this problem. Maybe we could
just use this.
Cheers,
Markus
On 27.02.2015 01:06, Stas Malyshev wrote:
Hi!
It's that time of the year again when I am sending a reminder that
On 26.02.2015 21:40, Martynas Jusevičius wrote:
Looks like someone hasn't learned the lesson:
https://www.mail-archive.com/wikidata-l@lists.wikimedia.org/msg02588.html
No, this post is unrelated. The cause of the problem was correctly
analysed by Stas.
Markus
On Thu, Feb 26, 2015 at 9:27
11 matches
Mail list logo
