-
Notifications
You must be signed in to change notification settings - Fork 15
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
Logrevision #38
Logrevision #38
Conversation
standard info levels (DEBUG, INFO, WARNING, ERROR, CRITICAL)
Can you create this request new an merge against the testing branch? I think it would be better. Changes can be testet without harming the master branch. |
I did. |
Merged :) |
When testing is stable, we can merge it into master and create a new
testing.
Am 11.02.2021 um 15:21 schrieb segaura:
…
I did.
Long better, thank you.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#38 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC2I5HHTA234XWDVDFKZEJ3S6PRWPANCNFSM4XO4GDTA>.
|
Cool, how test is managed? |
I don't think that unit tests make sense. The project is too smal for
this, too less contribution.
And now, with vannis new project, it will be a dead project soon.
To test it, I would do a "git clone2 on the testing branch and install
it via install.sh
Regards
Daniel
Am 11.02.2021 um 17:03 schrieb segaura:
…
Cool, how test is managed?
I ask both to contribute to actual test, both for a possible revision,
introducing unit tests, mock and so on.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#38 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC2I5HHSY43C6MP7SVX3FYTS6P5TJANCNFSM4XO4GDTA>.
|
:-o Can you provide me a link to that new project you mentioned? I'm using your project and I'm quite happy with it. I was glad to see the new contributions. |
It is at the very first beginning. There isn't a hompage etc. et the moment.
We'll see.....
Am 11.02.2021 um 18:25 schrieb martinbischofff:
…
And now, with vannis new project, it will be a dead project soon.
:-o Can you provide me a link to that new project you mentioned? I'm
using your project and I'm quite happy with it. I was glad to see the
new contributions.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#38 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC2I5HE5JYA6GEGNEV5MY73S6QHIFANCNFSM4XO4GDTA>.
|
Closes #37
NOTE: this pull request is about log, so it spreads over most of the python files, I am not able to test everything (e.g. openhub driver, HPSUD mode) so more peer inspection or peer test is needed
This pull request removes the printd() method
as it can be seen it has different problems:
To obtain printd() flexibility, a single logger is instructed to use:
FileHandler
when -g option requires to save log to fileStreamHandler
for default behavious when log is written to stdoutNullHandler
when no log has to be written due to "HPSUD mode"This "one-only-logger" approach enable all the log to use the same global settings for LOG LEVEL.
Having an effetive LOG LEVEL enables to change it via cli option, the
--log_level
has been introduced for this.A single unique formatter is defined in advance.
Two info log line were added as proof of concept, they are one for loading of command definitions JSON file and the other for loading of command trasnlations CSV file.
Default level has been left as-is: ERROR.
In addition to log revision this pull request includes:
(readonly)
" suffix is attached ...and this is because there are long more writable command than there are readonly commandMany things can be further improved, for instance: