User Details
- User Since
- Nov 26 2021, 3:08 PM (142 w, 4 d)
- Availability
- Available
- LDAP User
- Ollie Shotton
- MediaWiki User
- Ollie Shotton (WMDE) [ Global Accounts ]
Today
Yesterday
Fri, Aug 16
- A description has been added to all the graphs (the little (i) icon)
- Yes, this is currently the median latency of successful requests (have specified in the description). The legend isn't sorted by default. Silvan has added Min/Max values to the legend, which you can click on to sort ascending or descending. NOTE: it is the min and max of the median latency for the selected time period - not the min/max latency.
- I've separated these into two different graphs (and you are right, it's not possible to do it per error-code with the data we are currently provided)
Thu, Aug 15
Wed, Aug 14
I found something that's not ideal about the context.
For Item/Property/Statement it fine for the context to be { "parameter": "item_id" }, { "parameter": "property_id" }, or { "parameter": "statement_id" }.
For label/description/aliases in language, { "parameter": "language_code" } doesn't work as well - it's more the combination of item_id/property_id and language_code that is incorrect.
For sitelink not found for site id, { "parameter": "site_id" } also doesn't work - it's not the site with site_id that doesn't exist (that would result in an invalid-path-parameter error).
Dumping some of my thoughts here as I might not be in polishing.
Okay, I did some digging around the different "invalid operation" errors a PATCH request can return. The OAS seems to be correct as far as I can tell.
Tue, Aug 13
I think the request you posted would have passed before we made this change as well. The three cases where this error would have been returned are:
- a POST /entities/items request with an extra field in the item object
- a PATCH /entities/items request that results in an item that has an extra field, i.e. { "patch": [ { "op": "add", "path": "/foo", "value": "bar" } ] }
- a PATCH /entities/properties request that results in an item that has an extra field, i.e. { "patch": [ { "op": "add", "path": "/foo", "value": "bar" } ] }
Thanks Ifrah, that's helpful. I can pick this task up while Silvan is away.
Fri, Aug 9
Thu, Aug 8
Adding the related GitHub PR here for reference:
Wed, Aug 7
Thanks for persevering with this Silvan!
Tue, Aug 6
Mon, Aug 5
Thu, Aug 1
Wed, Jul 31
We missed the item-not-a-badge case 🙈
Tue, Jul 30
Mon, Jul 29
Thu, Jul 25
Wed, Jul 24
Mon, Jul 22
Jul 17 2024
Jul 15 2024
@Muhammad_Yasser_Jazirahly_WMDE found an issue, moving back to doing.