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

Feat/message type filters and improving message parsing #50

Merged

Conversation

pharr117
Copy link
Collaborator

@pharr117 pharr117 commented Jan 2, 2024

Adds the following:

  1. A way to filter TX message indexing by configuration files. Adds this into the workflow for TX parsing to skip indexing message types by type URL string or regex
  2. Add better decoding handling of TXes in app to allow getting to the raw Type URL without error
  3. If the message fails decoding but is filtered out, we skip message parsing and do not raise decoding errors

…ms to skip TXs that are not of interest. Use this to ignore in-app proto decode errors and allow indexing other TXes if the failed-to-decode txes would be ignored anyway
This was linked to issues Jan 2, 2024
@pharr117 pharr117 merged commit 7b44d8e into main Jan 2, 2024
4 checks passed
@pharr117 pharr117 deleted the feat/message-type-filters-and-improving-message-parsing branch January 2, 2024 03:14
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.

Implement Message model indexing Improve Transaction model indexing
1 participant