-
Notifications
You must be signed in to change notification settings - Fork 8
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
Allow force unlock of automated client locks #391
Conversation
9b79845
to
111d146
Compare
/backport to stable30 |
/backport to stable29 |
/backport to stable28 |
/backport to stable27 |
Will fix the conflict once I merged the remaining dependency updates on main |
Signed-off-by: Julius Knorr <[email protected]>
Signed-off-by: Julius Knorr <[email protected]>
Signed-off-by: Julius Knorr <[email protected]>
Signed-off-by: Julius Knorr <[email protected]>
a6dce61
to
f7eb95b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Had a look at the code. Did not test it though.
Signed-off-by: Julius Knorr <[email protected]>
When can we see a release with this? 🙂 |
good question. The backports have been merged so a release including this feature would be nice. I hope with the next minor releases we can get it |
Yes... next minor releases will include this. I'd expect them to be released mid January sometime around the next server releases. |
This will make sure that lock owners can still unlock stale locks from clients that use the token type 2. We will show a confirmation dialog as revoking a lock could cause conflicts with file changes if the client comes back online assuming the lock would still be present.
Steps to test:
Replaces #172
Fix #325
UI changes