[13:21:45] I was gonna run Pywikibot on `lhmnwiki` but it seems that I always got 403 [13:30:33] Have you set a proper UA? [13:30:49] If so, drop an email to tech@ with your IP [13:37:54] With contacts info and "bot" in UA, then yes [13:38:21] Drop an email with your ip then [13:38:25] And we'll take a look [14:01:51] Sent, sorry for the slow reply [14:28:46] You have mail! [14:46:02] 📨 [18:54:21] [1/2] uhh [18:54:22] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1457447077696245993/image.png?ex=695c08dd&is=695ab75d&hm=5da5c3bf601b8252dda9937f8918b3fd725732294256f8651d6a54faa3edfcb2& [18:55:39] [1/2] ?? [18:55:39] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1457447402377318480/image.png?ex=695c092a&is=695ab7aa&hm=44c586aa3cd8564a041c27db43de32bb66d967827956ed9fd396b89bc3c02bda& [18:56:44] @reception123 is this related to T14716? [18:57:58] yes [18:58:12] they started working on it [18:58:39] all 1.44 wikis on beta are broken [18:58:44] guess I'm gonna reset the local config changes [18:59:09] hopefully shouldn't be any besides it being a global ext [19:00:00] oh right I was supposed to make a pr for RW but got woefully distratced [19:00:25] Why are we deploying new global stuff to beta and leaving it broken during a freeze [19:00:30] With no even comms [19:00:43] no idea [19:00:54] Do I even want the answer [19:00:58] beta was broken like 4 times in the last couple weeks before the freeze started [19:01:10] Please file a task for a breach of the freeze [19:01:29] It's not even good practice any day of the week [19:01:31] invalid extension.json and extension files owned by root are the two cases I remember [19:02:02] It's just normal good behaviour when working with people to not leave every wiki broken with no comms, even on a testing environment [19:02:09] i called out the latter directly to rec, is it still not fixed? [19:02:27] I fixed both things immediately but it still was annoying to do [19:02:34] every 1.44 wiki (targeted harassment of random) [19:02:39] Whoever is messing with extension files a root needs a good lesson on security too [19:02:46] That's worth a task too [19:03:08] We have a bloody user for modifying them that owns them [19:03:15] Stop using root for no bleeding reason [19:03:42] yeah I think it was the .git folder as well back then, which is not good practice [19:04:00] I have a million questions [19:04:15] And none of them im that sure I want to know the answer too [19:05:26] @abaddriverlol please file a task for today's issue [19:05:33] doing rn [19:06:01] @abaddriverlol please also file one to clarify policy on DONT FUCKING USE ROOT WHEN ITS NOT NEEDED TO PULL GIT [19:06:30] Do it often enough on the wrong thing and it's a security risk [19:09:54] _thinks about the fact that an attacker only has to be lucky once, we have to be lucky every time_ [19:14:52] Beta is not part of the freeze [19:15:00] That's never been my understanding [19:15:26] Being unable to test during holiday periods isn't really an efficient policy [19:16:01] @reception123 not leaving things broken without any comms is just good manners [19:16:06] That's not even a freeze rule [19:16:11] no log entry in SAL either btw for the deployment [19:16:12] That's just normal behaviour [19:16:56] What was left broken? If it was the extension itself that was just because I was working on something, it shouldn't have been affecting anything else [19:17:00] Beta still needs to be treat with caution during the freeze in case there's an actual incident and we need it for actual testing [19:17:08] 1.44 wikis [19:17:13] All 1.44 wikis on beta were broken [19:17:28] Which I use to test stuff every time before deploying to prod [19:17:46] We should not be leaving all wikis matching our currently deployed version broken in a test environment during a freeze [19:18:31] or at any time [19:18:42] I wasn't aware anything was broken, in that case I apologize [19:19:02] But things being broken on beta shouldn't really be considered unusual, that is its purpose [19:19:15] If you're testing an extension, is there any need for it to be enabled globally anyway immediately [19:19:26] Things being broken isn't unusual, poor comms is [19:19:50] No SAL, no task update, no email, no message here, no Mattermost [19:21:48] The only reason was that I had no idea it affected anything else but next time I'll make sure to make it more clear if I'm testing something [19:22:30] I had no idea testing a global extension could impact something else is a bit pushing it [19:22:50] [1/2] Also please don't use root to create extension files [19:22:50] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1457454241911144449/image.png?ex=695c0f89&is=695abe09&hm=8a902c679b386775641c8b1c3da1a55230df7df05f29779f807ab4e8d4ec013f& [19:25:36] Or to clone them, since .git is owned by root as well [20:12:38] Hi, is this the right place to go with CSS questions? [20:13:14] #general or #support would be better :] [20:13:26] Got it, thanks! [20:13:33] Yw! [21:12:01] [1/5] @everyone [21:12:01] [2/5] https://cdn.discordapp.com/attachments/1006789349498699827/1457481719983898686/1.jpg?ex=695c2920&is=695ad7a0&hm=59b2a5fca5474a45e998508903c4e5b51043dc12d3ea66bfe004f67a2d802a25& [21:12:02] [3/5] https://cdn.discordapp.com/attachments/1006789349498699827/1457481720319311973/2.jpg?ex=695c2920&is=695ad7a0&hm=b30f49d9b3b9d772f6882392799b054780fbb2747c68432ee8830b16d0218dc8& [21:12:02] [4/5] https://cdn.discordapp.com/attachments/1006789349498699827/1457481720575168729/3.jpg?ex=695c2920&is=695ad7a0&hm=a4c587750b5030891d5a31907735e5ae1c1120659d235abb04c5de67606385e3& [21:12:02] [5/5] https://cdn.discordapp.com/attachments/1006789349498699827/1457481720847663165/4.jpg?ex=695c2920&is=695ad7a0&hm=c24302c482c3c313334920567b4bcaf63919bb81d25ac05248af452537a8a9c2& [22:23:44] can't believe my local test setup is more secure- [22:24:15] shoutout to that one time i saw maintenance scripts being run as root [22:25:03] [1/2] uhhhh [22:25:03] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1457500099939668129/image.png?ex=695c3a3e&is=695ae8be&hm=c7c6fa0434e19f3b8ed6a966d42e7338008e8c3928a4c627ab9a3ec5aff60129& [22:25:11] tbf it's a container [22:25:56] also no idea why I used lS instead of l [22:26:00] my files are owned by mwadmin lol [22:26:06] http user is... http [22:26:35] on my host my files are just owned by my linux user [22:26:43] fair lol [22:26:50] since I assume there would be 1000 problems with phpstorm or other tools otherwise [22:26:54] or mwutil [22:27:06] i do sometimes do `sudo chown -R claire:claire extensions/meow` so that i can rsync easily [22:27:31] [1/2] almost finished my rust rewrite [22:27:31] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1457500718180077648/image.png?ex=695c3ad2&is=695ae952&hm=4e83e38315e3e509d0dea3a97bff38f0c4c35cb66f889049a436240b2800d524& [22:27:42] ah [22:27:52] so different folders are owned by different users? [22:27:55] that sounds complicated [22:28:04] complicated to work with at least [22:45:05] mine is owned by myuser:staff idek who staff is [22:45:11] i think its some macOS system thing? [22:46:31] default group apparently [22:47:06] all I know is it causes me headaches with NGINX [22:47:14] i just chown every user I know until it works heh [23:05:09] eh, it's easy [23:05:25] [1/2] read-only? `sudo -u http` [23:05:25] [2/2] write? `sudo -u mwadmin` [23:05:48] ah makes sense