nextcloud / nextcloud/user_migration
Incoherent last modification time of file versions after User Migration
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 30
- Forks
- 10
- Avg merge
- 6h 5m
- Merged PRs (30d)
- 12
Description
If we make the hypothesis that the current version is always the most recent one, the output shown after a migration is not coherent
As you can notice, the first file version (1 hour ago) is newer than the current file (5 hours ago), not sure though on whether this issue is related to files_versions or to user_migration
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the migration described in the issue and inspect the interaction between user_migration and files_versions. Compare the timestamps of the current file and its versions after migration; done means the current version and version history have coherent modification times.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100