User Details
- User Since
- Nov 19 2018, 8:02 PM (295 w, 4 d)
- Availability
- Available
- IRC Nick
- jeena
- LDAP User
- Jeena Huneidi
- MediaWiki User
- JHuneidi (WMF) [ Global Accounts ]
Tue, Jul 16
if dep is not None: vote_on_change(change, dep) if dep.project in config_repos: boundary_hit = True evaluate_change_dependencies(dep, boundary_hit)
Thu, Jul 11
Wed, Jul 10
I tried to interpret the criteria into some psuedo-code. I attempted to capture all the cases in the criteria and explain the scenarios. I'm wondering if for the boundary scenario, such as for an unlikely dependency trail like [0]Core->[1]config->[2]core->[3]core, should we just consider the selected depends-on's branch as the the target branch (ex. change 3 is relevant if targeting same branch as change 2) for consistency's sake? As you mentioned in another comment this scenario is unlikely and it's hard to interpret the actual intention.
At that point we don't know which of the wmf version branches are required to contain the commit in K.
Tue, Jul 9
Adding a persistent volume for /var/www/html/wikis will allow the wikis to persist on reboot. No other volume is needed.
Mon, Jul 8
Fri, Jun 28
D belongs to the MW configuration repo and K belongs to a MW code repo --> If K doesn't target master it will vote in favor if, and only if, it's been merged or passed as root change in the command line. If it targets master it will vote in favor if, and only if, it's been merged and its commit is in all deployable branches (as determined by the "change/_/in" endpoint from Gerrit)
Wed, Jun 26
Thanks @Ladsgroup. I've been monitoring since then and I think you are right.
I have rolled back the train because of a higher than normal DBQueryError rate. I've created a bug task with the top DB error from logstash and added it as unbreak now.
Jun 18 2024
Jun 10 2024
Some things that need to happen on the patchdemo side:
After pushing "create demo":
- Print logs for catalyst media wiki creation
- On completion, make sure open wiki button goes to the right place
- Fix “you can log in as…text” by either adding those to our mediawiki chart or removing the text
Jun 4 2024
May 20 2024
May 16 2024
I'm wondering if we want to change the terminology of 'Production branch' to 'Active branch' to match the terminology that is all over scap (active wikiversions, etc.)?
May 14 2024
May 9 2024
May 8 2024
May 7 2024
I rolled back to testwikis due to errors caused by T364428.
May 3 2024
Apr 25 2024
Apr 24 2024
Apr 23 2024
I'm not clear on what the proposed code changes are. I think what is mentioned in the "relevant dependencies" and "backport vote" sections are already implemented in the code (or in the case of change_in, have a MR to do so), except for maybe reducing the number of confirmation prompts. Can you clarify which parts are missing or whether it is that you would like to change the structure of the dependency checking process?
Apr 16 2024
Mysql db is not in the patchdemo container so when running, a db connection is needed. Environment variables to be in the image are DB_HOST, DB_USER, DB_PASS, DB_DATABASE.
Apr 3 2024
Mar 28 2024
Sorry, false alarm! Looks okay now.
Is this related to the bug that was fixed earlier today?
Mar 20 2024
I made some changes to the script to get it working on our vm and put them here: https://gitlab.wikimedia.org/repos/qte/catalyst/patchdemo/-/tree/catalyst?ref_type=heads
Feb 27 2024
Feb 21 2024
stack trace of timout errors
Jan 18 2024
Yes, I think that is the correct assessment (the revert to bare metal did not fix the error. But I'm also not sure what configuration changes were needed to make this change on the mediawiki side that needed a scap deploy), so we still need to figure out how to solve this issue.
Jan 17 2024
isn't a deployment of changeprop in kubernetes needed here? I don't think scap does this.
Jan 11 2024
Jan 9 2024
I wanted to see this rogue button so I logged out but (un)fortunately it was in English for me
Nov 16 2023
Looks like we've had an increase in errors since deploying the train today
Nov 13 2023
Oct 4 2023
I updated the spec based on details in the miro board. I made some assumptions about the schema that might need changing, as well as renamed 'service' to 'resource' since I thought it was a bit confusing to refer to things like extensions and skins as services. I also removed DELETE /environments since it wasn't on the miro board (added DELETE /environments/:id).
Sep 12 2023
Sep 7 2023
Sep 5 2023
I think this needs to be backported since the branch commit for wmf.25 already happened before merge
Jun 17 2023
Hi @xSavitar, this feature exists already. I'll be adding an integration test for it soon.