-
Notifications
You must be signed in to change notification settings - Fork 223
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
ls workaround: (was Creating new project: 500 exception) #170
Comments
I got a similar error while creating a project from template i have locally
When i disable my internet and try to create the project i came across that it is trying to connect to the URL Accessing the URL through browser will return |
I'm getting a similar problem with local repos too, though the url is: Any workaround that you know of? TIA, |
I am not able to sort from where this URL is called 😞 or is there a way to disable checking for latest API. Can you please assign a bug label to this issue |
@JoyMonteiro The parameter can you check for the parameter All the best 👍 |
I had the same issue, when trying to run
The workaround @maxmithun described worked for me as well. I cloned Then I could run
without problem. |
We should catch |
Should we close the issue, since we are not using implicit.ly anymore? |
+1 |
We might need to still warn the user if it's used in a template. |
Hello,
I tried creating a new unfiltered project using the instructions in
http://unfiltered.databinder.net/Try+Unfiltered.html
It always seems to die with a 500 exception.
I then tried
g8 http://github.com/unfiltered/unfiltered-netty.g8
and it gave me a 301 "Moved Permanently" exception. I verified that that URL exists.
If I try
g8 git://github.com/unfiltered/unfiltered-netty.g8
I again get a 500 Unexpected response error.
However,
g8 n8han/giter8
works perfectly.
Any pointers as to what I'm doing wrong?
I also tried the variants
g8 softprops/unfiltered
g8 unfiltered/unfiltered-netty
as well, and again it fails with the 500 exception.
TIA,
Joy
The text was updated successfully, but these errors were encountered: