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
In the following code, your Project emit cachecontext twice which is not necessary and allowing emit same event twice.
// CacheContext returns a new Context with the multi-store cached and a new// EventManager. The cached context is written to the context when writeCache// is called. Note, events are automatically emitted on the parent context's// EventManager when the caller executes the write.func (cContext) CacheContext() (ccContext, writeCachefunc()) {
cms:=c.ms.CacheMultiStore()
cc=c.WithMultiStore(cms).WithEventManager(NewEventManager())
writeCache=func() {
c.EventManager().EmitEvents(cc.EventManager().Events())
cms.Write()
}
returncc, writeCache
}
The following code uses related function functions, which will cause all events in the hook to appear repeatedly. Bring risks to off-chain monitoring, especially considering that the event contains Send events
Introduction
In the following code, your Project emit cachecontext twice which is not necessary and allowing emit same event twice.
agoric-sdk/golang/cosmos/x/vlocalchain/keeper/keeper.go
Lines 224 to 239 in c596c96
The following code uses related function functions, which will cause all events in the hook to appear repeatedly. Bring risks to off-chain monitoring, especially considering that the event contains Send events
https://github.com/sagaxyz/ssc/blob/main/x/billing/keeper/hooks.go#L190
Related Refs