Last modified: 2013-08-14 12:11:36 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T54605, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 52605 - ParserOutput::setProperty with an array sometimes fails
ParserOutput::setProperty with an array sometimes fails
Status: NEW
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
1.22.0
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-08-07 08:39 UTC by Kunal Mehta (Legoktm)
Modified: 2013-08-14 12:11 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Kunal Mehta (Legoktm) 2013-08-07 08:39:27 UTC
If you set an array with ParserOutput::setProperty, sometimes it will fail, and sometimes it won't.

According to Roan, it should either always work or always fail.
Comment 1 Gerrit Notification Bot 2013-08-07 08:53:51 UTC
Change 78028 had a related patch set uploaded by Legoktm:
Store the targets list as a serialized string due to bug 52605

https://gerrit.wikimedia.org/r/78028
Comment 2 Gerrit Notification Bot 2013-08-07 08:55:19 UTC
Change 78028 merged by jenkins-bot:
Store the targets list as a serialized string due to bug 52605

https://gerrit.wikimedia.org/r/78028
Comment 3 Kunal Mehta (Legoktm) 2013-08-07 08:56:18 UTC
Err, that patchset doesn't address this bug, just works around it. Didn't realize the bot would do that, sorry.
Comment 4 db [inactive,noenotif] 2013-08-09 09:59:32 UTC
The doc does not say the datatype for a property, but it should be a string, because it is stored in a blob in the database

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links