Skip to content
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

files comming from skeleton have a empty version at the start #161

Closed
individual-it opened this issue Dec 6, 2018 · 6 comments
Closed
Labels

Comments

@individual-it
Copy link
Member

  1. set up a skeleton folder
  2. create a new user
  3. login as this new user
  4. check the versions of files that came from the skeleton

There is a version listed of 0 bytes

image

That does not happen when a file is uploaded, a freshly uploaded file has no versions

@ownclouders
Copy link
Contributor

GitMate.io thinks the contributor most likely able to help you is @ownclouders.

Possibly related issues are #66 (Initializing a new user leads to an empty version created of the skeleton file), #53 (Restoring a previous version of a shared file fails), #156 (restoring a version of a file does not recalculate the checksum), and #67 (Thumbnail preview of last version of a file does not work with scality).

@individual-it
Copy link
Member Author

@davitol
Copy link

davitol commented Oct 24, 2019

@individual-it Dupe of #66 ?

@individual-it
Copy link
Member Author

#66 is about the preview, but yes its related

@SagarGi
Copy link
Member

SagarGi commented May 4, 2022

This scenario is skipped as failing on scality. owncloud/core#40049

@skipOnStorage:ceph @files_primary_s3-issue-161 @notToImplementOnOCIS @newChunking @issue-ocis-1321
@issue-ocis-reva-17 @issue-ocis-reva-56
Scenario: Uploading a file asynchronously does create the correct version that can be restored
    Given the administrator has enabled async operations
    And user "Alice" has uploaded file with content "textfile0" to "textfile0.txt"
    When user "Alice" uploads file "filesForUpload/davtest.txt" asynchronously to "textfile0.txt" in 2 chunks using the WebDAV API
    And user "Alice" uploads file "filesForUpload/lorem.txt" asynchronously to "textfile0.txt" in 2 chunks using the WebDAV API
    And user "Alice" restores version index "1" of file "/textfile0.txt" using the WebDAV API
    Then the HTTP status code of responses on all endpoints should be "202"
    And the version folder of file "/textfile0.txt" for user "Alice" should contain "2" elements
    And the content of file "/textfile0.txt" for user "Alice" should be "Dav-Test"

@DeepDiver1975
Copy link
Member

works as designed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants