Skip to content
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

Fine tuning of logging levels required in classes Script and Outcome #331

Closed
martinbielmannicube opened this issue Jan 24, 2020 · 0 comments
Assignees
Labels
bug Something isn't working kernel issue for the kernel package
Milestone

Comments

@martinbielmannicube
Copy link
Contributor

The two following logs priority should lowered.

  • o.cristalise.kernel.scripting.Script - packScriptReturnValue(Device_DBCreate) - No output params defined, returnValue is NOT null but it is discarded
    should be changed to : TRACE

  • o.c.k.persistency.outcome.Outcome - getField() - 'Category' is invalid or not a single field
    should be set to : DEBUG

...in order to bring more flexibility in the log management.

@martinbielmannicube martinbielmannicube self-assigned this Jan 24, 2020
@martinbielmannicube martinbielmannicube changed the title Fine tuning of logging levels required on ActivityDef and Outcome Fine tuning of logging levels required in classes Script and Outcome Jan 24, 2020
@kovax kovax added bug Something isn't working kernel issue for the kernel package labels Jan 24, 2020
@kovax kovax added this to the 5.1.0 milestone Jan 24, 2020
kovax added a commit that referenced this issue Jan 24, 2020
…fLoggingLevelsRequiredOnActivityDefAndOutcome

#331: Tuned log levels in Outcome and Script
@kovax kovax closed this as completed Jan 24, 2020
kovax added a commit that referenced this issue Feb 21, 2020
kovax added a commit that referenced this issue Mar 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working kernel issue for the kernel package
Projects
None yet
Development

No branches or pull requests

2 participants