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

Jormun: Optim log readyness and others #3950

Merged
merged 2 commits into from
Mar 13, 2023
Merged

Conversation

kadhikari
Copy link
Contributor

  • Log on /readyness only with log_level=DEBUG
  • Duplicate log deleted

For details: https://navitia.atlassian.net/browse/NAV-1858

@kadhikari kadhikari requested review from azime, pbench, pbougue and xlqian March 8, 2023 15:16
@sonarqubecloud
Copy link

sonarqubecloud bot commented Mar 8, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

100.0% 100.0% Coverage
0.0% 0.0% Duplication

Copy link
Contributor

@pbougue pbougue left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Waiting for a reply on comments (from @pbench and me) but it looks OK

Comment on lines -78 to -79
if '.' not in cls:
self.logger.warning('impossible to build, wrongly formated class: {}'.format(cls))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't get what's affected by that change, even though it looks harmless.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is most probable that there will be an exception and hence will write another log four lines after.
I simply deleted duplicate log writing.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the change is that if we use a "root" class it won't raise anymore, but before it did... I guess it's not important.

@azime azime merged commit ef33582 into dev Mar 13, 2023
@azime azime deleted the optim_log_readyness_and_others branch March 13, 2023 09:02
@pbougue pbougue changed the title Optim log readyness and others Jormun: Optim log readyness and others Mar 28, 2023
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.

4 participants