Skip to content

Conversation

@nfebe
Copy link
Contributor

@nfebe nfebe commented Jun 17, 2024

A concurrency of who is not efficient. Low throughput, underutilization, high latency etc...

A concurrency of who is not efficient. Low throughput, underutilization, high latency etc...

Signed-off-by: fenn-cs <fenn25.fn@gmail.com>
@nfebe nfebe requested review from Pytal, SystemKeeper and susnux June 17, 2024 06:22
@nfebe nfebe self-assigned this Jun 17, 2024
@nfebe nfebe requested a review from skjnldsv as a code owner June 17, 2024 06:22
@nfebe
Copy link
Contributor Author

nfebe commented Jun 17, 2024

/compile

@nfebe
Copy link
Contributor Author

nfebe commented Jun 17, 2024

/backport to stable29

@nfebe
Copy link
Contributor Author

nfebe commented Jun 17, 2024

/backport to stable28

Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.com>
Copy link
Contributor

@SystemKeeper SystemKeeper left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

@SystemKeeper
Copy link
Contributor

Since the original was also included in 27.1, can we backport to stable27 as well?

@susnux susnux merged commit 7eecbab into master Jun 17, 2024
@susnux susnux deleted the fix/bump-delete-request-concurrency branch June 17, 2024 08:38
@backportbot
Copy link

backportbot bot commented Jun 17, 2024

The backport to stable28 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable28
git pull origin stable28

# Create the new backport branch
git checkout -b backport/45902/stable28

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 08323ee8 5eb7b999

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/45902/stable28

Error: No changes found in backport branch


Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

@susnux
Copy link
Contributor

susnux commented Jun 17, 2024

Since the original was also included in 27.1, can we backport to stable27 as well?

I think you need to align on this with @blizzz or @Altahrim ?

@AndyScherzinger
Copy link
Member

/backport to stable27

@backportbot
Copy link

backportbot bot commented Jun 17, 2024

The backport to stable27 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable27
git pull origin stable27

# Create the new backport branch
git checkout -b backport/45902/stable27

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 08323ee8 5eb7b999

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/45902/stable27

Error: No changes found in backport branch


Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

@SystemKeeper
Copy link
Contributor

/backport 08323ee to stable28

@backportbot
Copy link

backportbot bot commented Jun 17, 2024

The backport to stable28 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable28
git pull origin stable28

# Create the new backport branch
git checkout -b backport/45902/stable28

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 08323ee8

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/45902/stable28

Error: No changes found in backport branch


Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

@blizzz blizzz mentioned this pull request Jul 24, 2024
@susnux susnux moved this from 🏗️ In progress to ☑️ Done in 📁 Files team Mar 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: ☑️ Done

Development

Successfully merging this pull request may close these issues.

8 participants