User Details
- User Since
- Jan 6 2020, 4:43 PM (319 w, 1 d)
- Availability
- Available
- LDAP User
- Silvan Heintze
- MediaWiki User
- Silvan Heintze (WMDE) [ Global Accounts ]
Fri, Feb 13
Thu, Feb 12
Mon, Feb 9
Fri, Feb 6
First draft: https://www.wikidata.org/wiki/User:Silvan_Heintze_(WMDE)/Wikibase_GraphQL. Maybe review comments can be left on the corresponding talk page.
Currently, there is no prometheus instance for the beta cluster, so this needs to be product verified either locally before deployment or on production after the deployment (or both)
- updated the Grafana board and moved the panel to third position from top (as it's really not that interesing)
- this is currently a little hard to verify with all skipped entity metrics being 0, but I think all types and formats should be covered now and show once per day
- will possibly need further adjustments once we actually have more skipped entitities than 0
Wed, Feb 4
Fri, Jan 23
Jan 14 2026
Jan 8 2026
Jan 7 2026
Jan 6 2026
Thanks for the investigation and very comprehensible summary
#
# ##
# # #
##### #
# #
# #
#####Dec 19 2025
Dec 18 2025
waiting for approval by the SRE team
still waiting for T406497
Dec 17 2025
Dec 16 2025
The mismatching edit summary decribed in T361444 shows when deleting a statement using wbremoveclaims and including an old revision ID as baserevid parameter in the request. The REST API specification for edit/delete requests does not include a baserevid parameter to indicate the revision of an entity to be edited or deleted. Instead, it relies on the HTTP standard of "Conditional Requests" as defined in RFC9110 to prevent edit conflicts.
Dec 12 2025
Dec 9 2025
Dec 5 2025
Dec 3 2025
Nov 27 2025
Nov 26 2025
Nov 24 2025
Nov 17 2025
updating to docker-registry.wikimedia.org/repos/search-platform/cirrussearch-opensearch-image:v1.3.20-12 does fix the issue here locally
confirmed: I can reproduce this locally by running CirrusSearch\Maintenance\UpdateSearchIndexConfig --startOver and moving back to a commit prior to CirrusSearch: Make keyword fields actual opensearch keyword fields does fix it