App install: Handle invalid Git URLs better#426
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #426 +/- ##
==========================================
- Coverage 72.23% 72.22% -0.02%
==========================================
Files 18 18
Lines 1628 1631 +3
==========================================
+ Hits 1176 1178 +2
- Misses 452 453 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
c188b1d to
45f3445
Compare
7c9aa8e to
3481fe1
Compare
3481fe1 to
155061c
Compare
| elif re.match( | ||
| "fatal: Invalid object name", error_message, flags=re.IGNORECASE | ||
| ): | ||
| raise ValueError(f"Unknown commit: {self.commit}") |
There was a problem hiding this comment.
We don't know if the user was trying a specific commit, branch or tag so this error would be misleading.
|
Hi @danielhollas. Where are we at on this one? |
|
Planning to finish today hopefully, then we can make a release.
…On Mon, Apr 20, 2026, 03:44 Edan Bainglass ***@***.***> wrote:
*edan-bainglass* left a comment (aiidalab/aiidalab#426)
<#426?email_source=notifications&email_token=ACIY64J46FR522DY5ES7NXT4WWFJ5A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMRXG42TEOJUGQZKM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJNLQOJPWG33NNVSW45C7N5YGK3S7MNWGSY3L#issuecomment-4277529442>
Hi @danielhollas <https://github.com/danielhollas>. Where are we at on
this one?
—
Reply to this email directly, view it on GitHub
<#426?email_source=notifications&email_token=ACIY64J46FR522DY5ES7NXT4WWFJ5A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMRXG42TEOJUGQZKM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJNLQOJPWG33NNVSW45C7N5YGK3S7MNWGSY3L#issuecomment-4277529442>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACIY64IEIBMNOSXNLABRX5L4WWFJ5AVCNFSM6AAAAACX2AJEHSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DENZXGUZDSNBUGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
@edan-bainglass can you take a look again. Now I actually catch the exception so that the user doesn't see the horrible stacktrace from #396, which I guess was the original motivation to open the issue. Note the use of the term "git reference" because we don't know if the user meant to spell a branch, tag or a commit. EDIT: The failing tests are due the registry |
Closes #396