Skip to content

defined BlockNumber in setNewDispute #375

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
Oct 11, 2024
Merged

Conversation

CJPotter10
Copy link
Contributor

@CJPotter10 CJPotter10 commented Oct 11, 2024

No description provided.

…renced in a function but is not set and thus always 0
@CJPotter10 CJPotter10 changed the title defined BlockNumber in setNewDispute because this field is being refe… defined BlockNumber in setNewDispute Oct 11, 2024
@brendaloya brendaloya merged commit 93f5e56 into main Oct 11, 2024
3 checks passed
@brendaloya brendaloya deleted the fix/set-blockNum-on-dispute branch October 11, 2024 19:45
github-actions bot pushed a commit that referenced this pull request Oct 11, 2024
…renced in a function but is not set and thus always 0 (#375)

(cherry picked from commit 93f5e56)
brendaloya pushed a commit that referenced this pull request Oct 11, 2024
…renced in a function but is not set and thus always 0 (#375) (#376)

(cherry picked from commit 93f5e56)

Co-authored-by: CJPotter10 <91627020+CJPotter10@users.noreply.github.com>
CJPotter10 added a commit that referenced this pull request Oct 15, 2024
…renced in a function but is not set and thus always 0 (#375)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants