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

Logger: Removed configuration from final state #827

Closed
josephjclark opened this issue Nov 15, 2024 · 4 comments · Fixed by #828
Closed

Logger: Removed configuration from final state #827

josephjclark opened this issue Nov 15, 2024 · 4 comments · Fixed by #828

Comments

@josephjclark
Copy link
Collaborator

I hate this line:

Removed configuration from final state

It's a reasonably important line. It runs at the end of every step.

But when there's an error, it tends to appear before the error. Or it's the last log line we receive.

And it looks like it's the cause of a fail, rather than the effect of a step being completed.

I'm not really sure what to do about this. Logging to debug and adding a debug filter would help.

@github-project-automation github-project-automation bot moved this to New Issues in v2 Nov 15, 2024
@doc-han
Copy link
Collaborator

doc-han commented Nov 19, 2024

  1. Unable to reproduce a situation where that line is logged after an error.
  2. I get beautiful logs on CLI that helps in knowing which part of the logs shows the error.
some code
3. Maybe it's just a UI thing where lightening logs needs to also be colorful?
some code

@josephjclark
Copy link
Collaborator Author

I think a bit of context would go a long way here.

Maybe if the logs looked more like this (I'm just sketching, and on a mobile device too)

(Debug) Step complete with status: complete
(Debug) Cleaning up state. Removing keys: configuration 

In such a long, the key removal always comes after some kind of orderly job closure, so it makes a bit more sense about what is happening

@josephjclark
Copy link
Collaborator Author

Or I suppose just having the key removal line AFTER the job failed line would go a long way

@doc-han
Copy link
Collaborator

doc-han commented Nov 19, 2024

Ohkay, that makes sense.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants