Problem: Access Group is not defined
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- go
- Domain
- authorization
Research direction
The issue names no files, tests, or entry points. Start by locating the stream-creation authorization flow and determine how access groups are represented; done means the group is defined in a minimal form that distinguishes who can and cannot create streams.
Written by the indexing model from the issue text.
Description
Group should be defined in minimalist form
To determine who can vs who cannot create streams in TN
- Dominant language
- Go
- Stars
- 7
- Forks
- 3
- Avg merge
- 3h 2m
- Merged PRs (30d)
- 13
Getting set up
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 trufnetwork/node
-
type: goal
Difficulty 5/5 Over a week Newbie friendliness 35/100
trufnetwork/node#1436 ·
Maintainers usually reply within 1 day
-
Problem: settlement can't tell a capture was taken too earlyPossibly taken @MicBun claimed this 8 days ago. Open
trufnetwork/node#1435 · 1 assignee ·
Maintainers usually reply within 1 day
-
Goal: SDK call for market volume over a time periodPossibly taken @vinarmani claimed this 9 days ago. Open
trufnetwork/node#1429 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
trufnetwork/node#1313 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
trufnetwork/node#1200 · 1 comment ·
Maintainers usually reply within 1 day
All issues in trufnetwork/node
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
siderolabs/terraform-provider-talos#414 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
JuliaComputing/jh#63 · 1 comment ·
-
area/proxy kind/bug priority/backlog triage/accepted
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
lexfrei/cloudflare-tunnel-gateway-controller#840 ·
Maintainers usually reply within 1 day
-
Priority: Normal Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
cloudflare/cloudflared#1747 ·