-
Notifications
You must be signed in to change notification settings - Fork 12
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
Errors uploading to Door43 #5890
Comments
@cckozie @benjore - this error is actually a server error returned by Door43. Unfortunately when we changed to Isomorphic-git, it now throws exceptions instead of returning an error code. That's why we are now suddenly getting these strange error messages on upload failure. So I made fix to handle this and show the normal upload error message. I've also changed so we will show the project loading dialog while alignment data is being checked (creating the USFM3 file) and local file changes committed to git which is a major amount of the time consumed. This way the user sees something is happening before upload begins. |
@cckozie - this is a great "worst case" upload test. It imports a large book with alignments. When you open WA it initializes the data structures on disk. But since you don't change verses, none of the file changes are committed to git yet. Then when you do upload:
|
@cckozie - looks like this may have been due to git running so slow. Tested in Windows with fix for #5798 and don't see a problem. should work in https://tc-builds.door43.org/build/release-v1.1.3/translationCore-win-x64-1.1.3-64d8fb7.setup.exe |
I'm moving this to the QA Watch lane. |
Haven't seen this for some time now. Closing. |
1.1.2 (134656f)
I have not seen this before, but believe that some user's have.
Downloaded the usfm3 Acts file from https://git.door43.org/Door43-Catalog/en_ult/raw/branch/master/45-ACT.usfm and imported it. Loaded it in wA but did not make any changes to alignments, then uploaded. I received the same error twice. The third time it worked.
en_ult_act_book.zip
The text was updated successfully, but these errors were encountered: