-
Notifications
You must be signed in to change notification settings - Fork 9
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
[BBPBGLIB-1153] Allow disabling reports from SONATA config #156
Conversation
The test is admittedly not completely end-to-end, but given the other tests there this seemed to me the most logical place to include it. Let me know if I should move it somewhere else. |
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.
Thanks for the contribution! I like the solution, just a couple of nitpicks! :)
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.
LGTM. Thanks!
@kbvw , this PR can not trigger our GitLab CI tests because it is requested from the forked repo not the repo branch. |
No worries, that's my bad. I just now got added: will open a new one. |
Closing in favour of #159. |
Context
This PR solves
https://bbpteam.epfl.ch/project/issues/browse/BBPBGLIB-1153
According to the SONATA specification, reports can be disabled with an optional
enabled
parameter in the config file. This option was already parsed, but not used to disable the reports.Scope
A small change to the
enable_reports
method of theNode
class, filtering the reports based on theenabled
flag.Testing
An integration test in
tests/integration-e2e/test_reports.py
, reusing part of the existing fixture there and reading the flag from a SONATA config file.Review