real world transactional workload
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
Research direction
The issue names no files, tests, entry points, or concrete transactional workload. Start by clarifying the intended provisioning behavior and acceptance criteria with the maintainers, then locate the relevant Go implementation and define robot-tested scenarios. Done should mean the agreed real-world transactional workflow is implemented and fully covered by automated tests.
Written by the indexing model from the issue text.
Description
Real world, useful transactional provisioning. Fully robot tested.
- Dominant language
- Go
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
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 stackql/stackql-devel
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
stackql/stackql-devel#110 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
stackql/stackql-devel#103 ·
-
stackql/stackql-devel#101 · 1 comment · 1 assignee ·
-
stackql/stackql-devel#100 · 1 assignee ·
-
stackql/stackql-devel#99 · 1 assignee ·
All issues in stackql/stackql-devel
Similar issues
-
area/dev-productivity area/disaster-recovery area/ipcei kind/enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
kind/bug status/0-triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
🤔 refinement needed
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
equinor/radix-operator#1979 ·