swiftlyfalling

@hactar: Would you mind trying the branch `feature/OPR-681_condition_improvements`, and see if it fixes this issue for you? Mutual exclusivity is now evaluated in a way that resolves a number of...

Hi, Last time I checked, there were still some false-positives that could be triggered with certain patterns of Swift code / data structures + the Memory Graph Debugger / Leaks...

All the above said, looking at the CloudKitProcedure **tests**, it looks like some of the test classes are missing `tearDown` overrides that release the tested CloudKitProcedure as part of `tearDown`....

I'm also looking into whether there's an unexpected delay related to the TimeoutObserver that is internally added to the CloudKitProcedure. Or another issue with CloudKitProcedure itself. Will respond when I...

@Utsira: You are correct, those Conditions haven't made the cut. @danthorpe might have some more thoughts as to why and whether they will be reintroduced. As for migrating custom conditions...

@gk11: Could you provide some more details about your use-case? What are you trying to achieve by overriding `cancel()`? (Some of the internal Procedure functionality is deliberately non-overridable, but there...

Ah - thanks for the reference. Please keep in mind that that example is from back in the "Operations" days, and ProcedureKit v4 has some changes. To handle cancellation, simply...

@jshier: Sure. - `.cancel()` can be called on any thread, at any time. - The Will/DidCancelObservers (and `procedureWill/DidCancel` overrides) may be called on any thread at any time. - Access...

@jshier: With all of the above said, this is something I am exploring improving in the framework itself.

@martnst: This should be fixed as part of a new Conditions PR (with many other Condition improvements). See #681, and branch `feature/OPR-681_condition_improvements`.