Commit d5e9bd8
chore(performance): only check permissions when changing content
chore(performance): only check permissions when changing content
Avoid setting up the file system for read only shares.
Also clarify the behavior:
Updates are silently dropped as they were before.
Previously `stepsToInsert` would always be empty for readonly requests,
due to the continue in the loop collecting the steps.
So there was no way to trigger the
```
NotPermittedException('Read-only client tries to push steps with changes')
```
Keep this behavior for now so we can backport this commit.
Clients on readonly shares regularly push updates to the server
to update their awareness state - i.e. let others know they are still around.
These requests trigger the addStep function
even if they do not actually change the content of the file.
Signed-off-by: Max <max@nextcloud.com>1 parent abcb270 commit d5e9bd8
1 file changed
Lines changed: 3 additions & 8 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
207 | 207 | | |
208 | 208 | | |
209 | 209 | | |
210 | | - | |
211 | | - | |
212 | 210 | | |
213 | 211 | | |
214 | 212 | | |
215 | 213 | | |
216 | 214 | | |
217 | | - | |
218 | | - | |
219 | | - | |
220 | 215 | | |
221 | 216 | | |
222 | 217 | | |
| |||
225 | 220 | | |
226 | 221 | | |
227 | 222 | | |
228 | | - | |
229 | | - | |
| 223 | + | |
| 224 | + | |
| 225 | + | |
230 | 226 | | |
231 | | - | |
232 | 227 | | |
233 | 228 | | |
234 | 229 | | |
| |||
0 commit comments