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

Changed log level of Capturer Object #67

Merged
merged 3 commits into from
May 8, 2023
Merged

Changed log level of Capturer Object #67

merged 3 commits into from
May 8, 2023

Conversation

AlexPatrie
Copy link
Contributor

@AlexPatrie AlexPatrie commented May 7, 2023

What does this pr do?
Addresses an issue related to this specific repo and others, as per #56.
The log_level in method is by default set to StandardOutputErrorCapturerLevel.c which is "c". This results in a lack of proper output and a capture freeze. when setting this log_level to .python, a perfect output is produced in a timely fashion.

@AlexPatrie AlexPatrie requested review from fbergmann and eagmon and removed request for fbergmann May 7, 2023 06:16
Copy link

@eagmon eagmon left a comment

Choose a reason for hiding this comment

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

Wow, that's it??? Can this be generalized in utils? Let's get it merged and deployed.

@AlexPatrie
Copy link
Contributor Author

Working on a generalization now!

@sonarqubecloud
Copy link

sonarqubecloud bot commented May 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

No Coverage information No Coverage information
0.0% 0.0% Duplication

@AlexPatrie AlexPatrie merged commit e446a40 into dev May 8, 2023
@AlexPatrie AlexPatrie deleted the change-log-level branch May 8, 2023 04:48
@jcschaff
Copy link
Member

jcschaff commented May 9, 2023

seems that the try: except: block to catch an assertion is unexpected - is there a reason that an if or if/else could not have been used? Generally using try/except for normal flow of control is not best practice in most languages. If this is in response to SonarCloud - then we need to address that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

biosimulators no longer working on macOS Incorrectly raised Exception regarding number of time points
3 participants