Greg Smethells

cc @simonfontana

I am working on a solution for a large test suite that leverages Kubernetes runners in GitLab CI. So far, I will just note that the suggested solution has not...

@RonnyPfannschmidt I don't believe so, but I'll check. We use https://docs.gitlab.com/runner/executors/kubernetes.html

Nope: ``` pid is 22 ============================= test session starts ============================== ```

conftest.py: ``` @pytest.fixture(scope = 'session', autouse = True) def termHandler(): from signal import getsignal, signal, SIGTERM, SIGINT orig = signal(SIGTERM, getsignal(SIGINT)) yield signal(SIGTERM, orig) ``` Snippet of gcstorage_test.py (the `sleep()`...

Just to close the loop on previous comments: this appears to be a known issue with the Kubernetes gitlab-runner project. https://gitlab.com/gitlab-org/gitlab-runner/-/issues/28162 In any case, I believe the above fixture would...

Handling DICOM files that say one thing for their format and then encode in another is par for the course in real world examples. I cannot see pydicom being used...

@darcymason keep in mind what David Clunie said about the topic since he was part of that DICOM committee: http://dclunie.blogspot.com/2008/11/dicom-exposure-attribute-fiasco.html

Thank you for taking the time to discuss ideas and consider this. I understand wanting to adhere tightly to the standard (we do so for edge cases the majority of...

> reading/writing `dataset`s from/to files via pydicom continued to support maintaining existing values, regardless of whether those values violate the standard Any other position would become a deal breaker for...