RoaringBitmap / RoaringBitmap/roaring

How can you tell when a bitmap is ready to be read from?

Open
#251 1 comment 0 reactions 0 assignees View on GitHub

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.