kubo chore: update to go-log@v2

Need review and help in the flagged items in core/corehttp/logs.go.

Closes https://github.com/ipfs/go-ipfs/issues/8753. Closes #9245

Mar 04 '22 20:03 schomatis

2022-04-07: we need to see if this has been superseded by go-libp2p work.

Apr 07 '22 16:04 BigLep

@schomatis you should also rebase on master too, a few things have changed, but AFAIK not the main blocking point.

Apr 13 '22 03:04 Jorropo

@schomatis : are you going to make the corresponding change/improvement in go-lobv2?

Apr 21 '22 14:04 BigLep

@BigLep I'm confused on exactly what those changes should be. That's why I requested an issue to be created with the scoped changes needed to land this PR (if those are indeed a blocker here; I didn't completely understood the feedback here).

Apr 21 '22 18:04 schomatis

Ok, I'll open an issue on go-log

Apr 21 '22 19:04 Jorropo

2022-04-26 conversation:

For 0.13: do nothing (in the release notes for 0.13, "if you were using log-tail for certain things, you'll need to look at the daemon input. Previously we had some output in daemon logs and some log-tail.")
For 0.14 we're going to make log-tail work as desired.

Apr 26 '22 14:04 BigLep

@BigLep Note that ipfs log tail can be fixed pretty easily, independent of the entire "switch the whole code base to log@v2". It's just the file diff https://github.com/ipfs/go-ipfs/pull/8765/files#diff-8ecc58f41eaa3971752dc974dd21fd9c1ecfdac1c15e9e9c40dc6fa4283a8d4e.

That can land in the next release if desired.

Apr 26 '22 15:04 schomatis

@Jorropo : is there an issue in https://github.com/ipfs/go-log to improve things there?

Jul 26 '22 15:07 BigLep