User Details
- User Since
- Oct 8 2025, 8:23 AM (27 w, 5 h)
- Availability
- Available
- LDAP User
- Unknown
- MediaWiki User
- Xinacod [ Global Accounts ]
Sun, Apr 12
Thank you so much, @MusikAnimal! Really glad it's working well in production and that Barack Obama is back 🎉 The 1-2s improvement and the disk cleanup numbers are very satisfying to see at scale. Happy to have contributed!
Thu, Apr 2
Good suggestion — reverted the immediate deletion and added a cleanup_legacy_pickles management command instead. It only deletes legacy files older than N days that already have a new-format counterpart, so nothing gets lost. Supports --dry-run too. PR updated.
Good call on the cronjob approach — I'll revert the immediate deletion and add a management command instead. Also noted on the Barack Obama timeout; makes sense given the XML dump bypass was specifically for high-revision articles. Will keep that in mind going forward.
Hi @MusikAnimal , I will take a look at the Whocolor handler and update the code, thanks.
Tue, Mar 31
Wed, Mar 25
Perfect, I will start looking into it ASAP.
Thanks for the context @MusikAnimal. To answer your question directly: yes, this cache is per-Pywikibot instance — each deployment writes its own local copies of the WikiWho data. There's no shared storage between instances.
Thu, Mar 19
Hi @ParasharSarthak and @Jnanaranjan_sahu — opened one more PR today:
PR #64 — fixes a few reliability issues I spotted while testing locally:
- /api/upload and /api/edit_page were calling match[0][0] on the regex result without checking if it was empty, so any malformed URL would crash with an IndexError instead of returning a proper 400 - download_image() was calling .replace() on content-type without checking if the header existed — AttributeError on certain
responses
- Added timeout to every requests call (30s for API calls, 60s for image downloads, 120s for file upload POST) — without these, a slow wiki endpoint can hang a worker thread indefinitely
- Celery task had no error handling or logging around the CSRF fetch and upload POST — failures were silent. Wrapped both with try/except and logger.error
- Fixed inconsistent "error": [] vs "errors": [] across two API routes
https://github.com/indictechcom/wikifile-transfer/pull/64
Also working on my proposal — planning to cover batch upload, upload history with retry, category localization, and test coverage. Happy to discuss the design before I finalize anything.Mar 16 2026
Hi again — quick update on what I've been working on since my last message.
Mar 9 2026
Week 12: February 20, 2026 – February 24, 2026
Feb 21 2026
Hi @ParasharSarthak and @Jnanaranjan_sahu, I'm interested in contributing to Wikifile-Transfer for GSoC 2026.
Feb 20 2026
Week 11: February 16, 2026 – February 20, 2026 Overview of Tasks Completed
Feb 13 2026
Week 10: February 9, 2026 – February 13, 2026
Feb 7 2026
Week 9: February 2, 2026 – February 6, 2026
Jan 31 2026
Week 8: January 26, 2026 – January 30, 2026
Jan 24 2026
Week 7: January 18, 2026 – January 22, 2026
Jan 16 2026
Week 6: Mid-Point Progress Report
Outreachy Internship - PendingChangesBot-ng Development
Reporting Period: Weeks 1-5 (December 8, 2025 - January 10, 2026)
Current Status: Week 6 of 13 (January 13-17, 2026)
Jan 10 2026
Week 5: January 5 – January 10, 2026
Jan 9 2026
WikiWho Pickle Compression Investigation - COMPLETE
Jan 8 2026
Jan 6 2026
Jan 2 2026
Week 4: December 29, 2025 - January 2, 2026
Dec 26 2025
Week 3: December 22 - 26 , 2025
Dec 20 2025
Week 2: December 15, 2025 - December 21, 2025
Dec 13 2025
Week 1: December 8, 2025 - December 12, 2025
Dec 8 2025
@taavi Thanks for the guide.
Oct 11 2025
Howdo we get access to zulip @Aklapper
Oct 10 2025
check this out @shreya-bhagat
Welcome @Breechep , if you get stuck while setting your environment up using the resources above, do not hesitate to drop your question here. we will help out.
Oct 9 2025
@Pcnerd9 I think the first option is correct because you will work with your answers to those questions during implementation. imo though
HI @Aradhya05 Code for task is written inside same cell you forked, if you check the url it have changed to your username after forking it, that is also what you submit during contribution documentation. If you reread the above instruction for us you should be good.