concurrent transactions with write followed by reading fails due to timeout
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 38/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- databases
Research direction
Start with test/integration/cls.test.js#L120-L137 and review the CockroachDB issue linked in the report to confirm the transaction behavior. Document that a write held open in one transaction can cause a read from the same table in another transaction to time out, unless a supported workaround is identified.
Written by the indexing model from the issue text.
Description
Relevant test: https://github.com/sequelize/sequelize/blob/main/test/integration/cls.test.js#L120-L137
Context:
Doing a write in a transaction (and not committing) that uses one table and a read from the same table in a separate transaction causes timeout.
This is expected behaviour in Cockroach as serializable transactions cause writes to hold exclusive locks.
We do not expect the behaviour from the test above to succeed or Cockroach to change in a way such that the above test will succeed. We'll likely have to document that this is expected behaviour for sequelize-cockroachdb if we can't find a workaround.
Relevant issue: https://github.com/cockroachdb/cockroach/issues/61269
- Dominant language
- JavaScript
- Stars
- 54
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from cockroachdb/sequelize-cockroachdb
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 1/5 Under an hour Newbie friendliness 45/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
cockroachdb/sequelize-cockroachdb#153 · 1 comment ·
All issues in cockroachdb/sequelize-cockroachdb
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
swc-project/swc-ai-issues#995 ·
-
[workshop-sim] Repair: Strengthen checkpoints and lock-file prerequisite in Agentic intro (Step 5)Openfeedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
githubnext/gh-aw-workshop#5973 ·
Maintainers usually reply within 1 day
-
Development server fails with webpack-dev-server 6.1.0Possibly taken @utsxvrai claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
rabbitmq/rabbitmq-website#2733 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 80/100
kentcdodds/kcd-skills#32 ·
-
Edit: Cool ChannelOpenapproved channels:edit check:passed
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day