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
The current log output of the server outside verbose mode is not terribly useful as virtually everything that is related to CodeChecker is accessed through /CodeCheckerService.
For example, during normal day-to-day usage, the following logs are generated:
[INFO 2020-11-24 11:12] - 127.0.0.1:39506 -- [whisperity] POST /AdjacentParams/v6.35/CodeCheckerService
[INFO 2020-11-24 11:12] - 127.0.0.1:39512 -- [whisperity] POST /AdjacentParams/v6.35/CodeCheckerService
[INFO 2020-11-24 11:12] - 127.0.0.1:39514 -- [whisperity] POST /AdjacentParams/v6.35/CodeCheckerService
[INFO 2020-11-24 11:12] - 127.0.0.1:39518 -- [whisperity] POST /AdjacentParams/v6.35/CodeCheckerService
[INFO 2020-11-24 11:12] - 127.0.0.1:39522 -- [whisperity] POST /AdjacentParams/v6.35/CodeCheckerService
[INFO 2020-11-24 11:12] - 127.0.0.1:39526 -- [whisperity] POST /AdjacentParams/v6.35/CodeCheckerService
I have looked into the server implementation code and I agree it's not the easiest to properly refactor, however, an output similar in nature to
[INFO 2020-11-24 11:12] - 127.0.0.1:39506 -- [whisperity] POST /AdjacentParams/v6.35/CodeCheckerService@getReport
The text was updated successfully, but these errors were encountered:
The current log output of the server outside verbose mode is not terribly useful as virtually everything that is related to CodeChecker is accessed through
/CodeCheckerService
.For example, during normal day-to-day usage, the following logs are generated:
I have looked into the server implementation code and I agree it's not the easiest to properly refactor, however, an output similar in nature to
The text was updated successfully, but these errors were encountered: