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

Files are decoded as binary #188

Open
vjousse opened this issue Dec 5, 2024 · 3 comments
Open

Files are decoded as binary #188

vjousse opened this issue Dec 5, 2024 · 3 comments

Comments

@vjousse
Copy link

vjousse commented Dec 5, 2024

Hi,

We're trying to setup transcrypt in our team, everything works fine except for one member who gets the file content (json) as binary.

image

Some information about the versions installed on his Mac:

image
image

And the Mac version:

image

Another team member with an M2 Mac doesn't have problems.

Any idea how we could try to debug what's going on?

Thanks!

@jmurty
Copy link
Collaborator

jmurty commented Dec 5, 2024

Hi,

I haven’t seen this problem before.

I’m suspicious of the warning message after initialising transcrypt saying that “Executing command … git … timed out”

Are the encrypted files large?
And is the Homebrew-installed git version run during init of transcrypt the same as the “Apple Git-145” reported in the later screenshot?

@paulboosz
Copy link

Hi,

Are the encrypted files large?

No they are 0.4 mb

And is the Homebrew-installed git version run during init of transcrypt the same as the “Apple Git-145” reported in the later screenshot?

I updated git when troubleshooting from 2.39.3 to 2.47.1. I retried from a clean dir with the new git version 2.47.1, it failed as well.
image

I still have the [WARN] - (starship::utils): Executing command "/opt/homebrew/bin/git" timed out.
I don't have any reports about git in Console on Mac

@vjousse vjousse changed the title Files are decoded as binary on Mac Files are decoded as binary Dec 10, 2024
@vjousse
Copy link
Author

vjousse commented Dec 10, 2024

@jmurty we finally found the issue. The problem is that transcrypt doesn't fail when the password is not the good one.
We are calling transcrypt in a bash script using this command: transcrypt -y -c aes-256-cbc -p "$TRANSCRYPT_KEY"

If $TRANSCRYPT_KEY is not set for whatever reason, the command executed will be transcrypt -y -c aes-256-cbc -p "" and transcrypt is ok with that. It says The repository has been successfully configured by transcrypt. but the encrypted files are shown as binary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants