-
-
Notifications
You must be signed in to change notification settings - Fork 851
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement Blocking Logger Mechanism #2627
Conversation
@JC-comp
Is there some sort of 'ordering' to your PR for sequencing .. as there is some 'shared' change in #2608 Please fix, so that this PR (and all your others) self compile correctly, so that when I am testing these PR's they can be tested before being implemented. |
@abraunegg |
@JC-comp The issue stems from Debian and Ubuntu LTS versions - such as Ubuntu 20.04. It's ldc package is only v1.20.1 , thus, this is the minimum version that all compilation needs to be tested against. Why? Because the distribution version of 'ldc' is used to compile the packages presented at the OpenSuSE Build Service This means, the minimum version of LDC that can be tested against against all of these, which right now is Ubuntu 20.04 which is LDC v1.20.1. Currently I test against an even lower version (v1.18.0) because of even older architectures for Raspberry Pi operating systems. So in your testing and building, you must test each PR separately, by itself, compiling against the minimum LDC version, using a script similar to the following (assuming you already know how to install 'ldc' manually, and can install v1.20.1):
When using this script, against your PR, it generates the following error:
You must make your code compatible with LDC v1.20.1 at a minimum. |
Update
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
This PR introduces a blocking logger mechanism to replace the existing polling mechanism for enhanced efficiency and resource utilization. The new blocking logger ensures that log messages are processed synchronously, eliminating the need for continuous polling.
Changes