You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm unable to find documentation that covers how to properly register a module's interface within baseapp such that all message types supported by a module have their message handlers available. Is there existing documentation that details this, or alternatively existing unit tests that detail the steps that need to be taken?
Overview
As part of #18402 I'm attempting to write unit tests covering the integration of x/circuit within baseapp, including authorizing authorities to trip circuits, and actual tripping of circuits. Currently when attempting to trip circuits I run into the following error which seems to indicate that baseapp is unaware of the handler for types.MsgTripCircuitBreaker.
baseapp_test.go:864: response tx_results:<code:6 log:"no message handler found for *types.MsgTripCircuitBreaker: unknown request" codespace:"sdk" > consensus_param_updates:<> app_hash:",Bd\235\314\275\036\276!ZR\252\343\304Q\177\337\267\201\375\377\274\261^\324\306B\260j\006\275U"
I wasn't able to replicate, I cloned your branch (rangesecurity#1) and added the test you shared but it passed. Maybe the PR isn't up-to-date? Let me know
@facundomedica Apologies for the delayed response, and thank you for taking a look. I have another branch I'm working on to debug the error, additionally the no message handler message from baseapp doesn't appear to actually trigger a failure. I updated the unit test to cause a fatal error when the resposen from FinalizeBlock contains the message no message handler found, so it should now correctly display the message.
Reproduction steps:
$> git clone https://github.com/rangesecurity/cosmos-sdk
$>cd cosmos-sdk
$> git checkout debug/circuit-expiration
$> go test -v -run=TestBaseAppCircuitBreaker_TripCircuit ./...
Summary
Summary
I'm unable to find documentation that covers how to properly register a module's interface within
baseapp
such that all message types supported by a module have their message handlers available. Is there existing documentation that details this, or alternatively existing unit tests that detail the steps that need to be taken?Overview
As part of #18402 I'm attempting to write unit tests covering the integration of
x/circuit
withinbaseapp
, including authorizing authorities to trip circuits, and actual tripping of circuits. Currently when attempting to trip circuits I run into the following error which seems to indicate thatbaseapp
is unaware of the handler fortypes.MsgTripCircuitBreaker
.The test I have written is as follows
The text was updated successfully, but these errors were encountered: