-
-
Notifications
You must be signed in to change notification settings - Fork 167
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
BUG: Correctly update atmospheric conditions after changing date and location #743
Conversation
…location add location
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #743 +/- ##
===========================================
+ Coverage 75.99% 76.43% +0.44%
===========================================
Files 95 95
Lines 11015 11078 +63
===========================================
+ Hits 8371 8468 +97
+ Misses 2644 2610 -34 ☔ View full report in Codecov by Sentry. |
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.
Nice catch!
Can you run black again please? @WilliamArmst
I am wondering whether we should release this BUG in a minor version (v1.7.1).
Co-authored-by: Gui-FernandesBR <[email protected]>
I'm not sure what running black again means, if it's the local tests I'll have to wait until I get back from classes. This is a pretty small fix and even without it, I think updating the date sometimes works anyways for some reason? It doesn't make sense to me, but it only became an issue for me when I tried doing batch simulations with multiple dates. Ultimately up to you if you want to put it into a bugfix. |
Is it failing because the linter wants this?
|
Yes! The code line should not exceeds 88 length positions. Black is one of our linters. Running |
The base branch was changed.
Pull request type
Bugfix
Checklist
black rocketpy/ tests/
) has passed locallypytest tests -m slow --runslow
) have passed locallyCHANGELOG.md
has been updated (if relevant)Current behavior
If the environment date is updated after setting the atmospheric model, the function call to update the model to that date did not pass
self.atmospheric_model_type
when it is required by the function. This led to the file being passed in as the type.New behavior
Behaves as expected
Breaking change
Additional information
N/A