Skip to content

Feat: add option to disable contract interface fields - #7488

Open
aaronb-stacks wants to merge 1 commit into
stacks-network:mainfrom
aaronb-stacks:feat/disable-interface-fields
Open

Feat: add option to disable contract interface fields#7488
aaronb-stacks wants to merge 1 commit into
stacks-network:mainfrom
aaronb-stacks:feat/disable-interface-fields

Conversation

@aaronb-stacks

Copy link
Copy Markdown
Contributor

This adds the option to drop the contract interface field from event dispatcher events for people running observers that are uninterested in those fields.

@coveralls

Copy link
Copy Markdown

Coverage Report for CI Build 31034481045

Coverage increased (+0.03%) to 86.61%

Details

  • Coverage increased (+0.03%) from the base build.
  • Patch coverage: 26 of 26 lines across 6 files are fully covered (100%).
  • 137 coverage regressions across 36 files.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

137 previously-covered lines in 36 files lost coverage.

Top 10 Files by Coverage Loss Lines Losing Coverage Coverage
stacks-signer/src/client/stacks_client.rs 27 86.39%
stackslib/src/net/stackerdb/sync.rs 12 75.78%
stackslib/src/net/neighbors/comms.rs 10 77.25%
stacks-signer/src/monitoring/mod.rs 9 77.08%
stacks-signer/src/v0/signer.rs 7 87.11%
stacks-signer/src/v0/signer_state.rs 7 92.73%
stackslib/src/chainstate/nakamoto/coordinator/mod.rs 6 80.62%
stackslib/src/burnchains/bitcoin/network.rs 5 79.8%
stacks-common/src/deps_common/bitcoin/network/serialize.rs 4 51.96%
stacks-signer/src/client/stackerdb.rs 4 84.26%

Coverage Stats

Coverage Status
Relevant Lines: 232696
Covered Lines: 201537
Line Coverage: 86.61%
Coverage Strength: 19344376.34 hits per line

💛 - Coveralls

pub local_peer_seed: Option<String>,
pub miner: Option<bool>,
pub stacker: Option<bool>,
pub disable_contract_interface_in_events: Option<bool>,

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Maybe we could put this beneath an [event_publisher] or similar stanza? My gut feeling is that we're probably going to end up with a handful of similar kinds of configurations moving forward...

Or, maybe even better would be to have this on a per-observer basis, since it's likely only necessary specifically for the explorer indexer.

Thoughts?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

+1 for making this a per observer field

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.

4 participants