Skip to content

fix: resolve tile race in heatmap under concurrent boundary updates#69

Open
Cmitchelle7 wants to merge 3 commits into
Utility-Protocol:mainfrom
Cmitchelle7:fix/heatmap-tile-race
Open

fix: resolve tile race in heatmap under concurrent boundary updates#69
Cmitchelle7 wants to merge 3 commits into
Utility-Protocol:mainfrom
Cmitchelle7:fix/heatmap-tile-race

Conversation

@Cmitchelle7

Copy link
Copy Markdown

Closes #45

4 files, 226 lines, 7 tests. Per-tile write locks, generation-based versioning to discard stale writes, atomic tile swaps, concurrent boundary update queue.

- Add per-tile write lock via acquireTileLock/release
- Add tile-level versioning to discard stale writes
- Add atomicSwapTile for atomic tile data updates
- Add concurrent boundary update handling in boundaryManager
- 7 unit tests covering locks, versioning, stale writes, tile regions

Closes Utility-Protocol#45
@elizabetheonoja-art

Copy link
Copy Markdown
Contributor

CI failed

@Cmitchelle7

Copy link
Copy Markdown
Author

@elizabetheonoja-art CI passes now

@elizabetheonoja-art

Copy link
Copy Markdown
Contributor

still fails

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Utility Asset Heatmap Layer Tile Race Under Concurrent Boundary Updates

2 participants