cryptomator / cryptomator/cryptomator
Cannot clone git repo in a vault
- Dominant language
- Java
- Stars
- 16.1k
- Forks
- 1.5k
- Avg merge
- 2d 45m
- Merged PRs (30d)
- 1
Description
### Please agree to the following
- [X] I have searched [existing issues](https://github.com/cryptomator/cryptomator/issues?q=) for duplicates
- [X] I agree to follow this project's [Code of Conduct](https://github.com/cryptomator/cryptomator/blob/develop/.github/CODE_OF_CONDUCT.md)
### Summary
Cannot clone git repo in a vault
### What software is involved?
- Operating System: Mac OS 13.3.1
- Cryptomator: 1.8.0 dmg-4440 installed via brew with commands:
brew tap macos-fuse-t/homebrew-cask
brew install fuse-t
brew install fuse-t-sshfs
brew install cryptomator
### Volume Type
None
### Steps to Reproduce
Volume Type: automatic (not sure how to check which is actually in use?)
Clone a repo (newly created with just the readme inside) into a vault
### Expected Behavior
git clone should work
### Actual Behavior
git throws error when cloning:
...
Receiving objects: 100% (3/3), done.
fatal: bad object
fatal: remote did not send all necessary objects
### Reproducibility
Always
### Relevant Log Output
_No response_
### Anything else?
_No response_
Contributor guide
Research direction
Start by reproducing the failure with Cryptomator 1.8.0 on macOS 13.3.1 using the reported Homebrew FUSE-T setup, an automatically configured vault, and a newly created repository. Compare the git clone output with a successful clone outside the vault; done means cloning completes without “bad object” or “remote did not send all necessary objects” errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, java, macos
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100