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.

Sign up for GitHub

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

Jump to bottom

Boost messages should be stored in their own log file #2976

Closed
eschoeller opened this issue Sep 26, 2019 · 3 comments
Closed

Boost messages should be stored in their own log file #2976

eschoeller opened this issue Sep 26, 2019 · 3 comments
Labels
bug Undesired behaviour resolved A fixed issue
Milestone
v1.2.7

Comments

@eschoeller
Copy link

I'd like to request that these style messages:

BOOST NOTE: Updating Local Data Id

be shifted from cacti.log to boost.log, as I feel that's a more appropriate location for them. Any objections?
@cigamit
Copy link
Member

cigamit commented Sep 26, 2019

Nope. Evening.

@cigamit cigamit changed the title [1.2.6] Boost Note messages Relocate Boost debug messages to boost debug log Sep 26, 2019
cigamit added a commit that referenced this issue Sep 26, 2019
@cigamit
Resolving Issue #2976
dff39b8 
Relocate Boost debug messages to boost debug log
@cigamit cigamit added bug Undesired behaviour resolved A fixed issue labels Sep 26, 2019
@cigamit
Copy link
Member

cigamit commented Sep 26, 2019

Done.

@cigamit cigamit closed this as completed Sep 26, 2019
@cigamit cigamit added this to the v1.2.7 milestone Sep 26, 2019
@eschoeller
Copy link
Author

Thanks!

@netniV netniV changed the title Relocate Boost debug messages to boost debug log Boost messages should be stored in their own log file Sep 28, 2019
@github-actions github-actions bot locked and limited conversation to collaborators Jun 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug Undesired behaviour resolved A fixed issue
Projects
None yet
Milestone
v1.2.7
Development

No branches or pull requests
2 participants
@cigamit @eschoeller