You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 14, 2019. It is now read-only.
Sometimes (unfortunately i can't describe it more precisely and also can't reprodruce it) the following happens:
When uploading a file: a filerecord is created but the property copies (where also the key to the document data inside the chunks is) is missing. So i checked if there was anything uploaded in the chunks collection but nothing was there as well.
The Collection which uses GridFS (from Wekan):
Attachments = new FS.Collection('attachments', {
stores: [
// XXX Add a new store for cover thumbnails so we don't load big images in
// the general board view
new FS.Store.GridFS('attachments'),
],
});
FileRecord Entry looks like this (the property key with the chunkId and also the chunk itself is missing):
This happens very rarely to certain times, on different systems with different users. It then fixes itself even without restarting the app or anything at all.
Has some experienced this issue as well? Or can think of something why it happens?
(somehow i think of asynchronous code execution, but this is only a wild guess)
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Sometimes (unfortunately i can't describe it more precisely and also can't reprodruce it) the following happens:
When uploading a file: a filerecord is created but the property copies (where also the key to the document data inside the chunks is) is missing. So i checked if there was anything uploaded in the chunks collection but nothing was there as well.
The Collection which uses GridFS (from Wekan):
FileRecord Entry looks like this (the property key with the chunkId and also the chunk itself is missing):
This happens very rarely to certain times, on different systems with different users. It then fixes itself even without restarting the app or anything at all.
Has some experienced this issue as well? Or can think of something why it happens?
(somehow i think of asynchronous code execution, but this is only a wild guess)
The text was updated successfully, but these errors were encountered: