Log noise to do with websockets #36
Labels
No Label
bug
C:CLI
C:Crypto
C:Encoding
C:Proto
C:Types
dependencies
docker
documentation
duplicate
enhancement
go
good first issue
help wanted
high priority
in progress
invalid
javascript
low priority
medium priority
question
Status: Stale
Type: ADR
Type: Build
Type: CI
Type: Docs
Type: Tests
urgent
wontfix
Copied from Github
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cerc-io/laconicd-deprecated#36
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We see constant log output like this, under normal operating conditions:
This output is not useful and clutters the log making it hard to determine if the service is operating correctly.
Task is to stop this log output from appearing, one way or another.
Quick search of the laconicd source code shows that these messages are not coming from our code. Probably originate in a dependency. Checking...
Found it here:
https://github.com/tendermint/tendermint/blob/main/rpc/jsonrpc/server/ws_handler.go#L97
Code where the messages are generated:
https://github.com/tendermint/tendermint/blob/main/rpc/jsonrpc/server/ws_handler.go#L327
https://github.com/tendermint/tendermint/blob/main/rpc/jsonrpc/server/ws_handler.go#L97
(Can't find the code for "not stopping client; it is already stopped" yet)
Possibly here? https://github.com/tendermint/tendermint/blob/main/libs/service/service.go#L174
See also: https://github.com/evmos/ethermint/issues/1253
Resolved by rebasing to older CosmosSDK
Reports are the message persists in the latest release, re-opening.
Sample log output: