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

refactor(torture): use OrdMap to track the state #701

Merged
merged 1 commit into from
Jan 22, 2025

Conversation

gabriele-0201
Copy link
Contributor

No description provided.

@gabriele-0201 gabriele-0201 marked this pull request as ready for review January 17, 2025 17:20
@gabriele-0201 gabriele-0201 force-pushed the gm_torture_workload_state_back_to_ord_map branch from 6270d32 to 51ef2e0 Compare January 17, 2025 17:41
@gabriele-0201 gabriele-0201 force-pushed the gm_torture_sample_after_commit branch from 9adaa35 to 28037e3 Compare January 20, 2025 08:52
@gabriele-0201 gabriele-0201 force-pushed the gm_torture_workload_state_back_to_ord_map branch from 51ef2e0 to 7d8599d Compare January 20, 2025 08:52
@pepyakin pepyakin force-pushed the gm_torture_sample_after_commit branch from 28037e3 to 6fc7ac0 Compare January 20, 2025 15:28
@pepyakin pepyakin force-pushed the gm_torture_workload_state_back_to_ord_map branch from 7d8599d to bacfdd6 Compare January 20, 2025 15:28
@pepyakin pepyakin force-pushed the gm_torture_sample_after_commit branch from 6fc7ac0 to 1763dda Compare January 20, 2025 15:40
@pepyakin pepyakin force-pushed the gm_torture_workload_state_back_to_ord_map branch from bacfdd6 to 2cc1b70 Compare January 20, 2025 15:41
@gabriele-0201 gabriele-0201 force-pushed the gm_torture_sample_after_commit branch from 1763dda to a3c5384 Compare January 20, 2025 16:16
@gabriele-0201 gabriele-0201 force-pushed the gm_torture_workload_state_back_to_ord_map branch from 2cc1b70 to 3bbea42 Compare January 20, 2025 16:18
@pepyakin pepyakin force-pushed the gm_torture_sample_after_commit branch 2 times, most recently from 2b03934 to 323a7ba Compare January 20, 2025 16:49
@pepyakin pepyakin force-pushed the gm_torture_workload_state_back_to_ord_map branch from 3bbea42 to 3eef3cc Compare January 20, 2025 16:49
if self.mentions.is_empty() || self.rng.gen_bool(self.biases.new_key) {
let mut key = [0; 32];
let mut key = [0; 32];
if !self.committed.state.is_empty() && self.rng.gen_bool(self.biases.delete) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why don't we want to attempt a removal on an empty state?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To avoid deleting non-existing keys!

But now that I'm thinking about it, do we really not want to attempt to delete non-existing keys?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, exactly.

Base automatically changed from gm_torture_sample_after_commit to master January 21, 2025 08:46
Copy link
Contributor

pepyakin commented Jan 22, 2025

Merge activity

  • Jan 22, 12:40 PM EST: A user started a stack merge that includes this pull request via Graphite.
  • Jan 22, 12:40 PM EST: A user merged this pull request with Graphite.

@pepyakin pepyakin merged commit 5dfe11e into master Jan 22, 2025
8 checks passed
@pepyakin pepyakin deleted the gm_torture_workload_state_back_to_ord_map branch January 22, 2025 17:40
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.

2 participants