[10:52:37] BTW, I hope people don't mind putting in a few Wishlist items here to bring some attention. This one about supporting more modern Python web services would be great to have support on. If folks recall, we asked for this two years ago, and it's been sitting in Phabricator. [10:52:39] [10:52:40] https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2023/Bots_and_gadgets/Support_ASGI_on_Toolforge [13:14:39] Is there a way to programatically figure out when a page was added to a category and/or when a template was added to the page? (in my usecase it would be one and the same) [13:16:23] You must mean a way other than to use the WikiBlame method of inspecting every edit in the history? (re @jhsoby: Is there a way to programatically figure out when a page was added to a category and/or when a template was added to the page? (...) [13:16:37] yeah [13:16:59] hmm, actually, when you mention it, inspecting the history could work [13:18:48] i'm thinking of writing a bot to remove a "current event"-type template after X days. So if I check the newest revision that is older than X+1 days, and the template is present in that one, that might suffice as a criteria to remove it [13:26:04] oh, or I can just use ?action=query&prop=categories&clprop=timestamp (https://en.wikipedia.org/w/api.php?action=help&modules=query%2Bcategories) 😁😁 [13:27:24] or get a bot to date undated templates regularly and then just look at the date listed (re @jhsoby: i'm thinking of writing a bot to remove a "current event"-type template after X days. So if I check the newest revision that is ...) [13:27:38] a la other warning templates [13:28:12] we don't date any templates in the Norwegian Wikipedia [13:28:55] so just revert your bot if people disagree? [13:29:20] I was thinking manually update the date to prevent removal if it's still relevant [13:31:45] yeah, that would work [13:33:03] maybe not with history inspection unless bot remembered it's already been there. but with API I guess it should be ok (re @jhsoby: yeah, that would work) [13:37:11] There are so many "kitchen sink" functions in the action API - I didn't know it could do that (re @jhsoby: oh, or I can just use ?action=query&prop=categories&clprop=timestamp 😁😁) [13:38:35] https://www-archive.mozilla.org/docs/web-developer/samples/kitchensink.xml [17:03:30] @fuzheado: what is it you want as the solution for https://phabricator.wikimedia.org/T296729? I don't know what "formalize running ASGI in a more supported mode using gunicorn/uvicorn as the default config" means to you in practical terms. [17:06:01] It's been a while since I looked into the guts of that, but I suppose it's as simple as saying "We support that mode of operation" with kubernetes, instead of needing to hack the generic webservice :) And of course having documentation for it would be good. (re @wmtelegram_bot: @fuzheado: what is it you want as the solution for https://phabricator.wikimedia.org/T296729? I [17:06:01] don't know what "formali...) [17:06:26] As a reminder, legoktm did this hack to get it to run: https://phabricator.wikimedia.org/T296729#7539783 [17:12:06] @fuzheado: It is possible to use ASGI; as you note Kunal showed how hours after you filed the bug report. Since that point in time nobody has said anything at all about it, so we have continued to work on other things. As far as I know there are still no ASGI containers that work like UWSGI does, so the most we could really do is label a "python39-generic" container. [17:24:07] I think a python3X-generic container is the way to go, but it would be nice if there are actual tools that are using this first [19:00:25] There is a bit of chicken/egg dynamic here, as I wasn't keen on trying to use the ASGI hack if it wasn't really supported. That said, I have been wanting to experiment with some fastapi based tools (Pynecone) so maybe I'll fire it up