apologies if an FAQ (i did try to google this) - should :git/url work if the target sha is in a feature branch? so tools.gitlibs appears to be failing silently - situation: i see the gitlibs' "Checking out: " message, but no errors, and then when tools.deps tries to use the checkout, it fails because it's not there. i checked ~/.gitlibs manually and found the folder to be missing.
@robert-stuttaford yes. have you tried -Sforce
? I find myself needing that occasionally with git deps
-Sforce
doesn't seem to make a difference, unfortunately, thanks @borkdude
Might be something wrong with object dir - you could try rm’ing that under gitlibs
Can’t say I’ve seen this kind of problem before
maybe feature branch isn’t pushed? 🙂
should fail if sha isn’t known
i have one other hash in the folder, so it's defo succeeded at least once before. i'll scrub and retest! (feature branch defo pushed haha)
the commit hash that succeeded is on the default github branch (`develop` in our case), whereas the one that failed is in a feature branch. could it be that the git checkout it's doing isn't able to find the feature branch's commit?
Shouldn’t matter at all, I do this all the time
scrubbing and retesting yields the same results
You sure you have a commit sha and not like a tree sha or something
yes - i can visit the sha on http://github.com/org/repo/commit/SHA and i have it checked out locally
Checking out: git@github.com:Cognician/Base.git at 03c46df13f5b2a17474718530d5b9214f7ae236e
Checking out: git@github.com:Cognician/Monolith.git at 641eddbb7d909c671fdaa7b9eaba64f14bc8f73c
Error building classpath. Missing unknown 641eddbb7d909c671fdaa7b9eaba64f14bc8f73c
the first line is one that works (it's there after i run), the second line is the one that's meant to work but doesn't (not there after i run), and the third line is the downstream failure due to the missing folder.i guess the next step is to dig with tools.gitlibs at the repl!
Yeah that definitely drops down a layer
glad to know that this should work, thank you
Let me know how you make out
interestingly this resolves fine on our CI instance, but not locally :thinking_face: on the CI, i see Skipping coordinate:
with the same sha, presumably because it's already got it. of course, good old :local/root
works locally.