My conscious is a jukebox
Wed, Oct 21
Mon, Oct 19
An important distinction to be made with Event Metrics – ultimately the "report" data in Event Metrics gets pre-stored in a database, indefinitely. This isn't a problem in terms of storage because they are just numbers. In addition, Event Metrics had a timestamp of when the report was generated, and you as the user will always get that version of the report until you ask for an updated version. In our case, we end up with a epub (or other format), which is not as cheap to store, and also we want to automatically ensure the user is served the latest possible version. So the two systems won't work exactly the same.
Fri, Oct 16
I think this and T262631 are the only tasks in the AutoEdits column that aren't about updates to semi_automated.yml. I've no reservation against a new column (or a project), but I still don't think it would solve much. I have begun preliminary work on T262631: Move AutoEdits configuration to on-wiki JSON pages which will move the burden of updating to the community and make the new column/project redundant. That will take a good while to complete with my current workload, probably a few weeks.
Hmm, that's a pity! But I understand load balancing is more important than sql-optimizer :)
Thu, Oct 15
Task for caching credits info: T265660
Wed, Oct 14
For some reason I was under the impression that you needed a NDA to be able to access a VPS.
Thanks for reporting this. The old link should now work (but you may need to clear your browser cache first).
@dom_walden Ready for QA again! I thought I'd ping you since this was incorrectly in your column for almost 2 months... now it's intentionally there :)
Tue, Oct 13
This is now live. Maintainers of CopyPatrol should get an email when there are no cases younger than 4 hours old. @Diannaa you no longer need to ping us, but I'm not saying you can't, because of course you still can :) I should also point out that it seems you work on a slightly earlier schedule than most of us here at CommTech, and historically by the time I wake up the bot had fixed itself. But at least now we have some automation in place and may be able to catch things earlier. The next step obviously is to figure out why it keeps going down and what we can do to mitigate it. More on that soon, I hope!
Mon, Oct 12
Fri, Oct 9
Looks like activity has long since resumed. I'm happy to report, by the way, that our monitoring of the feed (T262767) will be deployed soon, and you will no longer need to inform us when there is no activity :)
Resolved per T264823
Thu, Oct 8
This is live on the staging tool. There are two URL params that can be passed, lang (default en) and offset (default 4), where offset is the number of hours.
Wed, Oct 7
Okay, glad to hear it is working! If you ever are convinced there is an issue, do please feel free to create a new task. Thanks!
Tue, Oct 6
For some quick numbers, I looked at the month of September 2020:
Mon, Oct 5
@Kizule Where do we stand with the bot? I see now it has edited numerous times: https://sr.wikipedia.org/wiki/Special:Contribs/Community_Tech_bot. Does these look correct to?
Fri, Oct 2
Thu, Oct 1
Still no new reports, and iThenticate links are failing to load. I wonder if we are out of credits at the Turnitin service?
It's merged now, we can iterate on it as necessary. I see dmaza moved this task to the Done column so I'll mark it as resolved.
FileNotFoundError: [Errno 2] No such file or directory: '/mnt/nfs/labstore-secondary-tools-project/commtech-commons/bot/i18n/sr.json'
How about "Wikisource Download"? So the proxy name could be ws-download.
I've restarted the bot, we'll see if that does anything. As for buttons not working, I suspect that was related to the general instability of Toolforge we've been experiencing the last few days, see https://stats.uptimerobot.com/BN16RUOP5 (the only tools at 100% uptime are on VPS, not Toolforge).
Wed, Sep 30
Merged and deployed, now waiting for the bot to edit https://sr.wikipedia.org/wiki/Special:Contribs/Community_Tech_bot
Could we solicit some help to get LiquidThreads fixed?
Tue, Sep 29
Mon, Sep 28
Wonderful! Closing as resolved.
Not an issue with the Pageviews tool, rather the data that it serves. Anyway I agree that this is most surely a bot.
Fri, Sep 25
With 1.35.0 shipped, I think we can close this.
Well that didn't take long: https://ar.wikipedia.org/wiki/Special:Diff/50662771
@alanajjar Apologies for the long wait! This has now been deployed. We will be keeping an eye on Special:Contribs/Community Tech bot. Let us know if something looks off, or if the bot failed to edit when you think it should have.
Thu, Sep 24
Sep 24 2020
Sep 23 2020
Sep 22 2020
Sep 21 2020
See also T258098: Purge unused watchlist rows which should fee up a sizable amount of space in the watchlist table (depending on the wiki), and has some ideas about future-proofing. I believe this is a worthwhile pursuit regardless of what happens with watchlist expiry.
Sep 20 2020
Sep 19 2020
Sep 18 2020
Sep 16 2020
Note also the dropdown itself either needs to be full-width or centered.
It turns out the job on Toolforge was stuck. I restarted it and the bot is now editing other wikis. By all indications it should be running on nl.wiktionary too, only it hasn't encountered a file used on nl.wiktionary yet. I'll continue to monitor.
Sep 15 2020
Sep 14 2020
To have it trigger alerts when no new entries are detected since some time, you can add a special endpoint in the webservice to serve GOOD or BAD keywords. This healtcheck would be defined by sql query "does there any new entry in last 4 hours for each wiki"