Overview
contract/src/event.rs (98 lines) was wired into the crate as a real audit module in CT-39, but there's no evident test for what happens when persisting an audit event itself fails (e.g. the event store is unreachable) — should the triggering operation (submit/revoke/transfer) still succeed, or roll back?
Tasks
Acceptance Criteria
Notes for Contributors
Comment below to be assigned.
Overview
contract/src/event.rs(98 lines) was wired into the crate as a real audit module in CT-39, but there's no evident test for what happens when persisting an audit event itself fails (e.g. the event store is unreachable) — should the triggering operation (submit/revoke/transfer) still succeed, or roll back?Tasks
Acceptance Criteria
Notes for Contributors
Comment below to be assigned.