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

Changed the way specific_log_level flag works in the Logging Configuration #1769

Merged

Conversation

DhruvSondhi
Copy link
Contributor

The current implementation didn't cater to a bug that I have encountered recently. This PR aims to implement the functionality such that we are able to set the specific flag default value in the debug sub section of the tardis_config.yml.

Description

Motivation and context

How has this been tested?

  • Testing pipeline.
  • Other.

Type of change

  • Bug fix.
  • New feature.
  • Breaking change.
  • None of the above.

Checklist

  • My change requires a change to the documentation.
    • I have updated the documentation accordingly.
    • (optional) I have built the documentation on my fork following the instructions.
  • I have assigned and requested two reviewers for this pull request.

@tardis-bot
Copy link
Contributor

tardis-bot commented Aug 4, 2021

Before a pull request is accepted, it must meet the following criteria:

  • Is the necessary information provided?
  • Is this a duplicate PR?
    • If a new PR is clearly a duplicate, ask how this PR is different from the original PR?
    • If this PR is about to be merged, close the original PR with a link to this new PR that solved the issue.
  • Does it pass existing tests and are new tests provided if required?
    • The test coverage should not decrease, and for new features should be close to 100%.
  • Is the code tidy?
    • No unnecessary print lines or code comments.

tardis/io/logger/logger.py Outdated Show resolved Hide resolved
tardis/io/logger/logger.py Outdated Show resolved Hide resolved
@codecov
Copy link

codecov bot commented Aug 4, 2021

Codecov Report

Merging #1769 (24c128e) into master (575002c) will increase coverage by 0.03%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #1769      +/-   ##
==========================================
+ Coverage   58.42%   58.45%   +0.03%     
==========================================
  Files          66       66              
  Lines        6684     6687       +3     
==========================================
+ Hits         3905     3909       +4     
+ Misses       2779     2778       -1     
Impacted Files Coverage Δ
tardis/tardis/io/logger/logger.py 93.75% <0.00%> (+1.94%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 575002c...24c128e. Read the comment docs.

@DhruvSondhi DhruvSondhi force-pushed the specific_log_debug_logic_change branch from 28f377d to 79291e7 Compare August 9, 2021 06:24
@DhruvSondhi DhruvSondhi marked this pull request as draft August 9, 2021 11:58
@DhruvSondhi DhruvSondhi changed the title Changed the way specific flag works in the Logging Configuration Changed the way specific_log_level flag works in the Logging Configuration Aug 9, 2021
@DhruvSondhi DhruvSondhi marked this pull request as ready for review August 13, 2021 13:27
@DhruvSondhi DhruvSondhi force-pushed the specific_log_debug_logic_change branch from 5e3d952 to 7dc8ed6 Compare August 13, 2021 13:35
@andrewfullard
Copy link
Contributor

Can you write up the bug that this fixes into an issue so we know what is being fixed?

@DhruvSondhi DhruvSondhi force-pushed the specific_log_debug_logic_change branch from 21ad1a0 to 24c128e Compare August 21, 2021 07:40
@wkerzendorf wkerzendorf merged commit a76aa3d into tardis-sn:master Sep 9, 2021
atharva-2001 pushed a commit to atharva-2001/tardis that referenced this pull request Oct 1, 2021
…uration (tardis-sn#1769)

* Changed the logical implementation for the `specific` flag in the debug schema for logging

* Fixed the implementation with intended logic

* Added logic change for specific_log_level flag

* Changed check for specific_log_level parameter & setting it up via the YAML
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Logger doesn't set specific_log_level to a Default value if no functional arguments are present
4 participants