T266496 Not possible to add new statements with any Math properties (original) (raw)

Not possible to add new statements with any Math properties

Closed, ResolvedPublic8 Estimated Story Points

It seems it is currently not possible to add new statements with the math datatype. Because of some still unknown error, the js frontend is using {"value":"a + b","type":"unknown"} in its requests, both for wbformatvalue and wbsetclaim.

This might have started with -wmf.11, but it could also be that this is when T266493 started to happen.

Editing the value (in the existing statement) is not possible as well.

Reproducing the issue: edit https://test.wikidata.org/wiki/Q516#P717 and try to save the changed value. Observe the error preventing saving of the new value.

The reason seems to be this change:
T266496#6584787

Notes:

Acceptance criteria

Event Timeline

Addshore renamed this task from Not possible to add any Math properties to Not possible to add new statements with any Math properties.Oct 26 2020, 6:22 PM

Comment Actions

Comparing the request pattern for strings vs the math datatype highlights the issue.

String (parse then format)

https://test.wikidata.org/w/api.php?action=wbparsevalue&format=json&parser=string&values=23&errorformat=plaintext&uselang=en&options={"lang":"en"} https://test.wikidata.org/w/api.php?action=wbformatvalue&format=json&datavalue={"value":"23","type":"string"}&generate=text/html; disposition=verbose-preview&property=P95180&errorformat=plaintext&uselang=en&options={"lang":"en"}

Math (only a format with the JS specifically stating the value is unknown as no parse has happened )

https://test.wikidata.org/w/api.php?action=wbformatvalue&format=json&datavalue={"value":"23","type":"unknown"}&generate=text/html; disposition=verbose-preview&property=P719&errorformat=plaintext&uselang=en&options={"lang":"en"}

Comment Actions

In case it helps: I had been able again to add math values for some time last week, but now it fails again.

Comment Actions

As @Lucas_Werkmeister_WMDE mentioned in mattermost, there seems to have been a regression in wmf.16 and we will need to backport the revert in T266671 back up. The permanent fix should be rolling out with wmf.18.

Comment Actions

It probably makes sense to wait with verifying this until next week, so that we verify not just the backported revert (wmf.16) but also the proper fix (wmf.18).

Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL · Credits