-
Notifications
You must be signed in to change notification settings - Fork 0
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
Validation and lemmatisation of remote ATF files occasionally fails #144
Comments
Another example, with more logging enabled for good measure. Successful run:
Failing run:
Note that Lines 8 to 12 in 0050341
|
In case it's not clear, the error message seems to indicate that the corresponding temporary files have not been created on the server. This could be due to not enough storage (unlikely if it only happens occasionally) or because we send the follow-up request too quickly. The latter might explain why it's not a problem with "local" (i.e. not-on-server) files, if the latency from the network allows enough time for the server to start processing the request. Perhaps adding a little delay before starting to send the status requests (to see if the result is ready) would smooth this, similar to the fix in #112? |
Trying to run lemmatisation or validation of ATF files on a remote server occasionally, but not always, fails with error
No problems when running the same commands on a local file with the same content.
This is the part of the code I'm less familiar with, but looking at the source I'm struggling to see what we do differently between remote and local files (and remote files are actually local for the remote instance of VS Code we're running).
Log of a successful run of validation on a remote file:
Log of the same command, now unsuccessful, run soon after:
The text was updated successfully, but these errors were encountered: