Skip to content
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

git-stack Crash Report: crashes on brand new repo without commits #367

Open
2 tasks done
rdelfin opened this issue Sep 11, 2024 · 0 comments
Open
2 tasks done

git-stack Crash Report: crashes on brand new repo without commits #367

rdelfin opened this issue Sep 11, 2024 · 0 comments
Labels
bug Not as expected

Comments

@rdelfin
Copy link

rdelfin commented Sep 11, 2024

Please complete the following tasks

  • I have searched the discussions
  • I have searched the existing issues

Description

While running git stack on a brand new Rust repo I generated with cargo generate, I ran into a crash. I was requested to report it here. Crash report contents:

"name" = "git-stack"
"operating_system" = "Red Hat Enterprise Linux 8.6.0 (Ootpa) [64-bit]"
"crate_version" = "0.10.17"
"explanation" = """
Panic occurred in file '/home/cloud-user/.cargo/registry/src/index.crates.io-6f17d22bba15001f/git-stack-0.10.17/src/legacy/git/repo.rs' at line 253
"""
"cause" = "Unexpected git2 error: reference 'refs/heads/main' not found; class=Reference (4); code=UnbornBranch (-9)"
"method" = "Panic"
"backtrace" = """

   0: 0x55b2af7d3a8e - git_stack::legacy::git::repo::GitRepo::head_commit::h68e6578159870b7a
   1: 0x55b2af6cb08a - git_stack::stack::stack::h437fe59465fe2a9c
   2: 0x55b2af70c611 - git_stack::args::Args::exec::hf406dffb710dc14f
   3: 0x55b2af73531a - git_stack::run::h05165c2c27e53595
   4: 0x55b2af734b2f - git_stack::main::h934a16b87272b086
   5: 0x55b2af740913 - std::sys_common::backtrace::__rust_begin_short_backtrace::h701eeee91fd97b07
   6: 0x55b2af71c509 - std::rt::lang_start::{{closure}}::h00b26efd220aed8b
   7: 0x55b2afa4184d - std::rt::lang_start_internal::hcee5ed89fc25829a
   8: 0x55b2af735f15 - main
   9: 0x7f50b4459d85 - __libc_start_main
  10: 0x55b2af6b866e - _start
  11:        0x0 - <unresolved>"""

Version

git-stack 0.10.17

Steps to reproduce

  • Create a new repo with the command cargo generate https://github.com/aya-rs/aya-template
  • Fill out the details .
  • Run git stack

Actual Behaviour

Error shows up saying there was a crash

Expected Behaviour

Either an error saying the repo is empty, or a blank stack page

Debug Output

$ git stack -vv
[TRACE git_stack::stack] Initializing
[TRACE git_stack::config] Loading gitconfig
[TRACE git_stack::config] Loading /home/cloud-user/code/rust/aya-test/.gitconfig
[TRACE git_stack::config] Loading /home/cloud-user/code/rust/aya-test/.git/config
[TRACE git_stack::stack] Ignoring `auto-fixup=move` without an explicit `--rebase`
[TRACE git_stack::stack] Ignoring `auto-repair=true` without an explicit `--rebase`
[DEBUG globset] built glob set; 0 literals, 4 basenames, 0 extensions, 0 prefixes, 0 suffixes, 0 required extensions, 0 regexes
[TRACE git_stack::legacy::git::repo] Loading local branches
[TRACE os_info::imp] linux::current_platform is called
[TRACE os_info::imp::lsb_release] lsb_release command returned Output { status: ExitStatus(unix_wait_status(0)), stdout: "LSB Version:\t:core-4.1-amd64:core-4.1-noarch\nDistributor ID:\tRedHatEnterprise\nDescription:\tRed Hat Enterprise Linux release 8.6 (Ootpa)\nRelease:\t8.6\nCodename:\tOotpa\n", stderr: "" }
[TRACE os_info::imp::lsb_release] Trying to parse "LSB Version:\t:core-4.1-amd64:core-4.1-noarch\nDistributor ID:\tRedHatEnterprise\nDescription:\tRed Hat Enterprise Linux release 8.6 (Ootpa)\nRelease:\t8.6\nCodename:\tOotpa\n"
[TRACE os_info::imp::lsb_release] Parsed as 'Some("RedHatEnterprise")' distribution and 'Some("8.6")' version
[TRACE os_info::imp] Returning Info { os_type: RedHatEnterprise, version: Semantic(8, 6, 0), edition: None, codename: Some("Ootpa"), bitness: X64, architecture: Some("x86_64") }
Well, this is embarrassing.

git-stack had a problem and crashed. To help us diagnose the problem you can send us a crash report.

We have generated a report file at "/tmp/report-d65cc55b-3529-4980-b1fc-f47bbfb0ac5f.toml". Submit an issue or email with the subject of "git-stack Crash Report" and include the report as an attachment.


We take privacy seriously, and do not perform any automated error collection. In order to improve the software, we rely on people to submit reports.

Thank you kindly!
@rdelfin rdelfin added the bug Not as expected label Sep 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Not as expected
Projects
None yet
Development

No branches or pull requests

1 participant