-
Notifications
You must be signed in to change notification settings - Fork 208
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: Clean up manager creation to avoid NPEs during background start #1586
fix: Clean up manager creation to avoid NPEs during background start #1586
Conversation
Signed-off-by: SamMayWork <sam.may@kaleido.io>
Signed-off-by: SamMayWork <sam.may@kaleido.io>
Gonna have to fix the Docker image
|
Fix tested manually using the recreate from #1585 (comment) and all looks good. |
Signed-off-by: SamMayWork <sam.may@kaleido.io>
Signed-off-by: SamMayWork <sam.may@kaleido.io>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1586 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 337 337
Lines 24225 24230 +5
=========================================
+ Hits 24225 24230 +5 ☔ View full report in Codecov by Sentry. |
@@ -75,7 +75,7 @@ ARG UI_TAG | |||
ARG UI_RELEASE | |||
RUN apk add --update --no-cache \ | |||
sqlite=3.44.2-r0 \ | |||
postgresql16-client=16.3-r0 \ | |||
postgresql16-client=16.4-r0 \ |
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.
Required to get the build working, looks like the old version of the client has been removed. A quick look through the PostgreSQL release notes for this version suggests it just contains bug fixes: https://www.postgresql.org/docs/release/16.4/
The extent of testing done on the new client version is the UTs in this repo, if there's any further testing required let me know.
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 great investigation and fix 👍
ref: #1585 (comment)
Without this fix when calling to create a contract manager, it's possible for both the return value and the error value to be non-nil. This ensures that strictly one or the other is set.
firefly/internal/orchestrator/orchestrator.go
Line 540 in dc97c73
Need to test using the steps provided above to ensure the fix is good (also pending UT coverage).