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

Offer more detailed logging #76

Closed
MaxKissgen opened this issue May 8, 2022 · 0 comments · Fixed by #111
Closed

Offer more detailed logging #76

MaxKissgen opened this issue May 8, 2022 · 0 comments · Fixed by #111
Assignees
Projects
Milestone

Comments

@MaxKissgen
Copy link
Contributor

MaxKissgen commented May 8, 2022

Currently the ocd service itself is only really able to log wrong requests. It would be highly beneficial to relay more information regarding which algorithm is executed and with what parameters, adding to that if it fails and why it fails.
For algorithm classes we can for example currently not use the one of the service classes because using this logger outside the class does not produce any output. Using an own logger here would however produce an own file.
General ideas on how to circumvent this would be to either have one central object/class with a logger that gets information from other objects, or to use an other logging library than las2peers built in one

@MaxKissgen MaxKissgen added this to the Next Release milestone May 8, 2022
@MaxKissgen MaxKissgen added this to To do in WebOCD via automation May 8, 2022
@beka-zhvania beka-zhvania self-assigned this Jul 3, 2022
@MaxKissgen MaxKissgen moved this from To do to In progress in WebOCD Oct 17, 2022
WebOCD automation moved this from In progress to Done Mar 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
WebOCD
  
Done
Development

Successfully merging a pull request may close this issue.

2 participants