-
Notifications
You must be signed in to change notification settings - Fork 6
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
The server doesn't index #1079
Comments
Just wanted to add that this happens to me basically every time I upload a fit and attempting a reupload fixes the indexing issue every time. |
If I login into the server and try touching some of the files. it updates instanteously:
So I am not sure what is happening. |
That said I am all for improving that infrastructure. |
Are there no errors in the logs? Maybe in |
No, nothing interesting. |
Meh, I was hoping for a I guess it would be good to add a logger to print "file received: " "starting index" and so on to check (if it exists you should see 2 of those for the 210127 fit). Otherwise a vp-check (even done automagically at the end of every upload) would do the trick I guess. |
would somebody EDIT: asking for a friend |
Unlikely. Theoretically it could cause the fit seeing less data to finish last so some data gets lost until another reindexing is triggered, but seems convoluted. |
I've just tried uploading a fit, waited for a few minutes and it was still not indexed. Tried to upload it again and it it worked. Tried again and this time it failed (so it was already there)*.
I think using said failure as the marker of whether the fit is upload it or not might be a quick and dirty but useful hack for the bot...
For a better solution, I guess we could have a
vp-check
(orvp-get --dry
or whatever) that just tells you whether the file is indexed or not (and that forces reindex).I've had a quick look at the script and maybe it makes sense to go for a simple systemd based rule? It's also based on inotify so it would only work if the problem is due to the external wrapper and not to the system forgetting to notify.
Tried to have a look at why it failed but can't open the logs. If you want to have a look the fit I was trying to upload was
210127-n3fit-001
*Come to think about it I've actually gotten a few mails lately asking me to upload this or that fit and I just assumed I had forgotten to do it (which is also a very likely explanation) but it might not have been my fault!
The text was updated successfully, but these errors were encountered: