Matej Drobnič

Hm wait, I think this `Proceed with installation?` prompt is from pacman? Feeel free to close if this is not part of yay.

Here is the configuration that works with the old gradle-nexus-staging plugin: https://github.com/inovait/kotlinova/blob/ce0efdcdbadb4fee7aa96cc24db17142b8e04798/build.gradle.kts#L26 And here is my attempt to use new publish-plugin: https://github.com/inovait/kotlinova/blob/9cbf41ea426216430d90eedc400cb062a3088359/build.gradle.kts#L28 which failed with the "No staging repository with...

Even worse, copying a really big amount of text X11 -> WL will freeze target application

For us, we are resolving this issue by introducing the concept of "[user presence](https://github.com/inovait/kotlinova/blob/0e02ccd1a181b9d74a1ca0fc75b85b19e9acf431/core/src/commonMain/kotlin/si/inova/kotlinova/core/flow/UserPresence.kt)" to the flow. When the flow is collected, a special object is inserted into flow's `coroutineContext`...

Just wondering, isn't `force-keyframes-at-cuts` a better option? Since it would cut without leaving in any sponsor segments

Just want to mention, I've been using this patch for months now with zero issues.

Could configuration cache even be shared using remote build cache? So, in case of cache miss, first only `settings.gradle.kts` would be applied to get build cache config and then potential...

Hm, that one is tricky. This seems to be the offending error: https://android.googlesource.com/platform/frameworks/base.git/+/34d3aeaf7f5dd744f46220f7730913468256ae9c/media/java/android/media/AudioEffect.java#1092 It throws when audio effect is uninitialized. But it can only be uninitialized in two cases: *...

Yeah, can confirm `--force-keyframes-at-cuts` does not appear to do the trick. It significantly increases processing time, but corruption is still there.

#11911 is an alternative solution, but it comes with its own drawbacks. So ideally, `--force-keyframes-at-cuts` would be fixed.