-
Notifications
You must be signed in to change notification settings - Fork 10
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
Eta hangs when accessing etlas.typelead.com #12
Comments
This looks interesting. Can you wipe out e.g. if your first command is |
Thanks for your quick response. Here you go.
|
And doing a |
I don't think I was clear on that, the command that I used to clone the repository was this:
So I had to use Update So, I decided I would try this method one more time just to see what happens. I did this again and it failed like it had the previous time. Here is the output after cloning the repository and then running
I then attempted this method again by:
This time the update worked again. My guess is that when git fails to the clone the first time |
Thank you for sharing your observations in detail! Does this mean I should make This is indeed a bug, the behaviour should be both to:
|
Yes, I think that you should be using
So there must be some other changes needed in etlas to make this possible. |
That's because etlas has two types of repos: Hackage-like (index is backed by a giant tar.gz) and Git-like (index is backed by a git repo). The So another change:
Thanks a lot! |
Hello,
I am running etlas 1.0.2.0 on macOS 10.12.6 and having a problem on the first run when the configuration is first generated. The first thing etlas does is it downloads repositories which it is unable to do. I tried running both
etlas init
andetlas update
which both ran into the same problem.It gets to this point:
Eventually it will quit since it is unable to make a connection to Github. Looking at the generated configuration file it appears that it is using the wrong protocol so I switched it from http to https and then set secure to true. After running etlas this time I get this message.
Removing the repository altogether will cause an infinite loop looking for patches with the following message.
Then if I clone the Github repository myself into
~/.etlas/packages/etlas.typelead.com
it fails with a different error.I have tried both the binary from the website and building from source with the same result.
The text was updated successfully, but these errors were encountered: