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
Currently the DebugInfo::write_events method stops after the most recent 25 events. This is hardcoded and possibly not ideal for users, some will want more, but it limits output when a contract has gone awry and produced thousands of events. We should provide a way to adjust it.
Note this only has to do with native testing mode, and only with debugging turned on, and can be changed without perturbing anything protocol-level. It's relatively low priority, just to help with debugging.
The text was updated successfully, but these errors were encountered:
Currently the
DebugInfo::write_events
method stops after the most recent 25 events. This is hardcoded and possibly not ideal for users, some will want more, but it limits output when a contract has gone awry and produced thousands of events. We should provide a way to adjust it.Note this only has to do with native testing mode, and only with debugging turned on, and can be changed without perturbing anything protocol-level. It's relatively low priority, just to help with debugging.
The text was updated successfully, but these errors were encountered: