-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Fixing HealthCheck for Supabase #1848
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
Fixing HealthCheck for Supabase #1848
Conversation
@shifluxxc , Please ensure that the PR title clearly reflects the primary fix or feature you're introducing. |
@shifluxxc Please comment on the 8000 issue that you want to work on it so that i can assign this issue to you. Thanks |
… within test functions
I will make sure to wait for assignment before picking up issues . I updated the PR title and also removed the setOut function from mocklogger. |
@shifluxxc , if you've addressed the review comments, please mark them as resolved. This helps move your PR toward merging. If the reviewer disagrees or has further suggestions, they will leave additional comments or update their review accordingly. |
Done 👍 |
I have tested the PR, it works fine. Below are the screenshots for the reference of other reviewers. However there is no logging and traces for HealthCheck in any of the SQL supported datasources addition(I checked for mysql local instance and supabase). I feel that is out of the scope of this PR and can be handled in another PR. @shifluxxc, please change the PR's name to : "Fixing HealthCheck for Supabase" |
Done |
@shifluxxc You have the following linter issues in your PR. Please resolve them so that we can go ahead and re-review your PR. |
Sir I have resolved the linting , you can review the changes |
Pull Request Template
Description:
Breaking Changes (if applicable):
Additional Information:
DB_HOST
orDB_NAME
are omitted for Supabase, as they are set to default.Checklist:
goimport
andgolangci-lint
.Thank you for your contribution!