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

Enhance logging system with levels and timestamps #3422

Closed
wants to merge 1 commit into from

Conversation

S1D007
Copy link

@S1D007 S1D007 commented Sep 11, 2024

  • Add new logging functions: nvm_log, nvm_debug, nvm_info, nvm_warn, nvm_error
  • Implement log levels (DEBUG, INFO, WARN, ERROR)
  • Add timestamps to log messages
  • Create nvm_run_command for logging command executions
  • Implement nvm_time_operation for timing long-running operations
  • Add nvm_log_env to log environment information
  • Update nvm function to log version and environment on start

- Add new logging functions: nvm_log, nvm_debug, nvm_info, nvm_warn, nvm_error
- Implement log levels (DEBUG, INFO, WARN, ERROR)
- Add timestamps to log messages
- Create nvm_run_command for logging command executions
- Implement nvm_time_operation for timing long-running operations
- Add nvm_log_env to log environment information
- Update nvm function to log version and environment on start
@ljharb
Copy link
Member

ljharb commented Sep 11, 2024

This is a pretty large and significant change to make without discussing first… can you elaborate on the use case and the need?

@S1D007

This comment was marked as off-topic.

@ljharb
Copy link
Member

ljharb commented Feb 3, 2025

@S1D007 can you elaborate on the use case and the need for this PR?

@S1D007
Copy link
Author

S1D007 commented Feb 3, 2025

@S1D007 can you elaborate on the use case and the need for this PR?

close this one.

@ljharb
Copy link
Member

ljharb commented Feb 3, 2025

… ok, but i'd still like to understand what motivated you to do this unsolicited work in the first place.

@ljharb ljharb closed this Feb 3, 2025
@S1D007
Copy link
Author

S1D007 commented Feb 3, 2025

… ok, but i'd still like to understand what motivated you to do this unsolicited work in the first place.

without knowing anything about the code saying explicit won't make anyone feel good. he deserves that nonchalant comment that i had given to him.

@ljharb
Copy link
Member

ljharb commented Feb 3, 2025

@S1D007 that was just a spam comment that was made on over 100 PRs, it wasn't personal and had nothing to do with you. Your response was off topic, so I hid it.

Would you answer the question from 6 months ago?

@S1D007
Copy link
Author

S1D007 commented Feb 3, 2025

@S1D007 that was just a spam comment that was made on over 100 PRs, it wasn't personal and had nothing to do with you. Your response was off topic, so I hid it.

Would you answer the question from 6 months ago?

oh god lol..

ok so for the comment you had given 6 month ago. i had just gone through the nvmsh install or setup bash file and saw few areas where enhancement can be done for further programmers and maintainer. and ofc users will have better experience if they are willing to check the code before executing it..

ps: this works still the same the code is written in better way

ans btw better is totally based on person whim

@ljharb
Copy link
Member

ljharb commented Feb 3, 2025

indeed, and for any given project, the only whims that matter wrt code structure are that project's maintainers' :-)

ftr, in order to justify the complexity of log levels, i'd want to see cases where the existing logs are noisy, but suppressing them all would hide important information.

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

Successfully merging this pull request may close these issues.

2 participants