User Details
- User Since
- Jun 7 2021, 8:33 PM (178 w, 15 h)
- Availability
- Available
- IRC Nick
- codebug
- LDAP User
- WQuarshie
- MediaWiki User
- WQuarshie (WMF) [ Global Accounts ]
Wed, Oct 30
Wed, Oct 9
Sep 12 2024
Jun 30 2024
Jun 25 2024
Jun 13 2024
Jun 5 2024
May 28 2024
May 27 2024
May 23 2024
May 20 2024
Mar 28 2024
Jan 10 2024
Jan 9 2024
Dec 19 2023
@FJoseph-WMF the last checkbox had said my personal github was fine to start with, that's why. should I move it?
I shared the improvement on my personal github here: https://github.com/codebuggg/wiki_rest
Using the suggestions from Bill in the task, I considered an extension of the script from the structure of extension development of rest endpoints;
- Using the reading list file structure, the goal was to implement the script such that it reads from a file(usually, extension.json or any json file indicated, the rest routes that are listed)
The assumption was that for any services, the routes will be defined in a particular file, using the same format, hence, we can access that file, get the route and also the method to make the call.
- I I thought to keep it a bash script also because I was thinking of it's possible use case outside php services since we have other services that may not be php.
Dec 14 2023
Dec 8 2023
Oct 9 2023
Oct 2 2023
Declining this task because:
- T196059 was created because of T189286, however, T189286 has been resolved without it. We therefore can no longer find the relevance of this task.
- The current implementation in XTools pulls InitialiseSettings.php.txt and parses it using regexes. An alternative might be to get this data in json format from https://noc.wikimedia.org/wiki.php.
- The json appears to be generated directly within that php page, so (unless we're missing something) there's no way to directly pull just the json for the config values of interest - they'd have to be extracted from the html. But that might be preferred to the current regex parsing
- It might also be possible to make those individual variable values available as raw json, by adding that functionality to the noc.wikimedia.org site (its code lives within the mediawiki-config repository). Unsure who is responsible for that particular bit of code - RelEng maybe? Doing this would justify a separate task and a conversation on-task with the maintaining team.
- It might also be possible to directly add logging of autoconfirmation assignment to mediawiki itself, so that autoconfirmation appears in Special:Log. However, that would be a significant number of database writes, and would therefore need an impact analysis to determine if it were actually feasible, and if usage of the feature would be beneficial enough to justify the additional load.
Aug 16 2023
I tried to replicate this bug but it seems it has been fixed.
I also tried to trace the patch that possibly fixed this, however, I was unsuccessful at that attempt. There seems to be a function that is setting them to default arrays.
Aug 9 2023
May 31 2023
May 11 2023
May 8 2023
May 3 2023
Apr 26 2023
@EChukwukere-WMF this code change was done in AQS Assist, I just wanna confirm that you updated with that change into device analytics before testing. If so, can you please give the steps to replicate this error
Apr 18 2023
Apr 12 2023
Apr 11 2023
@EChukwukere-WMF did you get to testing this after you cloned the new device-analytics repo?
can you kindly update the status on this cos I think this issue has been resolved
Apr 6 2023
The framework chosen was testify. We now have an example logic unit test for device analytics.
Mar 19 2023
@BPirkle This MR is ready for gerrit but our page analytics repo on gerrit does not have a .gitreview file so I cannot push
Mar 10 2023
Mar 8 2023
Feb 27 2023
I looked over a couple of golang mocking frameworks and did a little comparison below;
Some Go testing frameworks
I am moving this to paused as I will be assisting Emeka later today with gerrit so he can have the latest on this repo since we have fully moved to gerrit now.
His initial test was done on the gitlab repo which we don't use anymore
Feb 22 2023
Feb 15 2023
I added the test to this but realised a few of the existing tests already failed(I'd like to know if I'm the only one experiencing this, maybe it's just something with my local environment)
In regards to this ticket, this is resolved but we may want to look into the other tests and maybe create separate tickets for them.
Feb 13 2023
Feb 8 2023
Feb 7 2023
Feb 2 2023
Jan 31 2023
@EChukwukere-WMF this ticket was to add not found handler to pageviews and not unique devices. this test has to be done on pageviews and not unique devices
for reference, this ticket was created a sub ticket to: https://phabricator.wikimedia.org/T324160
Jan 30 2023
I am moving this ticket to paused to reflect the current status on the ongoing discussions about routers.
Extraction had began and is pending a gerrit review, however, with the ongoing router discussion, it is better to put it on hold
Jan 25 2023
Jan 24 2023
Jan 23 2023
Jan 17 2023
@JArguello-WMF I do. the first task of this is waiting to be merged, then the second can be completed
Jan 11 2023
Unique Devices / Page Views Comparison