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
@benhoyt and I decided that rather than monkey(patch) about with having an ActionFailed object in both Harness and Scenario and then trying to merge them when using Scenario via ops.testing, it would be better to just have the Harness object support a state attribute (always None when using with Harness).
This means that the object can be removed from Scenario (I guess re-exporting the name for backwards compatibility) and the ops._private.harness one used instead.
The text was updated successfully, but these errors were encountered:
@benhoyt and I decided that rather than monkey(patch) about with having an
ActionFailed
object in both Harness and Scenario and then trying to merge them when using Scenario viaops.testing
, it would be better to just have the Harness object support astate
attribute (alwaysNone
when using with Harness).This means that the object can be removed from Scenario (I guess re-exporting the name for backwards compatibility) and the
ops._private.harness
one used instead.The text was updated successfully, but these errors were encountered: