nextcloud / nextcloud/end_to_end_encryption

Lock - Unlock

Open
#361 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage feature: locking
Dominant language
PHP
Stars
320
Forks
36
Avg merge
1d 8h
Merged PRs (30d)
81

Description

It happens that an directory (fileID) remains locked for some client issue and is not possible write the lock (file id + token) in the internal DB (crashed ... or for example iOS go to in background mode == all network events automatically return with error), so the directory remains blocked.

it is requested:

  • API for the list of all directory (file id) blocked with time stamp & e2eToken
  • API for remove the block without the token with and not with the file ID (without = remove all directory locked)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the repository's existing server API and lock-handling entry points; the issue does not name specific files or tests. Done means defining and implementing APIs to list locked directories with timestamps and e2eTokens, and to remove a lock by file ID or remove all locks without a token.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
api, backend, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.