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

Return posted height along dr_id on post_data_request #235

Merged
merged 1 commit into from
Dec 2, 2024

Conversation

Thomasvdam
Copy link
Member

Motivation

Allow solvers to accurately track the DR that they posted and reduce the risk of forwarding an old result.

Explanation of Changes

Updated the test utility to verify the response and forward just the dr_id so we don't have to change all the tests.

Testing

Tests still pass.

Related PRs and Issues

N.A.

@Thomasvdam Thomasvdam requested a review from a team December 2, 2024 10:00
@Thomasvdam Thomasvdam force-pushed the feat/post-dr-return-height branch from 24fe960 to 7fdbdf4 Compare December 2, 2024 10:11
Comment on lines 7 to 11
pub(crate) struct PostRequestResponse {
pub dr_id: String,
pub height: u64,
}

Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
pub(crate) struct PostRequestResponse {
pub dr_id: String,
pub height: u64,
}
pub(crate) struct PostRequestData {
pub dr_id: String,
pub height: u64,
}

@Thomasvdam Thomasvdam force-pushed the feat/post-dr-return-height branch from 7fdbdf4 to 73e6a68 Compare December 2, 2024 10:30
Copy link
Collaborator

@gluax gluax left a comment

Choose a reason for hiding this comment

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

I would prefer this struct to be in common, just so test suite can also use it, but we can move it there later.

@Thomasvdam Thomasvdam merged commit 73e6a68 into main Dec 2, 2024
2 checks passed
@Thomasvdam Thomasvdam deleted the feat/post-dr-return-height branch December 2, 2024 15:07
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.

3 participants