User Details
- User Since
- Mar 14 2023, 12:16 PM (101 w, 19 h)
- Availability
- Available
- LDAP User
- Unknown
- MediaWiki User
- ROdonnell-WMF [ Global Accounts ]
Mon, Feb 17
Tue, Feb 11
Mon, Feb 10
Thu, Feb 6
Mon, Feb 3
Maybe add https://en.wikipedia.org/wiki/Template:False_version to our signals? RE: Liam's post
Thu, Jan 30
Tue, Jan 28
Metrics and findings in Realtime Concurrency Tests.
Wed, Jan 22
I updated the tick boxes.
Mon, Jan 20
@JArguello-WMF has this ticket been triaged and t-shirt-sized for this Sprint?
Jan 16 2025
Jan 15 2025
Jan 14 2025
Hi @Chiahwu if you have time, please download the latest Python code from GitHub and review/test the ReadMe instructions. I've simplified the dependency installation, by making it the same for all three demos. You can see the ReadMe at Demo - Getting Started README and afterwards pick a demo and follow those steps:
Jan 13 2025
Pull request has the 6 "Done" items in the last comment. https://github.com/wikimedia-enterprise/wme-sdk-python/pull/5
Jan 10 2025
Actionable items:
Jan 9 2025
Jan 8 2025
Jan 7 2025
Dec 10 2024
Dec 9 2024
Ruairi ToDo:
Marking as done:
Nov 28 2024
Nov 27 2024
My feedback from looking at on-call incidents is that there is a pattern to our problematic (slow) queries. From CloudWatch, I pulled our these slow KSQLDB queries in CSVs.
@FNavas-foundation I've read the Model Card. We need the performance details (Requests Per Second (RPS)) and the model F1 score to decide whether to integrate it into our API. We need the RPS and business expectations on SLA if something breaks.
Nov 26 2024
Cool, that makes the ticket easier. It's a simple change to deserialize the file in`TopicArticlesPath` and overwrite the TopicArticles field.
@RThomas-WMF Can you look at this and see if you are happy with this proposed Terraform change?
After consultation with the team, Option 1 is the consensus choice for implementing this ticket.
Picking up and bringing into Sprint
Nov 25 2024
Nov 22 2024
The API docs look better without the bulky text. The YAML uses a reference to re-use the same wording throughout the HTML. The best option is to put the Status Code descriptions in a new Web page and leave the Data Dictionary for JSON field descriptions. You know best how to optimise the Web page content.
@JArguello-WMF, Can this ticket be marked as Done?
Nov 21 2024
Nov 18 2024
Yes, and I mentioned it to Chuck in the eng channel
Nov 13 2024
Nov 12 2024
This ticket is unallocated. There is not enough detail for me to assess which fields the clients want in this "subset of Commons metadata fields".
New Password Required:
- orig: Responds NEW_PASSWORD_REQUIRED challenge by receiving username and session token and setting new password.
- proposed: NEED ENG INSIGHT HERE -- Is this still needed???
- why would it respond with this? anything helpful here? Feel free to ping chuck in slack with draft when ready.
- How do we explain that better in the description?
Description from @HShaikh "The new password requirement was I think a last minute addition so really needs a deeper look on how that works. If I remember correctly, it was due to mark from internet archive losing password and having us redo his password for him"
- Forgot password, action needed? - this should be part of the same workflow and contextual
Nov 11 2024
We were sharing usage metrics for the users that registered around the time of @Chiahwu's Hackathon.
Oct 31 2024
Error in HF:
Added a Google Doc in the Research folder
- Potential API upgrade for Main API