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

Sorry, I cannot find any reasonable answer for your query. #93

Closed
josephhyatt opened this issue Jun 19, 2019 · 21 comments
Closed

Sorry, I cannot find any reasonable answer for your query. #93

josephhyatt opened this issue Jun 19, 2019 · 21 comments

Comments

@josephhyatt
Copy link

No matter what question I ask (even your example question) I keep getting "Sorry, I cannot find any reasonable answer for your query."

Example question:
how2 read file while is changing

@pgcudahy
Copy link

Same here

@amishPro
Copy link

Same here. No matter what questions it returns "Sorry, I cannot find any reasonable answer for your query." I have installed it with "sudo npm install -g how-2".

@tomhayes
Copy link

Same here!

@rnmhdn
Copy link

rnmhdn commented Jun 29, 2019

same here even with the question how2 unzip bz2 which is illustrated in the readme:))
I installed without sudo.

@martinstepanek
Copy link

Same here and because last version is 3 years old, I guess one of the APIs changed.

@LeonAlvarez
Copy link

still broken

@PaoloCifariello
Copy link
Contributor

Hi guys and thank you for letting me know about this.

I immediately thought that this was caused by https://github.com/jprichardson/node-google.
I discovered that the library successfully retrieves an HTML containing the results, but unfortunately something changed in the response format, hence results are no more correctly parsed (this should be the broken line https://github.com/jprichardson/node-google/blob/master/lib/google.js#L68)

To fix this I should probably play a bit with cheerio and the produced HTML to see if I can extract results, changing the old div.g, which is apparently no more a valid selector.

My idea would be to also include that single-file-library (which is apparently not supported anymore) in this project and, eventually, switch from requests to axios to have Promise support in addition to this fix.

Feel free to help on this if you want/can.

@tomhayes
Copy link

tomhayes commented Jul 31, 2019 via email

@VladimirMikulic
Copy link

I immediately thought that this was caused by https://github.com/jprichardson/node-google.
I discovered that the library successfully retrieves an HTML containing the results, but unfortunately something changed in the response format, hence results are no more correctly parsed (this should be the broken line https://github.com/jprichardson/node-google/blob/master/lib/google.js#L68)

To fix this I should probably play a bit with cheerio and the produced HTML to see if I can extract results, changing the old div.g, which is apparently no more a valid selector.

I've noticed that also, but since I discovered a new library that is maintained, I decided to modify it a bit to suit our needs and removed the old one.

My idea would be to also include that single-file-library (which is apparently not supported anymore) in this project and, eventually, switch from requests to axios to have Promise support in addition to this fix.

I can do it in the next PR 😄

@VladimirMikulic
Copy link

@josephhyatt @pgcudahy @tomhayes @aranmohyeddin while we wait for the PR to be processed, you can download and install how2 from my Github repo and test it.

git clone https://github.com/VladimirMikulic/how2
sudo npm i -g ./how2

Enjoy 🚀 🚀 🚀

@petRUShka
Copy link

@VladimirMikulic, could you please provide release section with downloadable tgz npm package?

Like this one from npm repository: https://registry.npmjs.org/how2/-/how2-1.7.1.tgz

It is needed to create Arch linux PKGBUILD.

@VladimirMikulic
Copy link

@petRUShka as you wished, I added a release section. Good luck with Arch BTW :)

@petRUShka
Copy link

@VladimirMikulic, thanks!

@rnmhdn
Copy link

rnmhdn commented Aug 29, 2019

@petRUShka Thank you for maintaining the PKGBUILD ;)

@petRUShka
Copy link

@aranmohyeddin, @VladimirMikulic, how2 package uses @VladimirMikulic fork right now.

@VladimirMikulic
Copy link

@petRUShka I'll keep it updated, feel free to suggest new features & report bugs.
I fixed the "b" keyboard shortcut for opening a link in the browser.
I could also publish it to the NPM registry, it would be easier to install(and keep it up to date).

@iamaziz
Copy link

iamaziz commented Sep 21, 2019

@VladimirMikulic I wanna give you two likes if GitHub allows! Big Thanks 👍🏻

@PaoloCifariello
Copy link
Contributor

PaoloCifariello commented Sep 21, 2019

@VladimirMikulic thanks a lot for suggesting google-it as new package to query Google and obtain results.
I saw you forked google-it to make some small adjustments, but I preferred to keep the "official version" as it seems to be constantly updated.

I just updated how-2 to 1.8.0 on NPM and merged in master the code using the new package.
Thanks to everybody and sorry for this loooong issue.

@VladimirMikulic
Copy link

@PaoloCifariello glad you came back. Next time when you want to go on vacation feel free to message me :)

@svscorp
Copy link

svscorp commented Sep 26, 2019

Hi @PaoloCifriello,

Thank you for returning on that. Not sure it is related to the latest fix, but strangely after update query like "how2 fly to the moon" return error. Maybe it should resolve it that way for these non-it related queries.

@rowan-schaefer
Copy link

I am now getting this error, after the AI bit has been added. Never had it back when it was only stackoverflow.

"Sorry, I cannot find any reasonable answer for your query." Has anyone else encountered this after the update?

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

Successfully merging a pull request may close this issue.