Skip to content

fix: validate chain proposal length against chain exchange max length #942

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

Merged
merged 1 commit into from
Apr 16, 2025

Conversation

Kubuxu
Copy link
Contributor

@Kubuxu Kubuxu commented Apr 11, 2025

Otherwise the only valid value was chain exchange max length equal to
proposal chain length

Fixes #941

@Kubuxu Kubuxu force-pushed the fix/max-chain-len-check branch from c7d3bf9 to bc87486 Compare April 11, 2025 15:26
@Kubuxu Kubuxu enabled auto-merge April 11, 2025 15:44
@BigLep BigLep moved this to In review in F3 Apr 12, 2025
Otherwise the only valid value was chain exchange max length equal to
proposal chain length

Signed-off-by: Jakub Sztandera <oss@kubuxu.com>
@Kubuxu Kubuxu force-pushed the fix/max-chain-len-check branch from bc87486 to 3a52c7a Compare April 16, 2025 15:45
@Kubuxu Kubuxu added this pull request to the merge queue Apr 16, 2025
Merged via the queue into main with commit f8d3309 Apr 16, 2025
12 checks passed
@Kubuxu Kubuxu deleted the fix/max-chain-len-check branch April 16, 2025 16:19
@github-project-automation github-project-automation bot moved this from In review to Done in F3 Apr 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

Weird constraint in manifest check
2 participants