Update: it turned out that it didn't like the :git/tag for some reason. I removed that and put the full value in :git/sha

And that worked. Maybe there was something weird in this GitHub repo? confluentinc/kafka-streams-examples

Tags are only used to validate the sha

So if you had just the tag, that’s not allowed

Sorry, to clarify, I had both a tag and short sha

If you had the repro coords, happy to take a look

This hangs clojure -Sdeps ‘{:deps {io.github.confluentinc/kafka-streams-examples {:git/tag “v7.1.6-18” :git/sha “d1311bc”}}}’ This works clojure -Sdeps ‘{:deps {io.github.confluentinc/kafka-streams-examples {:git/sha “a3a1b4a528fb205ec86d2bf309431d45fb6d3e9d”}}}’

You can export GITLIBS_DEBUG=true to see the git commands being run

Ah it's stuck on the tag --sort=v:refname for whatever reason

Or after it anyway

The GitHub page for that repo / tag https://github.com/confluentinc/kafka-streams-examples/tree/v7.1.6-18 says that commit is not in that repo

That can happen with a fork

There are a very large number of tags in that repo, might actually be taking a very long time

I tried running the command it printed on my local terminal and it finished instantly

Well that’s weird then

When I get a chance I will look at it

Not urgent, I can work around, but I appreciate it

By the way, do you happen to know if test code should be available when using the git resolution?

Or is it only main?

Only :paths

One thing I’m considering is whether to allow git deps to publish aliases for use externally which would allow this

How does that work for a Maven project that's just hanging out on GitHub? I think I'm not quite understanding how :paths factors in there

It wouldn’t

@U0183EZCD0D this is a bug in capturing large output from the git process. I've pushed a fix, will be in the next build of the CLI. Thanks!