[09:42:04] any updates on https://issue-tracker.miraheze.org/T13977 ? 🥹 [12:10:52] [1/9] Speaking of extensions, I was playing around with Bucket and I saw [12:10:52] [2/9] ``` [12:10:52] [3/9] POST http://localhost:8080/index.php?title=Bucket:Student&action=submit net::ERR_CONTENT_LENGTH_MISMATCH 500 (Internal Server Error) [12:10:53] [4/9] ``` [12:10:53] [5/9] when creating a new bucket. According to the logs, this is the culprit: [12:10:53] [6/9] ``` [12:10:54] [7/9] [rdbms] Wikimedia\Rdbms\DBConnRef::query [0.058ms] mariadb: GRANT ALL ON bucketstudent TO Bucket@'%'; [rdbms] Error 1142 from Wikimedia\Rdbms\DBConnRef::query, GRANT command denied to user 'test'@'10.89.0.7' for table my_wiki.bucketstudent GRANT ALL ON bucket__student TO Bucket@'%'; mariadb [12:10:54] [8/9] ``` [12:10:54] [9/9] Looks like Bucket will try to grant itself all permissions on new bucket tables with the main DB connection, so I just granted the main DB connection the ability to grant additional permissions to other DB users. [12:15:05] [1/3] Currently stuck on inserting data into a bucket because no data shows up no matter what I do. It seems that `->from( $dbw->addIdentifierQuotes( $dbTableName ) )` is the culprit because it adds additional stuff to the table name which `SelectQueryBuilder` doesn't like (maybe it's a MW version problem?), but I still don't have any luck after removing `addIdentifierQuotes`. [12:15:05] [2/3] I was hoping that Bucket won't explode unless I try to index multi-value columns, but this is rougher than I expected. Maybe it'll be a better idea to revisit this once WeirdGloop deploys Bucket in production. [12:15:05] [3/3] https://cdn.discordapp.com/attachments/1006789349498699827/1410960950546403439/bucket_log.txt?ex=68b2eb48&is=68b199c8&hm=c691b382b8675b0ce256681a54c1bf4b8f9e1c6657a5ec51f1e537d2852057c7& [12:45:47] I thought they already deployed it to production? It's listed in their Special:Version [12:46:12] Which database engine are you using [12:46:51] Oh I saw this error in DPL before, are you on 1.44 [12:51:33] Why are they adding extra quotes to the table name’ [12:56:21] Oh nice. I wasn't aware of that. [12:56:45] Yep. I suspect that my local deployment being on 1.44 instead of 1.43 made a difference. [12:57:18] Yeah DPL3 used to do that and it threw errors when I tried to migrate to 1.44 back in like July or so [12:58:51] So I guess that's a thing they decided to error out on in 1.44 [13:28:47] Still no luck after removing those quotes, though, and I no longer see errors in logs. [13:36:41] I really need to figure out how to attach a debugger to a running MW server. Maybe I'll ask SomeRandomDeveloper how he did that with PhPStorm... [13:43:08] Are you using docker? [13:46:12] btw I'm coincidentally setting up a bucket testing environment locally right now because I was getting sick of cargo and SMW and decided to take a look at bucket, I can see if I can reproduce the bug you mentioned above [13:49:05] [1/2] I somehow managed to break my docker in the process... [13:49:05] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1410984606639067196/image.png?ex=68b30151&is=68b1afd1&hm=846447b5a99d44f81a7e1e1963dbe2ecbe53caf2e7b35a6da9b42e4819cc0112& [14:04:07] Yeah. I'm not sure how to make PhPStorm work with an external docker (podman) container, and the documentation on `Xdebug` seems to assume that everything resides in the same environment. [14:05:54] worked for me [14:06:21] Although you might need to adjust settings in PHPStorm after setting it up in case you're doing shenanigans with symlinks like me [20:56:17] Security updates are done, took a few retries though because of weird external connectivity issues/DNS. One of these days I'll look into them, but it won't be today because I'm sick. [20:56:36] Thanks for doing what you can, take care of yourself. [21:58:12] Thanks. I think I'm having issues with more basic things such as letting PHPStorm access the content of the container. Maybe I'll just use docker instead of podman and follow the MW-docker guide from the start. [22:01:49] [1/2] What I did is mount a directory with all extensions + skins as a volume to the docker container and then symlink the individual folders to subfolders of /var/www/html/w/extensions and /var/www/html/w/skins (the symlinks are updated using my CLI tool), this way the paths for extension and skin files are the same on the host and in the container. I don [22:01:49] [2/2] 't know what solution the docker guide suggests for managing those directories, but probably a simpler one [22:02:17] You could also replace /skins and /extensions with a symlink to the directory with all skins + extensions, though that causes problems in case you want to use core as a git repo [22:20:14] i prefer the cursed way of debugging: new MWException() [22:21:44] I had issues with xdebug recently and just used a ton of statements like `echo "a";` [22:27:18] i've never used xdebug in my life, only var_dump() [22:29:08] Ah this is one thing I tried. Now that I know it works for you, I should stick to it. [22:30:45] I forgot about this in my previous message but FYI this might cause problems phan and some maintenance scripts (although both were solvable for me), because parent directories linked via `../` resolve to the actual parent directories of the symlinked directories instead of `/var/www/html/w/...` [22:31:10] Running maintenance scripts with maintenance/run should avoid this problem [22:31:33] And for phan, you need to specify the folder MW is inside, e.g. `MW_INSTALL_PATH=/var/www/html/w vendor/bin/phan -d . --long-progress-bar` [22:32:34] I should really make the repo of my dev environment on github public [23:09:19] True debugging [23:10:13] [1/2] hey silly mirahezers, does anyone know why the mw email thingy wont work? [23:10:13] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1411125819178483822/image.png?ex=68b384d4&is=68b23354&hm=d921c3fa7634459bc3375b40451d8b9e11a333473775295d1975cec821f3e577& [23:10:48] I'm selfhosting and the app password I generated for the email doesnt work [23:12:47] was returning errors at first but whenever I try to use it now (through the emailuser feature) my browser tab keeps loading forever [23:21:12] Is this for your own MediaWiki instance? [23:21:46] yeah [23:22:07] the mw documentation thing about it was rly useless [23:22:33] https://discord.gg/ZrV2Ex9 we do not provide support in this server for self-hosted MediaWiki instances