After updating to 4.0 recently I started experiencing this issue.

Error: no reference found for shorthand 'origin/HEAD'; class=Reference (4); code=NotFound (-3)

Downgrading back to 3.0 doesn't show the same issue

I saw there was a PR for a similar issue that was merged in quite some time ago. Did that not make it into the new release?

Describe the issue.

It's weird, I don't seem to see any results. with strace I see that some git files are read.

~/dev
❯ gfold
There are no results to display.

gfold 0.8.0

Is this a bug report, feature request, or another type of issue?

bug

Are you using Windows, macOS, Linux, or another OS?

Linux

Are you using a pre-built binary? If not, how did you obtain gfold?

cargo install gfold

Hi, I came across your project and I liked it. It looks promising for sure. 🚀 I'm also a Rust developer and I maintain AUR packages in my spare time. So I created the following packages for the installation of gfold on Arch Linux and other distributions that support installing packages from AUR:

• gfold (builds from source)
• gfold-git (VCS/development package)

Installation can be made simply by a AUR helper such as yay. (e.g: yay -S gfold)

Feel free to update your documentation regarding to the AUR packages and installation. (I would propose a PR if requested)

Take care, orhun.

Upgrading fails via brew on macOS 12.13.1 (M1)

$ cargo --version
cargo 1.59.0

$ brew upgrade
==> Upgrading 1 outdated package:
nickgerace/nickgerace/gfold 3.0.0 -> 4.0.0
==> Downloading https://github.com/nickgerace/gfold/archive/refs/tags/4.0.0.tar.gz
Already downloaded: /Users/madeyoulook/Library/Caches/Homebrew/downloads/6cce67192febbafd684b46630662298e7cb5606c2eee8968621c887d340fbf78--gfold-4.0.0.tar.gz
==> Upgrading nickgerace/nickgerace/gfold
  3.0.0 -> 4.0.0

==> cargo install
Last 15 lines from /Users/madeyoulook/Library/Logs/Homebrew/gfold/01.cargo:
cargo
install
--locked
--root
/opt/homebrew/Cellar/gfold/4.0.0
--path
.

  Installing gfold v4.0.0 (/private/tmp/gfold-20220511-36324-uas33a/gfold-4.0.0)
    Updating crates.io index
error: failed to select a version for the requirement `libgit2-sys = "^0.13.3"`
candidate versions found which didn't match: 0.13.2+1.4.2, 0.13.1+1.4.2, 0.13.0+1.4.1, ...
location searched: crates.io index
required by package `git2 v0.14.3`
    ... which satisfies dependency `git2 = "^0"` (locked to 0.14.3) of package `gfold v4.0.0 (/private/tmp/gfold-20220511-36324-uas33a/gfold-4.0.0)`

If reporting this issue please do so at (not Homebrew/brew or Homebrew/core):
  https://github.com/nickgerace/homebrew-nickgerace/issues

Also, that last link for reporting issues does not work -- issues are turned off for that repo.

This will likely be in the README.

Link to project: https://github.com/AckslD/nvim-gfold.lua Reddit post: https://www.reddit.com/r/neovim/comments/t209wy/introducing_nvimgfoldlua/ Original comment: https://github.com/nickgerace/gfold/issues/176#issuecomment-1050675223

Great project @AcksID :)

Describe the issue.

According to the cargo workspace documentation, all packages should share a common Cargo.lock file which should be present in the workspace root.

All packages share a common Cargo.lock file which resides in the workspace root.

Also AUR packages will become non-reproducible due to this issue since --locked flag causes the build to fail. (because Cargo.lock doesn't exist in the workspace root)

==> Starting build()...
warning: profiles for the non root package will be ignored, specify profiles at the workspace root:
package:   /build/gfold/src/gfold-1.0.0/gfld/Cargo.toml
workspace: /build/gfold/src/gfold-1.0.0/Cargo.toml
    Updating crates.io index
error: the lock file /build/gfold/src/gfold-1.0.0/Cargo.lock needs to be updated but --locked was passed to prevent this
If you want to try to generate the lock file without accessing the network, use the --offline flag.
==> ERROR: A failure occurred in build().

Solution is simply removing Cargo.lock from .gitignore and pushing it.

Is this about gfold, gfld, or both?

Both, about Cargo workspaces.

Is this a bug report, feature request, or another type of issue?

Bug report.

Paste the output of the relevant application(s).

# to reproduce the build error
git clone "https://aur.archlinux.org/gfold-git"
cd gfold-git/
extra-x86_64-build

This adds a failing tests for #202. Might not be the best test case and my rust skill is not that high but hopefully it can help find out the issue :)

Really great project! :)

