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

Error Cloning #2593

Closed
S4L7 opened this issue Jan 21, 2025 · 2 comments
Closed

Error Cloning #2593

S4L7 opened this issue Jan 21, 2025 · 2 comments
Labels
bug Something isn't working

Comments

@S4L7
Copy link

S4L7 commented Jan 21, 2025

Describe the bug

When attempting to clone Eliza with WSL as I've done multiple times in the past, I receive a RPC / TLS error.

Cloning into 'traderman'...
remote: Enumerating objects: 79017, done.
remote: Counting objects: 100% (353/353), done.
remote: Compressing objects: 100% (220/220), done.
error: RPC failed; curl 56 GnuTLS recv error (-110): The TLS connection was non-properly terminated.
error: 7629 bytes of body are still expected
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: fetch-pack: invalid index-pack output

To Reproduce

Using WSL, I mount my C drive using

cd /mnt/c

I then type

git clone https://github.com/elizaos/eliza.git traderman

Expected behavior

I expected the repository to be cloned to the traderman directory for further development

Screenshots

Image

Additional context

the clone starts, the directory is created initially, then as the clone fails, the directory and all files within it are removed

I'm leaning more toward a network issue - and I've already restarted my hardware multiple times

@S4L7 S4L7 added the bug Something isn't working label Jan 21, 2025
Copy link
Contributor

Hello @S4L7! Welcome to the elizaOS community. Thank you for opening your first issue; we appreciate your contribution. You are now an elizaOS contributor!

@S4L7
Copy link
Author

S4L7 commented Jan 21, 2025

Update - everything is working again now. I did nothing. I think the answer here may have been just wait a bit - and - the repository may have been being updated. Unsure, but things are working again currently.

@S4L7 S4L7 closed this as completed Jan 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant