Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: an empty map could have been generated due to an issue in compaction #5157

Merged
merged 1 commit into from
Jun 18, 2024

Conversation

jeroiraz
Copy link
Contributor

…tion

What's being changed:

Review checklist

  • Documentation has been updated, if necessary. Link to changed documentation:
  • Chaos pipeline run or not necessary. Link to pipeline:
  • All new code is covered by tests where it is reasonable.
  • Performance tests have been run or not necessary.

@jeroiraz jeroiraz changed the title fix: an empty map could have been generated due to an issue in compaction fix: avoid empty map generation during compaction Jun 13, 2024
@jeroiraz jeroiraz changed the title fix: avoid empty map generation during compaction fix: an empty map could have been generated due to an issue in compaction Jun 13, 2024
Copy link

sonarcloud bot commented Jun 13, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@parkerduckworth parkerduckworth merged commit 6ecf439 into stable/v1.24 Jun 18, 2024
37 of 38 checks passed
@parkerduckworth parkerduckworth deleted the fix_mapcursor branch June 18, 2024 16:26
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.

None yet

2 participants