Skip to content

Some languages reported as unknown even though they're suggested #32

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

Open
TeMPOraL opened this issue Jul 11, 2018 · 3 comments
Open

Some languages reported as unknown even though they're suggested #32

TeMPOraL opened this issue Jul 11, 2018 · 3 comments

Comments

@TeMPOraL
Copy link

TeMPOraL commented Jul 11, 2018

Observe:

  temporal@galactica~> curl cht.sh/lisp
  Unknown topic.
  Do you mean one of these topics may be?
  
      * lisp/ 100
      * elisp/ 89
      * alias 67

Changing the URL to cht.sh/alias correctly gives a list of examples, while lisp and elisp are always reported as unknown. My guess is, something somewhere is storing those tokens with forward slash in the name, whereas the HTTP handling code strips it out from request.

@chubin
Copy link
Owner

chubin commented Jul 11, 2018

Yes, it's true, we are experiencing too high load now, and that it the root of the problem.
We are working on it and as soon as it will be fixed, everything should work fine.

Please try, whether curl cht.sh/lisp/:list works for you.

@TeMPOraL
Copy link
Author

Yes, :list works. It returns :learn. :learn returns a Lisp guide.

Thanks, I'll keep an eye on it and play some more once the load goes down :).

@chubin
Copy link
Owner

chubin commented Jul 11, 2018

Yes, I will write about it in this issue, as soon as the problem is fixed/mitigated.

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

2 participants