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

Filter Store and forward messages if feature is not enabled #837

Merged
merged 3 commits into from
Oct 14, 2019

Conversation

sdbondi
Copy link
Member

@sdbondi sdbondi commented Oct 11, 2019

Base PR: #836

Description

  • Store and forward messages are discarded when they are not supported
    by the node
  • To implement this, tower-filter was used. However, it is not released
    yet for futures 0.3 so I've included it directly in this PR

Motivation and Context

Closes #831

How Has This Been Tested?

Unit test for working filter

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Feature refactor (No new feature or functional changes, but performance or technical debt improvements)
  • New Tests
  • Documentation

Checklist:

  • I'm merging against the development branch
  • I ran cargo-fmt --all before pushing
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.

- rust nightly-2019-10-04 (Requires new docker image build)
- futures alpha.19
- tokio alpha.6
- tower alpha2

Came across this panic in the rust compiler in a PR to follow:
rust-lang/rust#64385
@sdbondi sdbondi force-pushed the sb-filter-saf-messages branch from 8538621 to 10514c4 Compare October 11, 2019 14:10
- Store and forward messages are discarded when they are not supported
  by the node
- To implement this, tower-filter was used. However, it is not released
  yet for futures 0.3 so I've included it directly in this PR
@sdbondi sdbondi force-pushed the sb-filter-saf-messages branch from 10514c4 to f38b937 Compare October 11, 2019 14:13
CjS77
CjS77 previously approved these changes Oct 14, 2019
Copy link
Collaborator

@CjS77 CjS77 left a comment

Choose a reason for hiding this comment

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

LGTM

@sdbondi
Copy link
Member Author

sdbondi commented Oct 14, 2019

This requires a new docker image for rust nightly-2019-10-04
(see #836)

@sdbondi sdbondi force-pushed the sb-filter-saf-messages branch from 07f7ce8 to 9c0b883 Compare October 14, 2019 11:43
Copy link
Collaborator

@CjS77 CjS77 left a comment

Choose a reason for hiding this comment

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

LGTM

CjS77 added a commit that referenced this pull request Oct 14, 2019
Merge pull request #837

Updated futures-rs, tokio, tower and rust
Filter Store and forward messages if feature is not enabled
updated croaring to =0.3.9
@CjS77 CjS77 merged commit 9c0b883 into development Oct 14, 2019
@CjS77 CjS77 deleted the sb-filter-saf-messages branch October 14, 2019 11:53
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.

Ignore propagated messages, and store and forward messages if that PeerFeature is not available
2 participants