[07:36:26] dcausse: Good morning! About https://gerrit.wikimedia.org/r/c/search/cirrus-streaming-updater/+/826664, do you know if there is a reason to use JUnit 4 over JUnit 5? [07:36:38] o/ [07:36:44] If not, I'll push a patch to upgrade [07:37:02] looking [07:49:14] Flink seems to be using junit 5.8.1, so that should not be an issue [08:00:48] there might be adaptations to be made to scalatest perhaps [08:01:01] perhaps using https://github.com/helmethair-co/scalatest-junit-runner [08:02:39] scala test depends on junit? I would have expected it to have its own runner [08:05:21] it has its own simple runner indeed [08:07:31] Sounds like things we'll need to figure out as we go. Do we have a preference arleady for Java over Scala? [08:09:50] There are also a few scala plugin configuration in that project. Would it make sense to move them all to the parent pom? And align between all projects? [08:12:40] yes for some (adding few thoughts in review comments) [08:27:36] for java vs scala, event-platform is writing scala so I think we should try it again [08:30:36] Damn, I'll have to learn scala eventually! [08:43:28] scala is fun [08:43:35] sometimes :P [10:15:08] lunch [10:34:55] lunch 2 [13:05:17] o/ [14:36:03] Trey314159: I've just closed T311654. Is there a followup that we should do to check the same issue on more wikis? [14:36:04] T311654: Apostrophes do not work well in search on nia.wikipedia - https://phabricator.wikimedia.org/T311654 [14:37:50] gehel: I opened T315118 to look into that and we triaged it as medium [14:37:50] T315118: Handle variation in apostrophe-like characters better - https://phabricator.wikimedia.org/T315118 [14:38:03] I'll add a link to the Nias ticket [14:38:19] Thanks! [15:01:45] triage meeting: https://meet.google.com/eki-rafx-cxi (cc ejoseph) [17:10:06] PR for upgrading beta-cluster ES instances in puppet: https://gerrit.wikimedia.org/r/c/operations/puppet/+/827535 [17:17:14] Feel free to review ^^ if you have the time! Lunch/errands, back in ~1 h [17:41:07] ebernhardson: if you have a couple minutes, it's finally green https://gerrit.wikimedia.org/r/c/wikidata/query/rdf/+/827524 [17:46:54] dcausse: looks reasonable, +2'd [18:14:52] ebernhardson: thanks! will trigger a release [18:24:12] back [18:31:43] ^^ reverted the SSL cert change from the above PR, have another look if you have time [18:32:43] inflatador: lgtm, although i have no clue if something might be missing :) [18:36:10] we'll know soon enough ;P [18:36:15] and thanks for the review! [18:57:37] dr apt, back in ~1 hr [18:58:26] 4 [19:44:55] ryankemper: I missed the deploy window but (for when you have time) the patch to deploy a new build of wdqs (mainly for wcqs) is up here: https://gerrit.wikimedia.org/r/c/wikidata/query/deploy/+/827550 [19:52:45] back [20:27:42] dcausse: ack, will get that out today [20:37:05] thanks! [21:17:02] ebernhardson Looking at https://phabricator.wikimedia.org/T308676 , are we planning on starting the codfw ES7.10 upgrades tomorrow or next Tues? (Was thinking it would be tomorrow) [21:18:06] inflatador: codfw is this week, eqiad in two weeks. The middle week (next week) is no-action on our part, except monitoring how the rollout goes as traffic shifts from eqiad to codfw [21:18:22] hopefully no-action at least :) Maybe some action if things don't work fully as expected [21:19:49] the initial plan was cloudelastic today, codfw rest of the week, but we pushed cloudelastic up earlier into last week and i suppose we could have pushed codfw up to today as well, but starting tomorrow is just as good [21:20:21] ebernhardson cool, just wanted to make sure I understood [21:28:37] school run time, back in a bit [21:59:55] back [22:00:48] meh, deployed an airflow update unrelated to other things, and now all the hourly jobs failed :S wonder why... [22:05:26] all the deployed artifacts are 74 bytes :S [22:19:55] yea, scap is certainly not calling git fat (per the logs)...but not sure why [22:40:07] turns out, if you `scap deploy` and it fails due to git-fat not being able to pull everything (didn't wait long enough for archiva to create the rsync targets), then a simple `scap deploy ...` isn't enough, have to `scap deploy --force ...`. Maybe. running now after reviewing code and logs :) [22:46:26] i suppose we have no way to really mark as such, but after fixing the scap deploy i've cleared all the tasks that emailed about failures and things look to be running as expected now