-
-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error message: "Could not parse OID from string ref:refs/heads/main" #1321
Labels
bug
Something isn't working
Comments
It looks like this may be related to this recent change in git: |
I think I have a fix. |
jblebrun
added a commit
to jblebrun/git-branchless
that referenced
this issue
May 22, 2024
jblebrun
added a commit
to jblebrun/git-branchless
that referenced
this issue
May 22, 2024
In git 2.45, reference transactions now support symbolic refs (see: git/git@a8ae923) To support this, this change runs the source string for MaybeZeroOid conversions through git2::Oid::hash_object rather than using `parse` directly, since `parse` into a `git2::Oid` object only supports 40 hex characters.
jblebrun
added a commit
to jblebrun/git-branchless
that referenced
this issue
May 22, 2024
In git 2.45, reference transactions now support symbolic refs (see: git/git@a8ae923) To support this, this change runs the source string for MaybeZeroOid conversions through git2::Oid::hash_object rather than using `parse` directly, since `parse` into a `git2::Oid` object only supports 40 hex characters.
jblebrun
added a commit
to jblebrun/git-branchless
that referenced
this issue
May 22, 2024
In git 2.45, reference transactions now support symbolic refs (see: git/git@a8ae923) To support this, this change runs the source string for MaybeZeroOid conversions through git2::Oid::hash_object rather than using `parse` directly, since `parse` into a `git2::Oid` object only supports 40 hex characters.
jblebrun
added a commit
to jblebrun/git-branchless
that referenced
this issue
May 22, 2024
In git 2.45, reference transactions now support symbolic refs (see: git/git@a8ae923) To support this, this change runs the source string for MaybeZeroOid conversions through git2::Oid::hash_object rather than using `parse` directly, since `parse` into a `git2::Oid` object only supports 40 hex characters.
jblebrun
added a commit
to jblebrun/git-branchless
that referenced
this issue
May 22, 2024
In git 2.45, reference transactions now support symbolic refs (see: git/git@a8ae923) To support this, this change runs the source string for MaybeZeroOid conversions through git2::Oid::hash_object rather than using `parse` directly, since `parse` into a `git2::Oid` object only supports 40 hex characters.
jblebrun
added a commit
to jblebrun/git-branchless
that referenced
this issue
May 22, 2024
In git 2.45, reference transactions now support symbolic refs (see: git/git@a8ae923) To support this, this change runs the source string for MaybeZeroOid conversions through git2::Oid::hash_object rather than using `parse` directly, since `parse` into a `git2::Oid` object only supports 40 hex characters.
jblebrun
added a commit
to jblebrun/git-branchless
that referenced
this issue
May 22, 2024
In git 2.45, reference transactions now support symbolic refs (see: git/git@a8ae923) To support this, this change runs the source string for MaybeZeroOid conversions through git2::Oid::hash_object rather than using `parse` directly, since `parse` into a `git2::Oid` object only supports 40 hex characters.
jblebrun
added a commit
to jblebrun/git-branchless
that referenced
this issue
May 22, 2024
In git 2.45, reference transactions now support symbolic refs (see: git/git@a8ae923) To support this, this change runs the source string for MaybeZeroOid conversions through git2::Oid::hash_object rather than using `parse` directly, since `parse` into a `git2::Oid` object only supports 40 hex characters.
jblebrun
added a commit
to jblebrun/git-branchless
that referenced
this issue
May 22, 2024
In git 2.45, reference transactions now support symbolic refs (see: git/git@a8ae923) To support this, this change runs the source string for MaybeZeroOid conversions through git2::Oid::hash_object rather than using `parse` directly, since `parse` into a `git2::Oid` object only supports 40 hex characters.
jblebrun
added a commit
to jblebrun/git-branchless
that referenced
this issue
May 22, 2024
In git 2.45, reference transactions now support symbolic refs (see: git/git@a8ae923) To support this, this change runs the source string for MaybeZeroOid conversions through git2::Oid::hash_object rather than using `parse` directly, since `parse` into a `git2::Oid` object only supports 40 hex characters.
jblebrun
added a commit
to jblebrun/git-branchless
that referenced
this issue
May 22, 2024
In git 2.45, reference transactions now support symbolic refs (see: git/git@a8ae923) To support this, we add a transaction reference resolver that's capable of looking up the Oid for a named reference. It requires a repository object to do this successfully. To support the functionality, a new `refname_to_id` function is added to the Repo object that calls the similarly named method on the inner repository to get the `git2::Oid` for a given reference name.
jblebrun
added a commit
to jblebrun/git-branchless
that referenced
this issue
May 22, 2024
In git 2.45, reference transactions now support symbolic refs (see: git/git@a8ae923) To support this, we add a transaction reference resolver that's capable of looking up the Oid for a named reference. It requires a repository object to do this successfully. To support the functionality, a new `refname_to_id` function is added to the Repo object that calls the similarly named method on the inner repository to get the `git2::Oid` for a given reference name.
jblebrun
added a commit
to jblebrun/git-branchless
that referenced
this issue
May 22, 2024
In git 2.45, reference transactions now support symbolic refs (see: git/git@a8ae923) To support this, we add a transaction reference resolver that's capable of looking up the Oid for a named reference. It requires a repository object to do this successfully. To support the functionality, a new `refname_to_id` function is added to the Repo object that calls the similarly named method on the inner repository to get the `git2::Oid` for a given reference name.
jblebrun
added a commit
to jblebrun/git-branchless
that referenced
this issue
May 22, 2024
In git 2.45, reference transactions now support symbolic refs (see: git/git@a8ae923) To support this, we add a transaction reference resolver that's capable of looking up the Oid for a named reference. It requires a repository object to do this successfully. To support the functionality, a new `refname_to_id` function is added to the Repo object that calls the similarly named method on the inner repository to get the `git2::Oid` for a given reference name.
jblebrun
added a commit
to jblebrun/git-branchless
that referenced
this issue
May 22, 2024
In git 2.45, reference transactions now support symbolic refs (see: git/git@a8ae923) To support this, we add a transaction reference resolver that's capable of looking up the Oid for a named reference. It requires a repository object to do this successfully. To support the functionality, a new `refname_to_id` function is added to the Repo object that calls the similarly named method on the inner repository to get the `git2::Oid` for a given reference name.
jblebrun
added a commit
to jblebrun/git-branchless
that referenced
this issue
May 22, 2024
In git 2.45, reference transactions now support symbolic refs (see: git/git@a8ae923) To support this, we add a transaction reference resolver that's capable of looking up the Oid for a named reference. It requires a repository object to do this successfully. To support the functionality, a new `refname_to_id` function is added to the Repo object that calls the similarly named method on the inner repository to get the `git2::Oid` for a given reference name.
jblebrun
added a commit
to jblebrun/git-branchless
that referenced
this issue
May 22, 2024
In git 2.45, reference transactions now support symbolic refs (see: git/git@a8ae923) To support this, we add a transaction reference resolver that's capable of looking up the Oid for a named reference. It requires a repository object to do this successfully. To support the functionality, a new `refname_to_id` function is added to the Repo object that calls the similarly named method on the inner repository to get the `git2::Oid` for a given reference name.
jblebrun
added a commit
to jblebrun/git-branchless
that referenced
this issue
May 22, 2024
In git 2.45, reference transactions now support symbolic refs (see: git/git@a8ae923) To support this, we add a transaction reference resolver that's capable of looking up the Oid for a named reference. It requires a repository object to do this successfully. To support the functionality, a new `refname_to_id` function is added to the Repo object that calls the similarly named method on the inner repository to get the `git2::Oid` for a given reference name.
jblebrun
added a commit
to jblebrun/git-branchless
that referenced
this issue
May 22, 2024
In git 2.45, reference transactions now support symbolic refs (see: git/git@a8ae923) To support this, we add a transaction reference resolver that's capable of looking up the Oid for a named reference. It requires a repository object to do this successfully. To support the functionality, a new `refname_to_id` function is added to the Repo object that calls the similarly named method on the inner repository to get the `git2::Oid` for a given reference name.
jblebrun
added a commit
to jblebrun/git-branchless
that referenced
this issue
May 23, 2024
In git 2.45, reference transactions now support symbolic refs (see: git/git@a8ae923) To support this, we add a transaction reference resolver that's capable of looking up the Oid for a named reference. It requires a repository object to do this successfully. To support the functionality, a new `refname_to_id` function is added to the Repo object that calls the similarly named method on the inner repository to get the `git2::Oid` for a given reference name.
jblebrun
added a commit
to jblebrun/git-branchless
that referenced
this issue
May 23, 2024
In git 2.45, reference transactions now support symbolic refs (see: git/git@a8ae923) To support this, we add a transaction reference resolver that's capable of looking up the Oid for a named reference. It requires a repository object to do this successfully. To support the functionality, a new `refname_to_id` function is added to the Repo object that calls the similarly named method on the inner repository to get the `git2::Oid` for a given reference name.
jblebrun
added a commit
to jblebrun/git-branchless
that referenced
this issue
May 23, 2024
In git 2.45, reference transactions now support symbolic refs (see: git/git@a8ae923) To support this, we add a transaction reference resolver that's capable of looking up the Oid for a named reference. It requires a repository object to do this successfully. To support the functionality, a new `refname_to_id` function is added to the Repo object that calls the similarly named method on the inner repository to get the `git2::Oid` for a given reference name.
jblebrun
added a commit
to jblebrun/git-branchless
that referenced
this issue
May 23, 2024
In git 2.45, reference transactions now support symbolic refs (see: git/git@a8ae923) To support this, we add a transaction reference resolver that's capable of looking up the Oid for a named reference. It requires a repository object to do this successfully. To support the functionality, a new `refname_to_id` function is added to the Repo object that calls the similarly named method on the inner repository to get the `git2::Oid` for a given reference name.
jblebrun
added a commit
to jblebrun/git-branchless
that referenced
this issue
May 23, 2024
In git 2.45, reference transactions now support symbolic refs (see: git/git@a8ae923) To support this, we add a transaction reference resolver that's capable of looking up the Oid for a named reference. It requires a repository object to do this successfully. To support the functionality, a new `refname_to_id` function is added to the Repo object that calls the similarly named method on the inner repository to get the `git2::Oid` for a given reference name.
jblebrun
added a commit
to jblebrun/git-branchless
that referenced
this issue
May 23, 2024
In git 2.45, reference transactions now support symbolic refs (see: git/git@a8ae923) To support this, we add a transaction reference resolver that's capable of looking up the Oid for a named reference. It requires a repository object to do this successfully. To support the functionality, a new `refname_to_id` function is added to the Repo object that calls the similarly named method on the inner repository to get the `git2::Oid` for a given reference name.
jblebrun
added a commit
to jblebrun/git-branchless
that referenced
this issue
May 23, 2024
In git 2.45, reference transactions now support symbolic refs (see: git/git@a8ae923) To support this, we add a transaction reference resolver that's capable of looking up the Oid for a named reference. It requires a repository object to do this successfully. To support the functionality, a new `refname_to_id` function is added to the Repo object that calls the similarly named method on the inner repository to get the `git2::Oid` for a given reference name.
jblebrun
added a commit
to jblebrun/git-branchless
that referenced
this issue
May 23, 2024
In git 2.45, reference transactions now support symbolic refs (see: git/git@a8ae923) To support this, we add a transaction reference resolver that's capable of looking up the Oid for a named reference. It requires a repository object to do this successfully. To support the functionality, a new `refname_to_id` function is added to the Repo object that calls the similarly named method on the inner repository to get the `git2::Oid` for a given reference name.
jblebrun
added a commit
to jblebrun/git-branchless
that referenced
this issue
May 23, 2024
In git 2.45, reference transactions now support symbolic refs (see: git/git@a8ae923) To support this, we add a transaction reference resolver that's capable of looking up the Oid for a named reference. It requires a repository object to do this successfully. To support the functionality, a new `refname_to_id` function is added to the Repo object that calls the similarly named method on the inner repository to get the `git2::Oid` for a given reference name.
jblebrun
added a commit
to jblebrun/git-branchless
that referenced
this issue
May 23, 2024
In git 2.45, reference transactions now support symbolic refs (see: git/git@a8ae923) To support this, we add a transaction reference resolver that's capable of looking up the Oid for a named reference. It requires a repository object to do this successfully. To support the functionality, a new `refname_to_id` function is added to the Repo object that calls the similarly named method on the inner repository to get the `git2::Oid` for a given reference name.
jblebrun
added a commit
to jblebrun/git-branchless
that referenced
this issue
May 23, 2024
In git 2.45, reference transactions now support symbolic refs (see: git/git@a8ae923) To support this, we add a transaction reference resolver that's capable of looking up the Oid for a named reference. It requires a repository object to do this successfully. To support the functionality, a new `refname_to_id` function is added to the Repo object that calls the similarly named method on the inner repository to get the `git2::Oid` for a given reference name.
jblebrun
added a commit
to jblebrun/git-branchless
that referenced
this issue
Jun 8, 2024
In git 2.45, reference transactions now support symbolic refs (see: git/git@a8ae923) To support this, we add a transaction reference resolver that's capable of looking up the Oid for a named reference. It requires a repository object to do this successfully. To support the functionality, a new `refname_to_id` function is added to the Repo object that calls the similarly named method on the inner repository to get the `git2::Oid` for a given reference name.
jblebrun
added a commit
to jblebrun/git-branchless
that referenced
this issue
Jun 8, 2024
In git 2.45, reference transactions now support symbolic refs (see: git/git@a8ae923) To support this, we add a transaction reference resolver that's capable of looking up the Oid for a named reference. It requires a repository object to do this successfully. To support the functionality, a new `refname_to_id` function is added to the Repo object that calls the similarly named method on the inner repository to get the `git2::Oid` for a given reference name.
jblebrun
added a commit
to jblebrun/git-branchless
that referenced
this issue
Jun 8, 2024
In git 2.45, reference transactions now support symbolic refs (see: git/git@a8ae923) To support this, we add a transaction reference resolver that's capable of looking up the Oid for a named reference. It requires a repository object to do this successfully. To support the functionality, a new `refname_to_id` function is added to the Repo object that calls the similarly named method on the inner repository to get the `git2::Oid` for a given reference name.
jblebrun
added a commit
to jblebrun/git-branchless
that referenced
this issue
Jun 8, 2024
In git 2.45, reference transactions now support symbolic refs (see: git/git@a8ae923) To support this, we add a transaction reference resolver that's capable of looking up the Oid for a named reference. It requires a repository object to do this successfully. To support the functionality, a new `refname_to_id` function is added to the Repo object that calls the similarly named method on the inner repository to get the `git2::Oid` for a given reference name.
jblebrun
added a commit
to jblebrun/git-branchless
that referenced
this issue
Jun 8, 2024
In git 2.45, reference transactions now support symbolic refs (see: git/git@a8ae923) To support this, we add a transaction reference resolver that's capable of looking up the Oid for a named reference. It requires a repository object to do this successfully. To support the functionality, a new `refname_to_id` function is added to the Repo object that calls the similarly named method on the inner repository to get the `git2::Oid` for a given reference name.
jblebrun
added a commit
to jblebrun/git-branchless
that referenced
this issue
Jun 10, 2024
In git 2.45, reference transactions now support symbolic refs (see: git/git@a8ae923) To support this, we add a transaction reference resolver that's capable of looking up the Oid for a named reference. It requires a repository object to do this successfully. To support the functionality, a new `refname_to_id` function is added to the Repo object that calls the similarly named method on the inner repository to get the `git2::Oid` for a given reference name.
jblebrun
added a commit
to jblebrun/git-branchless
that referenced
this issue
Jun 10, 2024
In git 2.45, reference transactions now support symbolic refs (see: git/git@a8ae923) To support this, we add a transaction reference resolver that's capable of looking up the Oid for a named reference. It requires a repository object to do this successfully. To support the functionality, a new `refname_to_id` function is added to the Repo object that calls the similarly named method on the inner repository to get the `git2::Oid` for a given reference name.
arxanas
pushed a commit
that referenced
this issue
Jun 15, 2024
In git 2.45, reference transactions now support symbolic refs (see: git/git@a8ae923) To support this, we add a transaction reference resolver that's capable of looking up the Oid for a named reference. It requires a repository object to do this successfully. To support the functionality, a new `refname_to_id` function is added to the Repo object that calls the similarly named method on the inner repository to get the `git2::Oid` for a given reference name.
Hi, Sorry if this was already planned, but since it seems to me that this was fixed more than 2 months ago, do you think it would be possible to make a new release that contains the fix? |
13 tasks
Closing as duplicate of #1388; follow there for updates. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of the bug
I've started to see an error appearing when I navigate between branches in git branchless:
It seems that it somehow gets the value
ref:refs/heads/main
in a position where a commit hash is expected.I'm still digging into this more, but figured I'd file a bug in case anyone else has any hunches about what might be happening.
So far, all I can say is that I can't find any entry in the SQLite db that contains
ref:refs/heads/main
in that position; so I'm not sure where that's being introduced.It seems that it's related to the state of the repository; even when I check out a fresh copy of the repository, this is happening. It just started happening yesterday or today, so perhaps it's somehow related to some commit metadata?
Functionally, everything still seems to work OK (it still switches tot he branch, for example).
Expected behavior
I expect the message not to appear.
Actual behavior
The message appears.
Version of
rustc
No response
Automated bug report
No response
Version of
git-branchless
0.8.0
Version of
git
2.45.1.288.patched (internal company version)
The text was updated successfully, but these errors were encountered: