-
Notifications
You must be signed in to change notification settings - Fork 27
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
🐛🔨 Maintenance: fixes log-level of server in boot and bumpversion commit failure #3070
🐛🔨 Maintenance: fixes log-level of server in boot and bumpversion commit failure #3070
Conversation
Codecov Report
@@ Coverage Diff @@
## master #3070 +/- ##
======================================
Coverage 80.8% 80.8%
======================================
Files 715 715
Lines 30849 30849
Branches 4024 4024
======================================
Hits 24933 24933
Misses 5053 5053
Partials 863 863
Flags with carried forward coverage won't be shown. Click here to find out more. |
6989e35
to
d2d6992
Compare
d2d6992
to
a38d18b
Compare
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.
👍
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.
this is very focused and very much welcomed. thanks!
…er changing README
19e9015
to
889a78d
Compare
Kudos, SonarCloud Quality Gate passed!
|
What do these changes do?
Two very verbose but simple fixes:
boot.sh
sets the same log-level to the app as to the server (i.e.uvicorn
orgunicorn
). Up to now, they were not connected and portainer would always show INFO logs of the server regardless the log-level we set via env varsbumpversion
was failing to commit due to pre-commit-hook failing in modified README -> disabled pre-commit check on bumpversion changes.Related issue/s
Maintenance