Skip to content
Discussion options

You must be logged in to vote

Possible workaround: try CLI v2.4.0
Reason: we are currently investigating a performance regression in CLI v2.5.0 and up, and have not yet released a fix.

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by adas98012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants