Add tests for the request logging

[yashrsharma44]

PRs for request logging #3361 #2849 contains some string manipulation, which might create unnecessary panic as observed in #3921

Would be nice to write tests for making sure panics do not happen.

[ashish493]

Any type of checklist for solving this issue?
Like do we have to use some tesing framework like ginkgo or like create some basic functional tests like this

func TestPanic(t *testing.T) {
    defer func() {
        if r := recover(); r == nil {
            t.Errorf("The code did not panic")
        }
    }()

    // The following is the code under test
    OtherFunctionThatPanics()
}

I'm bit confused :(

[yashrsharma44]

Like do we have to use some tesing framework like ginkgo

We could start with making simple Go-tests, no need to look for any testing framework.

We can also write up unit tests for different functions out in the logging package

• For starters, you can take a look at the grpc.go, and add unit tests for the functions that are working, would be nice to have a defined behaviour for them

[stale]

Hello 👋 Looks like there was no activity on this issue for the last two months.
Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗
If there will be no activity in the next two weeks, this issue will be closed (we can always reopen an issue if we need!). Alternatively, use remind command if you wish to be reminded at some point in future.

[stale]

Hello 👋 Looks like there was no activity on this issue for the last two months.
Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗
If there will be no activity in the next two weeks, this issue will be closed (we can always reopen an issue if we need!). Alternatively, use remind command if you wish to be reminded at some point in future.

[stale]

Closing for now as promised, let us know if you need this to be reopened! 🤗