Lakectl error reporting requires more verbosity. I did something like

lakectl local clone <lakefs://abc.dev.xyz.com:8888/doclake/main>

because I was in a flow and did not pay attention to the fact that

clone

expects a path relative to the server URL in the config file or --

base-uri

. The error I got was

path URI contains invalid repository name (repo=<http://abc.dev.xyz.com|abc.dev.xyz.com>): not a valid repo URI

. Wasted quite a bit of time figuring out the mistake. Yes, I should have referred to the documentation earlier but I feel

lakectl

should show more details of what it expected or perhaps examples in the

--help

output. More importantly the clone command is very particular about trailing slashes so

lakectl local clone <lakefs://doclake/main> docs

generates

path URI missing path part: not a valid path URI

but

lakectl local clone <lakefs://doclake/main/> docs

runs fine

Hey @Farhan Ahmad ! Thanks for reporting! would you mind opening a GitHub issue?

Over here 🙂

Thanks