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 messages still too noisy #174

Closed
r4nt opened this issue Apr 17, 2015 · 10 comments
Closed

Error messages still too noisy #174

r4nt opened this issue Apr 17, 2015 · 10 comments

Comments

@r4nt
Copy link

@r4nt r4nt commented Apr 17, 2015

I get complaints from a lot of users that the error message like:
REQUEST [error] Error (error) while connecting to http://127.0.0.1:38987/completions.
REQUEST [error] Error (error) while connecting to http://127.0.0.1:38987/event_notification. [26 times]
Are too noisy. Can we do something about this?

@Valloric just fyi

@Valloric

This comment has been minimized.

Copy link
Contributor

@Valloric Valloric commented Apr 17, 2015

Depending on the errors involved, this could be a client-side issue.

For event notification especially, ycmd will send back an error if the file is already being compiled. That error is completely ignorable though and shouldn't be presented to the user.

That's off the top of my head without more information about the errors.

@zhuzhongshu

This comment has been minimized.

Copy link

@zhuzhongshu zhuzhongshu commented Apr 19, 2015

Besides, ycmd will display"contacting host 127.0.0.1:xxxx" in the mode line every several seconds, which is noisy too...

@abingham

This comment has been minimized.

Copy link
Owner

@abingham abingham commented Apr 19, 2015

Yes, we can probably do something about these. I just need to find some time to look into it.

@abingham

This comment has been minimized.

Copy link
Owner

@abingham abingham commented Apr 20, 2015

@r4nt It looks like you can squash a lot of these messages by setting ycmd-request-msg-level to -1. Try that out and let me know if it works for you. This is a bit suboptimal, of course, because it might hide real errors, but that doesn't seem too likely, and it's far less of an issue than the noise problem.

@zhuzhongshu Setting the msg-level probably won't address the "contact host" messages. That seems to be buried down in the guts of the emacs http stack, but I'll see if I can figure it out.

@abingham

This comment has been minimized.

Copy link
Owner

@abingham abingham commented Apr 20, 2015

@zhuzhongshu Try setting url-show-status to nil. It looks like this prevents the "Contacting host" messages. Note that the documentation string for url-show-status seems incomplete or misleading on 24.4. See url-lazy-message if you want to see how it's really used.

@zhuzhongshu

This comment has been minimized.

Copy link

@zhuzhongshu zhuzhongshu commented Apr 20, 2015

It works! Many thanks @abingham .

@abingham

This comment has been minimized.

Copy link
Owner

@abingham abingham commented Apr 20, 2015

I've added a section to the README for this issue. I'll update it if it turns out that the advice is bad, and feel free to suggest any other additions you come up with.

@abingham

This comment has been minimized.

Copy link
Owner

@abingham abingham commented May 20, 2015

@r4nt Have you had a chance to try the ycmd-request-msg-level trick I mentioned above? If that works to your satisfaction then I'll close this out.

@r4nt

This comment has been minimized.

Copy link
Author

@r4nt r4nt commented May 20, 2015

Yep, works. Thanks!

@abingham

This comment has been minimized.

Copy link
Owner

@abingham abingham commented May 20, 2015

Thanks :)

@abingham abingham closed this May 20, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.