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
Ignore brew errors #614
Ignore brew errors #614
Conversation
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.
@janelletavares When I implemented this feature, I added the option to disable these notifications via an environment variable: https://github.com/meroxa/cli/blob/master/cmd/meroxa/builder/autoupdate.go#L33 and opened this other pull-request https://github.com/meroxa/acceptance/commit/413e232c78ed1e08438dc42b211eb57f6aaf69b3
For some reason this is not doing what's supposed to.
I'll take a look.
@janelletavares that should be working. Tested locally and with |
@janelletavares Did they fail locally or in CI? If it's locally, I'd recommend using |
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.
@janelletavares this is a good change to do anyways, but please take a look at my other comments to make sure the other parts are working for you (i.e.: curious wether this failed locally or in our acceptance tests via CI).
@raulb this failed in an automated acceptance test run in github |
@raulb looks like there's a type in the acceptance tests. the env var should be MEROXA_DISABLE_NOTIFICATIONS_UPDATE, but in the acceptance tests we set MEROXA_DISABLE_UPDATE_NOTIFICATION. update and notification are flipped and notification is singular. I'll open a PR in acceptance repo, too. thanks! |
@janelletavares oh no!!! No wonder it wasn't working! Thank you and nice catch! |
Description of change
Acceptance tests failed because we didn't get a coherent response from brew. Printing the upgrade message doesn't seem important enough to fail, so these changes just skip it and exit with no error instead.
Fixes
Type of change
How was this tested?
Demo
Additional references
=== RUN TestCollaborationsMySQLToPG/list_resource_types
shared_test.go:164: /app/bin/meroxa --cli-config-file /root/meroxa.main.env resources list --types
shared_test.go:166: TYPES
================
bigquery
elasticsearch
kafka
mongodb
mysql
postgres
redshift
s3
snowflakedb
sqlserver
notion
confluentcloud
panic: runtime error: index out of range [1] with length 0
Documentation updated