Skip to content
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

[stable27] fix: Catch Deadlock properly as execute throws Doctrine exceptions not our wrapped ones #38440

Merged
merged 1 commit into from
May 25, 2023

Conversation

juliusknorr
Copy link
Member

@juliusknorr juliusknorr commented May 24, 2023

Followup fix to #37820 since the Cache update method uses IQueryBuilder::execute which does not wrap the Doctrine exception as the phpdoc annotation wrongly defines.

Fix only against stable27 as for master i think we should fix the wrapping instead: #38439

@juliusknorr juliusknorr force-pushed the bugfix/stable27/catch-doctrine-exception branch 2 times, most recently from 4cd952e to c0eefa4 Compare May 24, 2023 15:10
Signed-off-by: Julius Härtl <jus@bitgrid.net>
@juliusknorr juliusknorr force-pushed the bugfix/stable27/catch-doctrine-exception branch from c0eefa4 to ce8e21d Compare May 24, 2023 18:46
@juliusknorr juliusknorr marked this pull request as ready for review May 25, 2023 06:14
@juliusknorr juliusknorr added bug 3. to review Waiting for reviews labels May 25, 2023
@juliusknorr juliusknorr changed the title fix: execute throws docrine exceptions not our wrapped ones fix: Catch Deadlock properly as execute throws Doctrine exceptions not our wrapped ones May 25, 2023
@juliusknorr juliusknorr added this to the Nextcloud 27 milestone May 25, 2023
@szaimen szaimen changed the title fix: Catch Deadlock properly as execute throws Doctrine exceptions not our wrapped ones [stable27] fix: Catch Deadlock properly as execute throws Doctrine exceptions not our wrapped ones May 25, 2023
@szaimen
Copy link
Contributor

szaimen commented May 25, 2023

@juliushaertl shouldnt we also push this to master in case #38439 does not get merged until the next branch-off? We can then still revert this change in #38439

@blizzz blizzz mentioned this pull request May 25, 2023
10 tasks
Copy link
Member

@blizzz blizzz left a comment

Choose a reason for hiding this comment

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

OK with the outlook of a proper wrapping fix :)

@blizzz blizzz merged commit ebb2f81 into stable27 May 25, 2023
@blizzz blizzz deleted the bugfix/stable27/catch-doctrine-exception branch May 25, 2023 10:27
@szaimen
Copy link
Contributor

szaimen commented May 25, 2023

/backport to stable26

@szaimen
Copy link
Contributor

szaimen commented May 25, 2023

/backport to stable25

@szaimen
Copy link
Contributor

szaimen commented May 25, 2023

/backport to master

@juliusknorr
Copy link
Member Author

/backport to stable24

@backportbot-nextcloud
Copy link

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

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

# Create the new backport branch
git checkout -b fix/foo-master

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts. Resolve them.
git cherry-pick abc123

# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-master

More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport

@backportbot-nextcloud
Copy link

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

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

# Create the new backport branch
git checkout -b fix/foo-stable25

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts. Resolve them.
git cherry-pick abc123

# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable25

More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport

@backportbot-nextcloud
Copy link

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

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

# Create the new backport branch
git checkout -b fix/foo-stable26

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts. Resolve them.
git cherry-pick abc123

# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable26

More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport

@backportbot-nextcloud
Copy link

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

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

# Create the new backport branch
git checkout -b fix/foo-stable24

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts. Resolve them.
git cherry-pick abc123

# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable24

More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport

@szaimen
Copy link
Contributor

szaimen commented May 25, 2023

/backport to stable26

@szaimen
Copy link
Contributor

szaimen commented May 25, 2023

/backport to stable25

@backportbot-nextcloud
Copy link

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

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

# Create the new backport branch
git checkout -b fix/foo-stable25

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts. Resolve them.
git cherry-pick abc123

# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable25

More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport

@szaimen
Copy link
Contributor

szaimen commented May 25, 2023

/backport to stable25

@backportbot-nextcloud
Copy link

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

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

# Create the new backport branch
git checkout -b fix/foo-stable26

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts. Resolve them.
git cherry-pick abc123

# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable26

More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport

@szaimen
Copy link
Contributor

szaimen commented May 25, 2023

/backport to master

1 similar comment
@szaimen
Copy link
Contributor

szaimen commented May 25, 2023

/backport to master

@szaimen
Copy link
Contributor

szaimen commented May 25, 2023

/backport to stable27

@szaimen
Copy link
Contributor

szaimen commented May 25, 2023

/backport to stable26

@szaimen
Copy link
Contributor

szaimen commented May 25, 2023

/backport to stable25

@szaimen
Copy link
Contributor

szaimen commented May 25, 2023

/backport to stable24

@backportbot-nextcloud
Copy link

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

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

# Create the new backport branch
git checkout -b fix/foo-master

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts. Resolve them.
git cherry-pick abc123

# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-master

More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport

@backportbot-nextcloud
Copy link

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 fix/foo-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 abc123

# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable27

More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport

@backportbot-nextcloud
Copy link

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

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

# Create the new backport branch
git checkout -b fix/foo-stable25

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts. Resolve them.
git cherry-pick abc123

# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable25

More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport

@backportbot-nextcloud
Copy link

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

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

# Create the new backport branch
git checkout -b fix/foo-stable26

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts. Resolve them.
git cherry-pick abc123

# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable26

More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport

@backportbot-nextcloud
Copy link

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

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

# Create the new backport branch
git checkout -b fix/foo-stable24

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts. Resolve them.
git cherry-pick abc123

# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable24

More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport

@szaimen
Copy link
Contributor

szaimen commented May 26, 2023

/backport to master

@szaimen
Copy link
Contributor

szaimen commented May 26, 2023

/backport to stable26

@szaimen
Copy link
Contributor

szaimen commented May 26, 2023

/backport to stable25

@szaimen
Copy link
Contributor

szaimen commented May 26, 2023

/backport to stable24

@backportbot-nextcloud
Copy link

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

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

# Create the new backport branch
git checkout -b fix/foo-stable24

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts. Resolve them.
git cherry-pick abc123

# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable24

More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3. to review Waiting for reviews bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants