[01:15:48] [telegram] https://phabricator.wikimedia.org/T308762 [01:15:49] [telegram] [01:15:50] [telegram] Pywikibot Mysteries: brief introduction during WM Hackathon 2022 [01:15:52] [telegram] [01:15:53] [telegram] is this session over? [01:32:18] [telegram] My hackathon accomplishment: during a demo I gave I set up InternetArchiveBot (dead link fixer) on Amharic Wikipedia. Doing something live there’s always a risk of something going wrong, but apparently, it worked and the bot is now in operation there. [02:03:09] [telegram] That's awesome, James! [02:15:00] [telegram] 👏 (re @harej: My hackathon accomplishment: during a demo I gave I set up InternetArchiveBot (dead link fixer) on Amharic Wikipedia. Doing some...) [02:16:45] [telegram] Great (re @harej: My hackathon accomplishment: during a demo I gave I set up InternetArchiveBot (dead link fixer) on Amharic Wikipedia. Doing some...) [02:35:39] [telegram] Till date LARRY JAY has been a great inspiration to me and my family. For a start I deposited $100 and after a work I got $1,200 return.he's accurate and reliability can't be compromised [02:35:40] [telegram] https://t.me/+B9enobjPceEwZmJk [02:50:00] they're not even trying anymore are they [03:39:30] [telegram] Hi all! Just a reminder to add yourself to the showcase list if you want to present. We'll start in ~11 hours. Really looking forward to it! https://etherpad.wikimedia.org/p/hackathon2022showcase [05:49:06] [telegram] Does anyone know who was working on Wikidebate? Almat is interested in getting involved. https://en.wikiversity.org/wiki/Wikidebate [05:56:19] [telegram] Hmm, https://en.wikiversity.org/w/index.php?title=Wikidebate&offset=&limit=500&action=history implies Sophivorus (Felipe Schenone). [09:53:20] [telegram] is there a way to “deprecate” a repository in Diffusion (Phabricator’s Git hosting)? show some kind of message when users visit or pull the repository? [09:53:39] [telegram] (e.g. I think GitHub shows you a warning when you pull from a repository that was moved, telling you to update the remote URL) [09:54:07] is there a way to redirect a Cloud VPS proxy to a static URL (specifically a Phab task explaining why/how it was shut down)? [09:55:14] [telegram] I believe https://wikitech.wikimedia.org/wiki/Nova_Resource:Redirects can do that? (haven’t used it myself though) [10:08:51] [telegram] (re deprecating a Diffusion repo, if there’s nothing else I guess I could just push an exclusive commit to that repo saying “hey look over here instead”) [10:33:42] [telegram] Hi everyone, I am trying to deploy a dashboard on toolforge. I running into the following error: [10:33:43] [telegram] [10:33:44] [telegram] unable to find "application" callable in file /data/project/incubatordashboard/www/python/src/app.py [10:33:46] [telegram] [10:33:47] [telegram] we are using Dash (dash.plotly.org), an abstraction of Flask and React.js [10:34:57] [telegram] try adding a line `app = application` in the `app.py` file (or directly rename the `application` variable to `app`) [10:35:54] [telegram] (also, I think that link should be dash.plotly.com, the .org link gave me a notice that the domain is for sale) [10:43:39] [telegram] thank you. application has to be defined as? (re @lucaswerkmeister: try adding a line app = application in the app.py file (or directly rename the application variable to app)) [10:44:11] [telegram] oh yes thank you (re @lucaswerkmeister: (also, I think that link should be dash.plotly.com, the .org link gave me a notice that the domain is for sale)) [10:45:18] [telegram] the app is defined app directly. (re @kcvelaga: thank you. application has to be defined as?) [10:45:58] [telegram] it looks like you did both changes together now, that’s not going to work [10:46:19] [telegram] if you’re renaming the variable to `app` everywhere then you can remove the `app = application` line [10:46:56] [telegram] the same error; here is the code: https://github.com/jhsoby/IncubatorDashboard [10:47:35] [telegram] did you restart the webservice after the last change? [10:48:43] [telegram] yes [10:51:04] [telegram] grmbl, apparently a `Dash` instance isn’t actually a WSGI server by itself [10:51:12] [telegram] you need to expose `.server` https://help.pythonanywhere.com/pages/DashWSGIConfig [10:51:40] [telegram] so, probably rename the variable back to `application` (or something else), and then add `app = application.server` somewhere [10:52:28] [telegram] (Toolforge expects the name `app`, so that needs to be the `.server` of the `Dash` instance, the variable name of the `Dash` instance doesn’t matter but shouldn’t also be `app`) [10:53:13] [telegram] this is helpful, thank you! We will try and see how this works. [10:55:12] [telegram] if the variable name is already app, will app = app.server work? (re @lucaswerkmeister: so, probably rename the variable back to application (or something else), and then add app = application.server somewhere) [10:55:39] [telegram] only if you put that at the very end of the file, after you’re done with everything else that interacts with `app` [10:55:44] [telegram] and it will be pretty confusing imho [10:55:49] [telegram] so I wouldn’t recommend it ^^ [10:56:24] [telegram] so, the best way would be to rename to application and then use app = application.server (re @lucaswerkmeister: so, probably rename the variable back to application (or something else), and then add app = application.server somewhere) [10:56:32] [telegram] I think so, yes [10:59:28] [telegram] it is working: https://incubatordashboard.toolforge.org/ [10:59:29] [telegram] [10:59:31] [telegram] thank you so much! [11:00:56] [telegram] \o/ [11:03:08] [telegram] Can someone review https://gerrit.wikimedia.org/r/c/mediawiki/core/+/795246 [11:10:07] taavi: replied. What we've got set is the default config as far as I can tell [11:10:47] Default value [] [11:10:52] which is exactly what's set [11:11:34] then the config loading code should be fixed, not the downstream uses of config values [11:11:59] this is what I see with latest master: https://phabricator.wikimedia.org/P28268 [11:12:13] [telegram] It's possible to "Disable Publishing" but UI wise it's not very obvious, and I doubt it has any influence on git pull/clone (re @lucaswerkmeister: is there a way to “deprecate” a repository in Diffusion (Phabricator’s Git hosting)? show some kind of message when users visit ...) [11:12:31] taavi: I posted on task what I see with eval.php on 1.37 [11:12:46] I have no idea where I'd look for config loading code [11:14:04] did you test without ManageWiki? [11:14:33] taavi: nope, I have no idea why ManageWiki would do anything as stupid as that [11:14:42] But then again it wouldn't shock me [11:18:14] well I can't reproduce with core mediawiki and managewiki alters how the config is loaded on your setup, so that's what I suspect may be causing issues [11:18:53] It is certainly anything related to your config. Running var_dump($wgUsersNotifiedOnAllChanges); on REL1_37 simply returns "array (0) {}", like it is supposed to be [11:22:46] https://github.com/miraheze/ManageWiki/blob/639546c27ca58c841e5d79774dce311fede81e00/includes/Helpers/ManageWikiTypes.php#L325 should be where it's set [11:22:53] taavi, zabe ^ [11:25:48] is that code saving stuff to the database or loading stuff from it? [11:27:09] taavi: I belive saving [11:28:20] Yeah [11:28:22] https://github.com/miraheze/ManageWiki/blob/346d67de0ab845f3a90f03523a1f1bcdf09542fc/includes/FormFactory/ManageWikiFormFactoryBuilder.php#L375 [11:28:51] well your bug is with the code that loads the config data [11:29:34] taavi: it should be just decoding json [11:29:37] https://github.com/miraheze/ManageWiki/blob/639546c27ca58c841e5d79774dce311fede81e00/includes/Hooks.php#L67 [11:31:21] the saving code turns the array into a single string, so you need to convert it back to an array somewhere before passing that to mediawiki [11:32:36] Why is our software so weird [11:32:51] There's no reason you can't dump and restore an array in json [12:17:25] [telegram] Still a few more hours of hacking until the showcase! If you want to present what you've worked on, don't forget to add your project to the showcase list! https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2022/Showcase [12:42:56] addshore: ping :P [12:52:20] [telegram] gsoc [12:56:43] [telegram] hey heyare you guys still taking in mentors for GSOC? [13:00:07] Amir1: sorry, I'v been away from my desk all weekend (an still am) :/ [13:16:39] [telegram] Nice! (re @kcvelaga: it is working: https://incubatordashboard.toolforge.org/ [13:16:40] [telegram] [13:16:41] [telegram] thank you so much!) [13:43:58] [telegram] yay [13:43:58] [telegram] Forwarded from wmtelegram_bot: !log tools.wd-image-positions deployed 15ade38230 (Diffusion → GitLab) [14:29:41] [telegram] the showcase starts in 30 minutes, don’t forget to add your projects to the etherpad! :) https://etherpad.wikimedia.org/p/hackathon2022showcase [14:53:57] While you are enjoying the showcase, consider leaving your feedback on this event too -- https://etherpad.wikimedia.org/p/Wikimedia_Hackathon_2022_Feedback [14:54:55] You can help us make the next hackathon even better by sharing the things you enjoyed and the things you would like to see done differently the next time. [14:57:24] [telegram] Just discovered we have magic links to positions in workadventure - Don't miss the showcase in 2 minutes https://play.workadventu.re/@/wmf/hackathon2022/map#undefined&moveTo=83,299 [15:00:22] bd808: done [15:01:15] [telegram] Can someone share the link to the meeting room, please? [15:01:58] [telegram] https://coremeet.workadventu.re/showcase [15:02:14] [telegram] (according to [[mw:Wikimedia Hackathon 2022/Showcase]], at least) [15:02:53] Showcase starting now in https://coremeet.workadventu.re/showcase [15:03:14] [telegram] Thank you! (re @lucaswerkmeister: https://coremeet.workadventu.re/showcase) [15:15:20] [telegram] Welcome all! You can present projects by signing up here: https://etherpad.wikimedia.org/p/hackathon2022showcase [15:15:40] [telegram] You can present whatever you worked on this weekend, or things you are working on and would like help with. [15:48:00] [telegram] Big cheers to everyone in the teams for moving any of these efforts forward 🥂🍻 [15:48:01] [telegram] Thank you so much to all the organizers for making this possible. We can get so much more done together!! [16:02:00] I missed the showcase :( was it recorded at all? [16:02:13] [telegram] Don't believe so [16:03:46] Hi people! First time trying this out! <3 [16:03:46] [telegram] No, sorry :( But the links to projects are in the etherpad! [16:07:33] [telegram] @djhartman at the risk of making you hate React even more… the new UTC timestamp at the bottom seems to be in 12-hour time, without any indication that that’s the case : https://tools-static.wmflabs.org/bridgebot/5f8ea2e5/file_19597.jpg [16:08:23] [telegram] @lucaswerkmeister https://github.com/hartman/zonestamp/pull/9 :) [16:08:38] [telegram] wait what [16:08:42] [telegram] there are two github repos?! [16:09:04] [telegram] small wonder https://github.com/hartman/zonestamp-toolforge/issues/3 didn’t get a reaction… [16:09:14] [telegram] yes (re @lucaswerkmeister: there are two github repos?!) [16:10:03] [telegram] … [16:14:14] [telegram] https://github.com/hartman/zonestamp/issues/12 [16:19:14] [telegram] There is a zonestamp repo and a deploy repo [16:19:53] [telegram] If you missed the showcase, you can still put your projects on MediaWiki or share here! https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2022/Showcase [16:22:55] [telegram] After you put your project to MediaWiki, it would be nice to sending some descrtion message to here too. So that people will be notified and check the project, even if you missed the showcase. (re @haleywmf: If you missed the showcase, you can still put your projects on MediaWiki or share here! https://www.mediawiki.org/wiki/Wikimedia...) [16:58:53] [telegram] Join us for the closing ceremony! Starting now. [16:59:07] [telegram] In the game space or here: https://www.youtube.com/watch?v=vBAfJCxRCaU [17:00:37] [telegram] Closing video is live https://www.youtube.com/watch?v=vBAfJCxRCaU [17:02:23] [telegram] Join us in the top right room of workadventure too if you'd like :) [17:03:00] [telegram] At the very end we will take a screenshot of the avatars. Come join us for a group photo! [17:11:17] [telegram] Thank you hackers! What an awesome hybrid event. See you in a few months at the Wikimania hackathon! [17:11:45] Where's the group picture? [17:12:02] Closing Ceremony room? [17:12:15] [telegram] yes, but I think we already took some screenshots [17:20:36] thank you everyone [17:24:22] [telegram] Thanks, everyone! [17:26:30] I'm so happy that I got to see so many of y'all this weekend. This community is what makes the annoying parts of my work life worthwhile. <3 [17:30:45] ^ +1 to that! :) [17:34:03] [telegram] YAAY After 48 hours of hacking, Finally later version of the tool is live!!!! [17:34:04] [telegram] https://videocuttool.wmcloud.org/ [17:34:05] [telegram] [17:34:07] [telegram] Please try out and report bugs/feature requests on phab board (https://phabricator.wikimedia.org/tag/videocuttool/). [17:37:33] [telegram] Thank you everyone for a great weekend [17:38:04] [telegram] It's been fantastic to finally see faces [18:07:29] [telegram] Thank you all for joining the event! We would really like your feedback. This was a very experimental event so your responses will actually have an effect on future events. https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2022 [19:25:03] [telegram] That looks pretty awesome ! (re @gopavasanth: YAAY After 48 hours of hacking, Finally later version of the tool is live!!!! [19:25:04] [telegram] https://videocuttool.wmcloud.org/ [19:25:05] [telegram] [19:25:07] [telegram] Please try out...) [19:55:57] * bd808 closes the workadventure world for everyone and sweeps up the after-party mess [19:56:15] xD [19:56:22] I just tried joining to see if anyone was there, haha [19:56:38] [telegram] Thanks for an amazing event! [21:22:44] addshore: it seems I also have to change WikibaseLexeme tests, I am getting in CI: TypeError: Argument 6 passed to Wikibase\Repo\Maintenance\DumpJson::setServices() must implement interface Wikibase\Repo\Store\EntityTitleStoreLookup, instance of Serializers\DispatchingSerializer given, called in [21:22:44] /workspace/src/extensions/WikibaseLexeme/tests/phpunit/maintenance/DumpJsonTest.php on line 217 [21:22:58] so I added an argument to setServices [21:24:27] so should I make another gerrit change for the other repository? I assume that one depends on wikibase, too; so how do I change both at the same time? [21:38:41] OK, I made new argument optional, I think this will fix thins [21:38:43] *things [23:52:28] OK, https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Wikibase/+/793934 is ready for review, it has both opt-in configuration option and a test