May 7, 2026
8:26 a.m.
On Thu May 7 13:26:41 2026 +0000, Nikolay Sivov wrote:
Ok, let's see how it goes in testing. It's difficult to tell just by looking at it. In principle, is it a good place to unlock on clone? Is it "safe" to unlock multiple times when same topology is queued over and over? I don't see any documented way for topology node to expose this flag, so maybe it's fine. Setting the async unlock attribute again should be a no-op. Also, according to the documentation, the attribute exists only to prevent an async transform being used without knowing what it is and how to use it.
-- https://gitlab.winehq.org/wine/wine/-/merge_requests/10606#note_139060