"fatal: not a git repository" after installing plugin
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
cinc-auditor plugin install train-juniper
Fetching net-ssh-7.3.2.gem
Fetching ffi-1.17.4-x86_64-linux-gnu.gem
Fetching train-juniper-0.8.0.gem
fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
fatal: not a git repository: 'ext/ffi_c/libffi/.git'
fatal: not a git repository: 'ext/ffi_c/libffi/.git'
fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
train-juniper plugin, version 0.8.0, installed from rubygems.org
[earonne@tss-jump ~]$ cinc-auditor plugin list
fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
fatal: not a git repository: 'ext/ffi_c/libffi/.git'
fatal: not a git repository: 'ext/ffi_c/libffi/.git'
fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
fatal: not a git repository: 'ext/ffi_c/libffi/.git'
fatal: not a git repository: 'ext/ffi_c/libffi/.git'
fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
┌────────────────────────────────────────┬─────────┬──────────────┬─────────┬────────────────────────────────────────────────────────────────────────┐
│ Plugin Name │ Version │ Via │ ApiVer │ Description │
├────────────────────────────────────────┼─────────┼──────────────┼─────────┼────────────────────────────────────────────────────────────────────────┤
│ inspec-compliance │ 7.0.107 │ core │ 2 │ Plugin to perform operations with Chef Automate │
│ inspec-habitat │ 7.0.107 │ core │ 2 │ Plugin to create/upload habitat package │
│ inspec-init │ 7.0.107 │ core │ 2 │ Plugin for scaffolding profile, plugin or a resource │
│ inspec-license │ 7.0.107 │ core │ 2 │ Plugin to list user licenses. │
│ inspec-parallel │ 7.0.107 │ core │ 2 │ Plugin to handle parallel InSpec scan operations over multiple targets │
│ inspec-plugin-manager-cli │ 7.0.107 │ core │ 2 │ CLI plugin for InSpec │
│ inspec-reporter-html2 │ 7.0.107 │ core │ 2 │ Improved HTML reporter plugin │
│ inspec-reporter-json-min │ 7.0.107 │ core │ 2 │ Json-min json reporter plugin │
│ inspec-reporter-junit │ 7.0.107 │ core │ 2 │ JUnit XML reporter plugin │
│ inspec-sign │ 7.0.107 │ core │ 2 │ │
│ inspec-streaming-reporter-progress-bar │ 7.0.107 │ core │ 2 │ Displays a real-time progress bar and control title as output │
│ inspec-supermarket │ 7.0.107 │ core │ 0 │ │
│ train-aws │ 0.2.44 │ gem (system) │ train-1 │ AWS API Transport for Train │
│ train-habitat │ 0.2.22 │ gem (system) │ train-1 │ Habitat API Transport for Train │
│ train-juniper │ 0.8.0 │ gem (user) │ train-1 │ Train transport for Juniper Networks JunOS devices │
│ train-kubernetes │ 0.3.1 │ gem (system) │ train-1 │ Train Kubernetes │
│ train-winrm │ 0.4.3 │ gem (system) │ train-1 │ Windows WinRM API Transport for Train │
└────────────────────────────────────────┴─────────┴──────────────┴─────────┴────────────────────────────────────────────────────────────────────────┘
17 plugin(s) total
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the problem with cinc-auditor plugin install train-juniper and cinc-auditor plugin list from a directory that is not a Git repository. Trace the plugin installation and listing entry points to identify why Git commands run there; done means both commands complete without the reported errors while the plugin remains installed and listed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, ruby
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100