celestiaorg
bug: bitswap log severity as ERROR is confusing for users
When running light node on v0.18.2-mocha, I observe a flood of logs:
2024-10-08T14:38:50.290-0400 ERROR shwap/bitswap bitswap/block_fetch.go:190hasher: no unmarshallers registered for bagipaamr6aaqyaaaaaaaak6uuyaauaaq
While the log can be ignored and is non-critical, it is confusing and worrisome to users who see "ERROR" repeatedly in their logs.
The error message should say "INFO" if this is not in fact an "ERROR"
https://github.com/user-attachments/assets/ced9c237-5988-41dd-809e-02ec10c1bc54
The good news are. I've been running a version of node over the weekend with none of those logs addressing the root issue. We can expect it to come around next week.
There are duplicate messages being requested and every duplicate spawns a log.
Hello,
I'd love to help out with this issue if it's still up for grabs. It looks like the log level should just be adjusted from "ERROR" to "INFO" to avoid spooking users with non-critical messages.
Happy to work on it and follow any contribution guidelines. Let me know if I can pick this up!
