fix(Scanner): Use time based limit for the transaction#56290
Conversation
3f93896 to
ca2607d
Compare
|
/backport to stable32 |
|
/backport to stable31 |
618bd87 to
d63a245
Compare
|
/backport! to stable30 |
|
The backport to # Switch to the target branch and update it
git checkout stable30
git pull origin stable30
# Create the new backport branch
git checkout -b backport/56290/stable30
# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 8dd6e002 d63a2454
# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/56290/stable30Error: Failed to push branch backport/56290/stable30: remote: Invalid username or token. Password authentication is not supported for Git operations. Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports. |
|
/backport to stable33 |
|
I think we should keep the max entry to commit limit, so that we have two limits instead of one. I'll try to look into it. |
Signed-off-by: Louis Chmn <[email protected]>
d63a245 to
fed9e42
Compare
e4a42f3 to
f499ea0
Compare
Using the node count does not help if handling a node is slow. Signed-off-by: Louis Chmn <[email protected]>
Signed-off-by: Louis Chmn <[email protected]>
Signed-off-by: Louis Chmn <[email protected]>
f499ea0 to
03bfa32
Compare
|
Closing as we will rather remove the transaction all together |
Using the node count does not help if handling a node is slow.
This prevent locking the database for unknown amount of time.
10 seconds is arbitrary, but I don't see any reason to no go even lower.