The following taps are not trusted: aws/tap Homebrew is currently ignoring formulae, casks and commands from these taps because tap trust is required. Untap them with: brew untap aws/tap Trust specific formulae, casks and commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> Whole-tap trust is broader and includes all current and future formulae, casks and commands from the listed taps. Trust whole taps with: brew trust aws/tap To disable trust checks: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release. For more information, see: https://docs.brew.sh/Tap-Trust

passing non-Sendable parameter 'completionHandler' to function expecting a '@sendable' closure

passing non-Sendable parameter 'completionHandler' to function expecting a '@sendable' closure

passing non-Sendable parameter 'completionHandler' to function expecting a '@sendable' closure

'var FeedFlowKit.SuggestedFeed.description' was renamed to 'var FeedFlowKit.SuggestedFeed.description_' because of a name collision with an another declaration 'func FeedFlowKit.KotlinBase.description() -> Swift.String'. Consider resolving the conflict either by changing the name in Kotlin, or via the @ObjCName annotation. You can also suppress this warning using the 'SuppressSkieWarning.NameCollision' configuration. However using renamed declarations from Swift is not recommended because their name will change if the conflict is resolved.

'var FeedFlowKit.RssparserYoutubeItemData.description' was renamed to 'var FeedFlowKit.RssparserYoutubeItemData.description_' because of a name collision with an another declaration 'func FeedFlowKit.KotlinBase.description() -> Swift.String'. Consider resolving the conflict either by changing the name in Kotlin, or via the @ObjCName annotation. You can also suppress this warning using the 'SuppressSkieWarning.NameCollision' configuration. However using renamed declarations from Swift is not recommended because their name will change if the conflict is resolved.

'var FeedFlowKit.RssparserRssItem.description' was renamed to 'var FeedFlowKit.RssparserRssItem.description_' because of a name collision with an another declaration 'func FeedFlowKit.KotlinBase.description() -> Swift.String'. Consider resolving the conflict either by changing the name in Kotlin, or via the @ObjCName annotation. You can also suppress this warning using the 'SuppressSkieWarning.NameCollision' configuration. However using renamed declarations from Swift is not recommended because their name will change if the conflict is resolved.

'var FeedFlowKit.RssparserRssImage.description' was renamed to 'var FeedFlowKit.RssparserRssImage.description_' because of a name collision with an another declaration 'func FeedFlowKit.KotlinBase.description() -> Swift.String'. Consider resolving the conflict either by changing the name in Kotlin, or via the @ObjCName annotation. You can also suppress this warning using the 'SuppressSkieWarning.NameCollision' configuration. However using renamed declarations from Swift is not recommended because their name will change if the conflict is resolved.

'var FeedFlowKit.RssparserRssChannel.description' was renamed to 'var FeedFlowKit.RssparserRssChannel.description_' because of a name collision with an another declaration 'func FeedFlowKit.KotlinBase.description() -> Swift.String'. Consider resolving the conflict either by changing the name in Kotlin, or via the @ObjCName annotation. You can also suppress this warning using the 'SuppressSkieWarning.NameCollision' configuration. However using renamed declarations from Swift is not recommended because their name will change if the conflict is resolved.

'var FeedFlowKit.Ktor_httpHttpStatusCode.description' was renamed to 'var FeedFlowKit.Ktor_httpHttpStatusCode.description_' because of a name collision with an another declaration 'func FeedFlowKit.KotlinBase.description() -> Swift.String'. Consider resolving the conflict either by changing the name in Kotlin, or via the @ObjCName annotation. You can also suppress this warning using the 'SuppressSkieWarning.NameCollision' configuration. However using renamed declarations from Swift is not recommended because their name will change if the conflict is resolved.

The number of threads 4 is more than the number of processors 3