Describe the bug
Right now MempoolFilter is supposed to collect the hashes of the pending transactions which are received by the message pool, instead it is collecting the hashes of the messages present in the latest tipset (that are already part of the chain), through the EventsFilter which is what the TipsetFilter suppose to do.
Check how the MempoolFilter collects the hashes here
Expected behaviour
MempoolFilter should only return the hashes of the messages which were added to the message pool:
- Only return the
Added messages through the filter
- Ignore the messages which were
Removed from the message pool
There is a a test for the API, but it waits for sometimes after sending transaction which obviously get include in the next tipset and hence MempoolFilter gets the latest tipset and returns the hashes.
Screenshots
Environment (please complete the following information):
- OS:
- Branch/commit:
main branch
- Hardware
Other information and links
Describe the bug
Right now
MempoolFilteris supposed to collect the hashes of thepending transactionswhich are received by the message pool, instead it is collecting the hashes of the messages present in the latest tipset (that are already part of the chain), through theEventsFilterwhich is what theTipsetFiltersuppose to do.Check how the
MempoolFiltercollects the hashes hereExpected behaviour
MempoolFiltershould only return the hashes of the messages which were added to the message pool:Addedmessages through the filterRemovedfrom the message poolThere is a a test for the API, but it waits for sometimes after sending transaction which obviously get include in the next tipset and hence
MempoolFiltergets the latest tipset and returns the hashes.Screenshots
Environment (please complete the following information):
main branchOther information and links