#✔ parsing command line arguments 12.7s !?

1 messages · Page 1 of 1 (latest)

frank meadow
#

What could be causing this?

delicate plinth
past lichen
# frank meadow What could be causing this?

My guess is that we're wrongly mixing the span for the time and the repo / current dir is long ? It's the Go SDK, I suppose, from your other message ? A repro would be amazing yes 🙏

gusty sierra
#

I've seen this happen when passing a Directory by argument, and the directory contains large binary files. It will seemingly hang at "parsing command line arguments" in the CLI, but IIRC if you dig into the trace you can see that it's uploading files. Past ~50-100MB it does seem to take an awfully long time, though. I've never let it finish.

It's easy to accidentally do this when passing in e.g. a local repo as content (--source .). The repo might have files that are easy to forget about because they are in the gitignore. Adding an Ignore annotation to the argument fixes the hang in that case.