You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Aside from losing tags and branch heads in places like git log (see discussion post-merge in #277), I'm now running into another error:
git.exc.GitCommandError: Cmd('git') failed due to: exit code(128)
cmdline: git rm --cached -- ci_support\upload_or_check_non_existence.py
stderr: 'fatal: pathspec 'ci_support\upload_or_check_non_existence.py' did not match any files'
There's a missing period before "ci_support"; no idea though where the processing goes wrong.
Downgrading smithy to the _0 build of smithy 3.36.0 didn't fix things (neither the error, nor the tag visibility), but that didn't get rid of the new m2-* packages that _1 had dragged in (and conda install --revision <X> didn't resolve for 15min, so I gave up). However, after recreating the environment from scratch, the rerender works again. So it's the mere presence of some of the following libs that breaks things.
Long-term, I'd like to have a __git package (not necessarily virtual, just something that tells the resolver it's already available locally), which allows me not to drag in the huge git updates all the time.
The text was updated successfully, but these errors were encountered:
Aside from losing tags and branch heads in places like
git log
(see discussion post-merge in #277), I'm now running into another error:There's a missing period before "ci_support"; no idea though where the processing goes wrong.
Downgrading smithy to the
_0
build of smithy 3.36.0 didn't fix things (neither the error, nor the tag visibility), but that didn't get rid of the new m2-* packages that_1
had dragged in (andconda install --revision <X>
didn't resolve for 15min, so I gave up). However, after recreating the environment from scratch, the rerender works again. So it's the mere presence of some of the following libs that breaks things.Long-term, I'd like to have a
__git
package (not necessarily virtual, just something that tells the resolver it's already available locally), which allows me not to drag in the huge git updates all the time.The text was updated successfully, but these errors were encountered: