Hi @ParasharSarthak @Jnanaranjan_sahu
I’ve worked on fixing the AxiosError (500) during file uploads and have opened a PR for it The fix mainly adds proper validation and structured error handling across the upload pipeline (/api/upload, utils, and async task), preventing backend crashes and returning consistent JSON responses instead of raw 500 errors
I’d really appreciate any feedback or suggestions for improvement Thanks!

On a closer review I realized that retry behavior is not currently configured in the Celery task My earlier mention of retry analysis was premature I’m now evaluating whether adding controlled retries for transient failures would improve reliability Would it make sense to introduce retries specifically for network-related exceptions (e.g., requests failures), or are there considerations in this workflow that I should be aware of before proposing such a change? @ParasharSarthak @Jnanaranjan_sahu @Gopavasanth

Today I performed a deeper analysis of the upload pipeline, focusing on the process_upload() function and its interaction with the /api/upload route. I traced how file size validation determines whether the upload is processed synchronously or delegated to a Celery background task for larger files.
I reviewed the Celery task implementation to understand how asynchronous uploads are queued and executed. In particular, I examined the exception handling logic, retry behavior, and how failures are logged.
I also explored helper utilities in utils.py, especially how authenticated sessions are created and how external requests are handled during the transfer process.
Currently, I am evaluating potential improvement areas, such as making retry limits configurable and improving error logging for better observability. I plan to continue exploring failure scenarios and edge cases in the async workflow

Hi, @ParasharSarthak @Jnanaranjan_sahu
I’ve been exploring the Wikifile-Transfer project locally and working on understanding the overall architecture and upload flow.
So far, I have
Successfully run the backend locally.
Resolved configuration-related issues and handled the OAuth initialization problem for local development.
Fixed the template loading issue so the Flask server runs without crashing.
Studied the /api/upload route in detail to understand the complete file transfer flow.
Traced how download_image(), authenticated_session(), and process_upload() work together.
Understood the sync vs async upload logic (direct upload for files <50MB and Celery-based async processing for larger files).
Reviewed how the project separates frontend and backend components.
I’m currently going through utils.py and the Celery task logic to get a deeper understanding of the upload mechanism and identify possible areas for enhancement (especially around batch uploads and test coverage).
I also had a small question regarding the contribution timeline:
Are we not allowed to submit PRs before March 16, or is it fine to continue contributing before that date?
Looking forward to your guidance

Hi, I am interested in contributing to the Wikifile-Transfer project for GSoC 2026
I have created my Phabricator account and I am reviewing the project details. I will begin setting up the development environment locally.
Could you please guide me towards beginner-friendly microtasks to get started?
Thank you @ParasharSarthak @Jnanaranjan_sahu