The "requestId" could be generated before "checkAuth" is called
Open
- Dominant language
- Rust
- Stars
- 20.8k
- Forks
- 2.1k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 181
Description
The `checkAuth` function is called right at the beginning when Cube starts to handle a request. Because of that, I use it to print the first log message about the incoming request.
But the 'requestId' is not set in the `request` object that is given to `checkAuth`. So it is difficult to link the first log message with the subsequent log messages that already contain a requestId.
Couldn't the 'requestId' be set on the request before `checkAuth` is invoked?
Contributor guide
Assessment
This issue has not been assessed yet.