Wrap Logging#823
Conversation
|
@zeptin, I also found and fixed two cases of malformed logging statements: |
|
It seems Debug filtering is going to require another look before we can commit this. |
|
@zeptin, I've fixed a legacy issue with how |
src/Stratis.Bitcoin/Configuration/Logging/LoggingConfiguration.cs
Outdated
Show resolved
Hide resolved
src/Stratis.Bitcoin/Configuration/Logging/LoggingConfiguration.cs
Outdated
Show resolved
Hide resolved
|
@quantumagi did you test this branch with debug logging enabled? Does the other projects like Poa etc still do debug logging as they use the LogManager.GetCurrentClassLogger. |
|
Also there are some tests still failing. |
@fassadlr , i've completed a round of testing successfully but will be re-testing due to recent changes/simplifications. The |
|
@fassadlr , I'm still able to debug specific projects: |

https://app.clickup.com/t/1nq21qq
This PR creates a standardized wrapper over everything related to logging - i.e.:
using NLogis removed and replaced withusing Stratis.Bitcoin.Configuration.Loggingwhere needed.this.logger = LogManager.GetCurrentClassLogger();remains supported but so also the logger factory pattern - which I managed to get working correctly. The latter can be removed in a follow-up PR but in this PR it serves to keep the solution-wide changes minimal.The interesting changes are found in the
Stratis.Bitcoin.Configuration.Loggingnamespace and those mentioned in comments below. The overwhelming bulk of changes just relate to theusingstatements.