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

feat: add signer-key to synthetic pox events #4329

Merged
merged 1 commit into from
Feb 1, 2024

Conversation

zone117x
Copy link
Member

@zone117x zone117x commented Feb 1, 2024

No description provided.

Copy link

codecov bot commented Feb 1, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (f698448) 83.39% compared to head (74e3ced) 71.84%.

Additional details and impacted files
@@             Coverage Diff             @@
##             next    #4329       +/-   ##
===========================================
- Coverage   83.39%   71.84%   -11.55%     
===========================================
  Files         435      435               
  Lines      309245   309254        +9     
===========================================
- Hits       257886   222177    -35709     
- Misses      51359    87077    +35718     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Member

@jcnelson jcnelson left a comment

Choose a reason for hiding this comment

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

LGTM if CI passes

Copy link
Contributor

@hstove hstove left a comment

Choose a reason for hiding this comment

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

LGTM

}}
}})
"#,
extend_count = &args[0],
pox_addr = &args[1],
signer_key = &args.get(2).map_or("none".to_string(), |v| v.to_string()),
Copy link
Contributor

@hstove hstove Feb 1, 2024

Choose a reason for hiding this comment

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

Suggested change
signer_key = &args.get(2).map_or("none".to_string(), |v| v.to_string()),
signer_key = &args.get(2).unwrap_or(&Value::none()),

I'm still learning Rust, but my understanding is that to_string() is just calling the fmt::Display method, so to_string isn't necessary.

Copy link
Member Author

Choose a reason for hiding this comment

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

unwrap_or wants the same type for both expressions

@zone117x zone117x merged commit a7c5984 into next Feb 1, 2024
1 of 2 checks passed
}}
}}
"#,
lock_amount = &args[0],
lock_period = &args[3],
pox_addr = &args[1],
start_burn_height = &args[2],
signer_key = &args.get(3).map_or("none".to_string(), |v| v.to_string()),
Copy link
Contributor

Choose a reason for hiding this comment

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

Ah we missed this - needs to be .get(4)

@blockstack-devops
Copy link
Contributor

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@stacks-network stacks-network locked as resolved and limited conversation to collaborators Nov 6, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants