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
Debug events when output do not include a clear indication of which contract ID generated the event. This can get ambiguous with even small traces involving only a couple contracts. For example:
HostError
Value: Status(ContractError(5))
Debug events (newest first):
0: "Debug escalating error '' to panic"
1: "Debug contract call invocation resulted in error Status(ContractError(5))"
2: "Debug caught panic from contract function 'Symbol(add)', propagating escalated error 'Status(ContractError(5))'"
3: "Debug escalating error '' to panic"
4: "Debug incompatible signature format"
Agreed. This goes together with #681 IMO, we should just have objects kicking around for any contract ID that we can tag anything with that is contract-ID-specific.
(Possibly the object handles for contract IDs can/should be related to the ticket numbers in #132 -- if we're never rolling back object handles it might make sense to assign ticket numbers as "the next free object handle" when pushing a frame)
Debug events when output do not include a clear indication of which contract ID generated the event. This can get ambiguous with even small traces involving only a couple contracts. For example:
(This log is from #771.)
Could we include contract IDs, or truncated contract IDs in debug events?
cc @graydon
The text was updated successfully, but these errors were encountered: