Skip to content

Remove constructor logging in DefaultRegistryClient#59

Merged
cmoesel merged 1 commit intoFHIR:mainfrom
reason-healthcare:remove-constructor-logging
Jun 30, 2025
Merged

Remove constructor logging in DefaultRegistryClient#59
cmoesel merged 1 commit intoFHIR:mainfrom
reason-healthcare:remove-constructor-logging

Conversation

@bkaney
Copy link
Contributor

@bkaney bkaney commented Jun 30, 2025

This was causing a problem where the logger was being called before the calling superclass was initialized, leading to error: "Must call super constructor in derived class before accessing 'this' or returning from derived constructor"

This was causing a problem where the logger was being called before the calling superclass was initialized, leading to error: "Must call super constructor in derived class before accessing 'this' or returning from derived constructor"
Copy link
Member

@cmoesel cmoesel left a comment

Choose a reason for hiding this comment

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

For others who might be following this, we agreed that we don't need to log the custom registry since the log messages during package downloads show the custom registry URL (and since logging during class construction was causing problems).

Thanks for this PR, @bkaney. And thanks for the new test -- it's a great representation of the exact issue we were running into.

@cmoesel cmoesel merged commit c5d0b5b into FHIR:main Jun 30, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants