-
Notifications
You must be signed in to change notification settings - Fork 19
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
FIX: Background App initialization #1030
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1030 +/- ##
==========================================
+ Coverage 83.73% 87.82% +4.08%
==========================================
Files 35 36 +1
Lines 2269 2324 +55
==========================================
+ Hits 1900 2041 +141
+ Misses 369 283 -86 |
@dipinknair On docker I can reproduce that crash with 252 on the main branch of PyMechanical. I will proceed with the merge. Please try to find out which build date of 252 the crash started to happen in |
@koubaa build date for the 252 where failure has seen. |
@dipinknair to confirm, the failure is seen on the 1/6 build but not on the 1/5 build? |
Pass on build date 11/27/2024 09:34:44 |
@dipinknair that's a long range. Were there no builds in between? |
@koubaa |
@dipinknair ok - seems like something from the very beggining of 25.2. Could be related to the revisioning itself or a thirdparty library change that happened with the revisioning |
@dipinknair please come up with a script that is a minimal reproduction of the crash and we can dig deeper |
@koubaa , Here is a simple script that throws an exception
this is suppose to show only deprecation warning but with 252 its giving the exception as below.
|
Fixes #975
Also cleans up some of the special case handling for exit codes