RoaringBitmap / RoaringBitmap/roaring
How can you tell when a bitmap is ready to be read from?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.9k
- Forks
- 262
- Avg merge
- 2h 34m
- Merged PRs (30d)
- 8
Description
Hi!
I've noticed that this:
`func calculateBitSetChecksum(dest *checksumStruct, bitmap map[string]uint, imageAsBaseSixtyFour string, numberOfPixels int) {
for i := 0; i < len(imageAsBaseSixtyFour)-numberOfPixels; i++ {
dest.checksum.Add(uint32(bitmap[imageAsBaseSixtyFour[i:(i+numberOfPixels)]]))
}
dest.checksumReady = true
}`
This is run in a go routine, and later on I want to do some operation much later:
for checksumsSlice[i].checksumReady == false {}
(This waits until checksumReady == true)
checksumReady is true but highlowcontainer is nil...
Is there a way to ensure that the bitmap is valid?
Thanks!
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 by tracing calculateBitSetChecksum and every read or write of checksumReady and highlowcontainer. Reproduce the concurrent access described in the issue, then verify that the bitmap is observed only after checksum computation and related state are complete, including the nil case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100