Skip to content

Smarter logging of semanticTokens messages #6469

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

Closed
Timmmm opened this issue Nov 4, 2020 · 2 comments
Closed

Smarter logging of semanticTokens messages #6469

Timmmm opened this issue Nov 4, 2020 · 2 comments

Comments

@Timmmm
Copy link
Contributor

Timmmm commented Nov 4, 2020

Bug #6402 happened for me again, and I have verbose logging enabled, but unfortunately it is pretty impossible to read because of messages like this:

[Trace - 3:45:47 PM] Received response 'textDocument/semanticTokens/full/delta - (15638)' in 34ms.
Result: {
    "data": [
        0,
        0,
        3,
        1,
... Followed by 100k lines of data ...

I doubt anyone is going to read that - you might want a custom Debug impl. I folded a few of those away and the next biggest causer of spam is progress messages (I got about 1500 of them in just a few seconds).

[Trace - 3:45:47 PM] Received notification '$/progress'.
Params: {
    "token": "rustAnalyzer/indexing",
    "value": {
        "kind": "report",
        "message": "47/770 (term)",
        "percentage": 6.103896103896104
    }
}
@lnicola
Copy link
Member

lnicola commented Nov 4, 2020

Those are printed by Code, not rust-analyzer. As a workaround, you can disable semantic highlighting (or post-process the trace).

@Timmmm
Copy link
Contributor Author

Timmmm commented Nov 6, 2020

Oh ok, never mind then!

@Timmmm Timmmm closed this as completed Nov 6, 2020
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