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

[Merged by Bors] - Ban and unban peers at the swarm level #3653

Conversation

divagant-martian
Copy link
Collaborator

@divagant-martian divagant-martian commented Oct 24, 2022

Issue Addressed

I missed this from #3491. peers were being banned at the behaviour level only. The identify errors are explained by this as well

Proposed Changes

Add banning and unbanning

Additional Info

Befor,e having tests that catch this was hard because the swarm was outside the behaviour. We could now have tests that prevent something like this in the future

@AgeManning
Copy link
Member

bors r+

bors bot pushed a commit that referenced this pull request Oct 24, 2022
## Issue Addressed

I missed this from #3491. peers were being banned at the behaviour level only. The identify errors are explained by this as well

## Proposed Changes

Add banning and unbanning 

## Additional Info

Befor,e having tests that catch this was hard because the swarm was outside the behaviour. We could now have tests that prevent something like this in the future
@michaelsproul michaelsproul added ready-for-merge This PR is ready to merge. v3.2.0 Minor release following v3.1.2 labels Oct 24, 2022
@bors bors bot changed the title Ban and unban peers at the swarm level [Merged by Bors] - Ban and unban peers at the swarm level Oct 25, 2022
@bors bors bot closed this Oct 25, 2022
bors bot pushed a commit that referenced this pull request Oct 25, 2022
## Issue Addressed

NA

## Proposed Changes

Bump version to `v3.2.0`

## Additional Info

- ~~Blocked on #3597~~
- ~~Blocked on #3645~~
- ~~Blocked on #3653~~
- ~~Requires additional testing~~
bors bot pushed a commit that referenced this pull request Oct 25, 2022
## Issue Addressed

NA

## Proposed Changes

Bump version to `v3.2.0`

## Additional Info

- ~~Blocked on #3597~~
- ~~Blocked on #3645~~
- ~~Blocked on #3653~~
- ~~Requires additional testing~~
bors bot pushed a commit that referenced this pull request Oct 25, 2022
## Issue Addressed

NA

## Proposed Changes

Bump version to `v3.2.0`

## Additional Info

- ~~Blocked on #3597~~
- ~~Blocked on #3645~~
- ~~Blocked on #3653~~
- ~~Requires additional testing~~
macladson pushed a commit to macladson/lighthouse that referenced this pull request Jan 5, 2023
## Issue Addressed

I missed this from sigp#3491. peers were being banned at the behaviour level only. The identify errors are explained by this as well

## Proposed Changes

Add banning and unbanning 

## Additional Info

Befor,e having tests that catch this was hard because the swarm was outside the behaviour. We could now have tests that prevent something like this in the future
macladson pushed a commit to macladson/lighthouse that referenced this pull request Jan 5, 2023
## Issue Addressed

NA

## Proposed Changes

Bump version to `v3.2.0`

## Additional Info

- ~~Blocked on sigp#3597~~
- ~~Blocked on sigp#3645~~
- ~~Blocked on sigp#3653~~
- ~~Requires additional testing~~
Woodpile37 pushed a commit to Woodpile37/lighthouse that referenced this pull request Jan 6, 2024
## Issue Addressed

I missed this from sigp#3491. peers were being banned at the behaviour level only. The identify errors are explained by this as well

## Proposed Changes

Add banning and unbanning 

## Additional Info

Befor,e having tests that catch this was hard because the swarm was outside the behaviour. We could now have tests that prevent something like this in the future
Woodpile37 pushed a commit to Woodpile37/lighthouse that referenced this pull request Jan 6, 2024
## Issue Addressed

NA

## Proposed Changes

Bump version to `v3.2.0`

## Additional Info

- ~~Blocked on sigp#3597~~
- ~~Blocked on sigp#3645~~
- ~~Blocked on sigp#3653~~
- ~~Requires additional testing~~
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-for-merge This PR is ready to merge. v3.2.0 Minor release following v3.1.2
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants