Error "Missing unknown 0000..." for newly created resources

forTEXT / catma

Computer Assisted Text Markup and Analysis

https://www.catma.de

GNU General Public License v3.0

87 stars 8 forks source link

Error "Missing unknown 0000..." for newly created resources #310

Closed TomSgrizzi closed 2 years ago

TomSgrizzi commented 2 years ago

Describe the bug After I upload a few documents (.docx or .txt) I get this error and lose access to my project. If I refresh the page, or log in again I still have no access to the project and all the documents uploaded are gone.

To Reproduce Steps to reproduce the behavior:

Go to 'Project'
Click on 'Add Document'
Upload them
After few uploads the errors appear. It appears immediately with bulk upload. If I try to upload them one by one inevitably after a few it crushes.

Expected behavior I should be able to upload my documents, work on them and access my project

Screenshots or screen recording I attached screenshots

Information about your environment

OS: Win11
Browser Chrome

Additional context Add any other context about the problem here. Screenshot (1111) Screenshot (1113)

Thanks a lot in advance!

maltem-za commented 2 years ago

Thank you kindly for the report. We are investigating the root cause of this issue.

In the mean time, we ask that anyone experiencing this error please send an email to support@catma.de with their username / email address that they use to log in to CATMA and the name of the project affected. This will allow us to solve the problem for you in the short term.

maltem-za commented 2 years ago

The error occurs due to badly initialised submodules when new resources are created. The root cause is not yet known.

Symptoms:

Staged changes in the root repo
git submodule output containing one or more of the following: 0000000000000000000000000000000000000000 <resource container directory>/<resource GUID> ()
Submodule directory containing only a .git file and nothing else, no commits

Workaround:

Manually re-add the submodule

maltem-za commented 2 years ago

This issue could not be correlated with any of the recent releases or code changes. The root cause remains a mystery, however it appears to be a JGit bug that is somehow influenced by external factors (as it occurs randomly and we weren't able to reproduce it reliably).

A workaround has been implemented, which will go live in the coming days. This issue will remain open until then.

maltem-za commented 2 years ago

Closing with the release of 6.5.1