The Wayback Machine - https://web.archive.org/web/20230601071351/https://github.com/chubin/cheat.sh/issues/323
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 500 when searching for keyword #323

Closed
niksy opened this issue Jan 24, 2022 · 11 comments
Closed

Error 500 when searching for keyword #323

niksy opened this issue Jan 24, 2022 · 11 comments
Labels
waiting-for-feedback fixed, waiting for the feedback

Comments

@niksy
Copy link

niksy commented Jan 24, 2022

Internal server error is thrown everytime I try to search for keyword, e.g. curl cheat.sh/~redirect. Same thing happens on website and when using via curl.

@abitrolly

This comment has been minimized.

@niksy
Copy link
Author

niksy commented Jan 24, 2022

I was looking for keyword redirect specifically, i.e. results for either curl or redirecting standard error and output in shell.

@abitrolly
Copy link
Collaborator

Then the URL that gives 500 error should be https://cheat.sh/~redirect because curl.sh/~redirect is a different site.

@niksy
Copy link
Author

niksy commented Jan 24, 2022

Sorry, I’ve switched curl with cheat. Updated original post.

@estiens
Copy link

estiens commented Feb 8, 2022

yeah, I get a 500 error from most requests it can't quite parse it seems

chubin added a commit that referenced this issue Apr 17, 2022
* Fixes directories handling in git-based repos
* Fixes a minor bug in tldr-adapter
@chubin
Copy link
Owner

chubin commented Apr 17, 2022

Should be fixed now, please test.

@chubin chubin added the waiting-for-feedback fixed, waiting for the feedback label Apr 17, 2022
chubin added a commit that referenced this issue Apr 17, 2022
* Fixes directories handling in git-based repos
* Fixes a minor bug in tldr-adapter
@niksy
Copy link
Author

niksy commented Apr 18, 2022

@chubin it works now, but queries like /scala/~closure or /~snapshot/r still don’t work.

chubin added a commit that referenced this issue Apr 18, 2022
chubin added a commit that referenced this issue Apr 18, 2022
@chubin
Copy link
Owner

chubin commented Apr 18, 2022

Please check it again

@niksy
Copy link
Author

niksy commented Apr 19, 2022

It works now, at least it doesn’t throw 500; for example /scala/~closure doesn’t return anything.

@chubin
Copy link
Owner

chubin commented Apr 19, 2022

I suppose that it is correct in this case, but maybe we should return some "nothing found" message explicitly.
This query searches for closure in the scala cheat sheets, not on external resources, and so there are no closure occurrences there. Compare it with /scala/~loop or /scala/~function, for example

@niksy
Copy link
Author

niksy commented Apr 19, 2022

Yeah, that should probably make more sense. Closing this issue since original problem has been solved!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
waiting-for-feedback fixed, waiting for the feedback
4 participants