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

[cherry-pick] les: fix GetProofsV2 bug (#21896) #1265

Merged
merged 1 commit into from
Dec 14, 2020

Conversation

oneeman
Copy link
Contributor

@oneeman oneeman commented Dec 14, 2020

Description

Cherry pick a PR from upstream (upstream PR 21896) which fixes a possible panic in the LES server

Tested

Manually confirmed that the panic can happen without this patch, and that this patch fixes it.

Backwards compatibility

No backwards compatibility concerns.

@mergify mergify bot merged commit 85c142a into master Dec 14, 2020
@mergify mergify bot deleted the oneeman/cherry-pick-les-server-fix branch December 14, 2020 20:59
oneeman pushed a commit that referenced this pull request Dec 14, 2020
### Description

Cherry pick a PR from upstream (upstream PR 21896) which fixes a possible panic in the LES server

### Tested

Manually confirmed that the panic can happen without this patch, and that this patch fixes it.

### Backwards compatibility

No backwards compatibility concerns.
oneeman pushed a commit that referenced this pull request Dec 14, 2020
### Description

Cherry pick a PR from upstream (upstream PR 21896) which fixes a possible panic in the LES server

### Tested

Manually confirmed that the panic can happen without this patch, and that this patch fixes it.

### Backwards compatibility

No backwards compatibility concerns.
oneeman pushed a commit that referenced this pull request Dec 15, 2020
### Description

Cherry pick a PR from upstream (upstream PR 21896) which fixes a possible panic in the LES server

### Tested

Manually confirmed that the panic can happen without this patch, and that this patch fixes it.

### Backwards compatibility

No backwards compatibility concerns.
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