Need variants of ExecuteInTx and ExecuteTx that take a `fn(context.Context, ...)` as arg
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start by locating the ExecuteTx and ExecuteInTx definitions and their existing callback signatures. Review nearby tests or call sites to understand the current behavior, then add variants whose callbacks receive context.Context while keeping the requested transaction behavior consistent. Done means the new APIs accept context-aware callbacks and are covered by the relevant existing tests.
Written by the indexing model from the issue text.
Description
The ExecuteTx and ExecuteInTx APIs take a function callback that only takes either no argument or a tx object.
We want to pass a callback instead that takes the context as argument.
cc @rafiss
- Dominant language
- Go
- Stars
- 170
- Forks
- 78
- 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/cockroach-go
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
cockroachdb/cockroach-go#188 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 45/100
cockroachdb/cockroach-go#185 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
cockroachdb/cockroach-go#169 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
cockroachdb/cockroach-go#166 · 4 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
cockroachdb/cockroach-go#165 ·
All issues in cockroachdb/cockroach-go
Similar issues
-
☢️ Bug v3
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
area/import-export area/projects concern/ux
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
go-vikunja/vikunja#4455 · 1 comment ·
Maintainers usually reply within 2 days
-
Dependabot PRs no longer merge automaticallyPossibly taken @dwisiswant0 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
projectdiscovery/urlfinder#160 ·
Maintainers usually reply within 1 day
-
database
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
chnm/legal-modernism#450 ·
Maintainers usually reply within 1 day
-
tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day