Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug (watcher): retry on files whose blob has yet not been found. #302

Open
SHAcollision opened this issue Jan 26, 2025 · 2 comments
Open
Labels
bug Something isn't working

Comments

@SHAcollision
Copy link
Collaborator

SHAcollision commented Jan 26, 2025

If a /file and a /blob are uploaded to the homeserver concurrently, the File will finish faster than the Blob , therefore, there is a big change that Nexus watcher will process a /file event whose blob does not yet exists leading to:

https://nexus.staging.pubky.app/static/files/cf3eris488gmgcribc9diomexbyddsr98dm9ejbcsorfar3sttwo/0032S6VRC92BG net::ERR_CONTENT_LENGTH_MISMATCH 200 (OK)

Ideally, this /file event line should be left to try later using the new Retry Manager #247 @tipogi

@SHAcollision SHAcollision added the bug Something isn't working label Jan 26, 2025
@tipogi
Copy link
Collaborator

tipogi commented Jan 27, 2025

File Retry Manager is not yet good handled because I would like to work on that when the file related PR (#255) is closed. Once it is merged, I will take a look that error 👍

@tipogi
Copy link
Collaborator

tipogi commented Jan 27, 2025

or could we create the /file event in the front end, once the file is uploaded?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants