Skip to content

Fix bug where lock is acquired on wrong database table - #4863

Closed
arnaudsjs wants to merge 2 commits into
masterfrom
issue/4834-set-lock-on-correct-table
Closed

Fix bug where lock is acquired on wrong database table#4863
arnaudsjs wants to merge 2 commits into
masterfrom
issue/4834-set-lock-on-correct-table

Conversation

@arnaudsjs

Copy link
Copy Markdown
Contributor

Description

Fix bug where lock is acquired on the ConfigurationModel table instead of the ResourceAction table. This bug causes deadlocks.

closes #4834

Self Check:

  • Attached issue to pull request
  • Changelog entry
  • Type annotations are present
  • Code is clear and sufficiently documented
  • No (preventable) type errors (check using make mypy or make mypy-diff)
  • Sufficient test cases (reproduces the bug/tests the requested feature)
  • Correct, in line with design
  • End user documentation is included or an issue is created for end-user documentation

Reviewer Checklist:

  • Sufficient test cases (reproduces the bug/tests the requested feature)
  • Code is clear and sufficiently documented
  • Correct, in line with design

@arnaudsjs arnaudsjs added the merge-tool-ready This ticket is ready to be merged in label Sep 20, 2022
@inmantaci

Copy link
Copy Markdown
Contributor

Processing this pull request

inmantaci pushed a commit that referenced this pull request Sep 20, 2022
…because it acquires a table-level lock on an incorrect database table. (Issue #4834, PR #4863)

# Description

Fix bug where lock is acquired on the ConfigurationModel table instead of the ResourceAction table. This bug causes deadlocks.

closes #4834

# Self Check:

- [x] Attached issue to pull request
- [x] Changelog entry
- [x] Type annotations are present
- [x] Code is clear and sufficiently documented
- [x] No (preventable) type errors (check using make mypy or make mypy-diff)
- [x] Sufficient test cases (reproduces the bug/tests the requested feature)
- [x] Correct, in line with design
- [ ] ~~End user documentation is included or an issue is created for end-user documentation~~

# Reviewer Checklist:

- [ ] Sufficient test cases (reproduces the bug/tests the requested feature)
- [ ] Code is clear and sufficiently documented
- [ ] Correct, in line with design
@inmantaci

Copy link
Copy Markdown
Contributor

Merged into branches master in ddada43

inmantaci pushed a commit that referenced this pull request Sep 20, 2022
…because it acquires a table-level lock on an incorrect database table. (Issue #4834, PR #4863)

# Description

Fix bug where lock is acquired on the ConfigurationModel table instead of the ResourceAction table. This bug causes deadlocks.

closes #4834

# Self Check:

- [x] Attached issue to pull request
- [x] Changelog entry
- [x] Type annotations are present
- [x] Code is clear and sufficiently documented
- [x] No (preventable) type errors (check using make mypy or make mypy-diff)
- [x] Sufficient test cases (reproduces the bug/tests the requested feature)
- [x] Correct, in line with design
- [ ] ~~End user documentation is included or an issue is created for end-user documentation~~

# Reviewer Checklist:

- [ ] Sufficient test cases (reproduces the bug/tests the requested feature)
- [ ] Code is clear and sufficiently documented
- [ ] Correct, in line with design
@inmantaci inmantaci closed this Sep 20, 2022
@inmantaci
inmantaci deleted the issue/4834-set-lock-on-correct-table branch September 20, 2022 10:29
@inmantaci

Copy link
Copy Markdown
Contributor

Processing #4866.

inmantaci pushed a commit that referenced this pull request Sep 20, 2022
…because it acquires a table-level lock on an incorrect database table. (Issue #4834, PR #4863)

Pull request opened by the merge tool on behalf of #4863
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

merge-tool-ready This ticket is ready to be merged in

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Investigate deadlock on the delete path

4 participants