bitseq: invalid bit range on IPv6
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.2k
- Forks
- 875
- PR merge metrics
- No merged PRs in 30d
Description
This issue occurred during append IPAMV6Conf to IPAMConf struct to automatic allocate IPv6 address as follows:
invalid bit range [0, 18446744073709551615]
FILE:
bitseq/sequence.go
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start with bitseq/sequence.go, then trace the IPAMV6Conf append path described in the report and reproduce automatic IPv6 allocation. Done means the invalid bit range error no longer occurs during that allocation; the payload does not name a test or additional file to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100