-
Notifications
You must be signed in to change notification settings - Fork 169
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
chore: Change debug level to info as this logging is frequent in harmless cases #13400
Conversation
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
Should this even be |
...ver/src/main/java/com/vaadin/flow/server/communication/rpc/AbstractRpcInvocationHandler.java
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@TatuLund I had an another and more deep look into AbstractRpcInvocationHandler::handle
method. Changing warn
to debug
seems a fine solution, because:
- When the
node
does not exist on the server state tree, the server basically has no information why, therefore it cannot decide whether log the message and what level to choose, and what do with it in the end. - When the
node
is detached, IMO it doesn't make sense to figure out why it is detached. We can probably check if thenode
corresponds toHasValue
component, but it is a "private" case when such a warnings occur. - As Artur said, and I agree with him, these warn message doesn't give a clear understanding of what is broken or what's wrong with the caller's code. But it can be useful for development, debugging or anomaly investigation.
So in short I propose to setdebug
level and apply this patch.
...ver/src/main/java/com/vaadin/flow/server/communication/rpc/AbstractRpcInvocationHandler.java
Outdated
Show resolved
Hide resolved
...ver/src/main/java/com/vaadin/flow/server/communication/rpc/AbstractRpcInvocationHandler.java
Outdated
Show resolved
Hide resolved
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
Hi @TatuLund and @mshabarov, when i performed cherry-pick to this commit to 9.0, i have encountered the following issue. Can you take a look and pick it manually? |
…less cases (#13400) (#13798) Closes: vaadin/flow-components#1157 Co-authored-by: Tatu Lund <[email protected]>
…less cases (#13400) (#13799) Closes: vaadin/flow-components#1157 Co-authored-by: Tatu Lund <[email protected]>
…less cases (#13400) (#13799) Closes: vaadin/flow-components#1157 Co-authored-by: Tatu Lund <[email protected]>
…less cases (#13400) (#13799) Closes: vaadin/flow-components#1157 Co-authored-by: Tatu Lund <[email protected]>
Closes: vaadin/flow-components#1157