You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the formatting is conflicting with some structured log format that zap is expecting, but I have to look deeper.
Still: The log.go:44 line does not make sense to me, as this would mean the issue is on the logger creation? I am not sure if this means v2.0.7 will break other things, therefore opening this for tracking. If deemed to be go-ds-crdt specific, this can be closed.
The text was updated successfully, but these errors were encountered:
When upgrading to v2.0.7 this happens all over the place in go-ds-crdt tests.
They have a custom logger implementation that wraps this logger: https://github.com/ipfs/go-ds-crdt/blob/master/crdt_test.go#L43
I think the formatting is conflicting with some structured log format that zap is expecting, but I have to look deeper.
Still: The
log.go:44
line does not make sense to me, as this would mean the issue is on the logger creation? I am not sure if this means v2.0.7 will break other things, therefore opening this for tracking. If deemed to be go-ds-crdt specific, this can be closed.The text was updated successfully, but these errors were encountered: