-
Notifications
You must be signed in to change notification settings - Fork 128
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
Conversation
Kudos, SonarCloud Quality Gate passed! |
There was a problem hiding this 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
if '.' not in cls: | ||
self.logger.warning('impossible to build, wrongly formated class: {}'.format(cls)) |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
For details: https://navitia.atlassian.net/browse/NAV-1858