What do you think about having an option to output as json. This would make it easy/ier to integrate with other tools/scripts.

Hey! I came to your tool from 📝 How I Read "The Rust Programming Language".

I noticed that the binary panics on bare repositories.

➜  tmp RUST_BACKTRACE=full /Users/kyle/.cargo/bin/gfold
thread 'main' panicked at 'failed get statuses: cannot status. This operation is not allowed against bare repositories.; class=Repository (6); code=BareRepo (-8)', src/gfold.rs:71:27
stack backtrace:
   0:        0x1067e61fe - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h13e6f26430148ff2
   1:        0x1068038cc - core::fmt::write::h45a9bd04db15c24f
   2:        0x1067e3629 - std::io::Write::write_fmt::h8ae61696f13218d5
   3:        0x1067e7e75 - std::panicking::default_hook::{{closure}}::hc98fe2390b6284e5
   4:        0x1067e7bb2 - std::panicking::default_hook::h9a63cea866a4c14a
   5:        0x1067e83d5 - std::panicking::rust_panic_with_hook::h4d446ca45c8e1faa
   6:        0x1067e7fa2 - rust_begin_unwind
   7:        0x10680f1db - std::panicking::begin_panic_fmt::h0f7b83f993394bc5
   8:        0x1066fedb0 - gfold::gfold::walk_dir::h7ce7a797048a9dd9
   9:        0x1066fc1b9 - gfold::main::h9a34aaa0573dc180
  10:        0x1066fc4e6 - std::rt::lang_start::{{closure}}::h1185fef6ccb1df63
  11:        0x1067e86a9 - std::rt::lang_start_internal::hecbcda5e1a75a865
  12:        0x1066fc4d9 - main

Steps to reproduce

$ mkdir repos
$ cd repos
$ git clone --bare https://github.com/octocat/Spoon-Knife
$ gfold

• in the table rows, one could have a clickable repository url
• and of course a state against the local repo : upgradable (5 commits)

with colors, in term of importance (new version > commits > minor commit > ...)

my 2 cents, I wanted to build the same tool, and I'm surprised how compact the code is, bravo!

Primary:

• Switch to cargo workspace to replace xtask, make, etc.
• Add debug symbol stripping

Misc:

• Upgrade all packages
• Replace entries iterator with "next" due to the following PR: https://github.com/rust-lang/git2-rs/pull/854
• Remove "rustfmt.toml"

Fixes #207

As of 5c297ad, display submodule information is only included in the json display mode. It should be added to a new or existing display mode.

Previous issue: https://github.com/nickgerace/gfold/issues/177

Hi

I'm running into this on 4.0.1 with git version 2.37.0.windows.1. The stuff befor this looks good, and I can't figure out, which repo issues this, and if its related to #202

...
[2022-07-28T12:22:46Z DEBUG gfold::report] finalized report collection for repository at path: "\\\\?\\C:\\Users\\**
Error: unsupported extension name extensions.worktreeconfig; class=Repository (6)
   0: <unknown>
   1: git_trace_set
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: git_trace_set
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: BaseThreadInitThunk
  12: RtlUserThreadStart

Just thinking about how TUI mode would fit in this project. We can do some operations on the TUI as such: jump, delete, sync, fetch, copy path, rename, move, etc.

Wdyt?

Thanks for such a great tool!

Currently, it's a bit hard to use without selective mode. I still want to use fzf git repo search and jumping to dir by pressing ENTER.

atuin would be a great benchmark for this feature.

What do you think?