-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Turn off default httpavailabilitystrategy for source-marketo (GA) #22015
Conversation
/test connector=connectors/source-marketo
Build FailedTest summary info:
|
/test connector=connectors/source-marketo
Build FailedTest summary info:
|
Same failure as in #connector-health |
Then I think it's probably OK to merge |
Thanks, will do. Double-checking all others for which this is the case and posting those as well! |
/publish connector=connectors/source-marketo run-tests=false
if you have connectors that successfully published but failed definition generation, follow step 4 here |
Apparently this version was published 11 days ago without a changelog, coming back to look into it |
It was released off of this PR that was never merged: #20973. Seems to have been published by a contributor while skipping the tests |
If I try to push a new version of the connector, I'd essentially be undoing the changes from the unmerged contributor PR for the latest version of the connector published. That would affect OSS users who upgraded to this version because they were seeing the issue linked in that PR. However, cloud is still seeing 0.1.11, since the cloud catalog was never updated, since the PR was merged. Therefore cloud users should see no effects of going from 0.1.11 to 0.1.13. Users who want 0.1.12 in OSS can still use that version as they see fit, and then when that PR is merged, the changes will be reflected in 0.1.14 (or whatever version is next when it goes in) for both cloud and OSS users. Does that sound good @evantahler? I suppose I'd add the changelog entry from 0.1.12 too, and make it clear that 0.1.13 reverts those changes |
Yep! Although, it's a shame we got into this position. Alternatively, you could merge in #20973 and then merge this after? |
I would, except for the fact that the acceptance tests went from consistently succeeding to consistently failing. I think that PR needs some more work before it goes in 😕 will run tests on that branch |
Actually, now that I think about it, it seems weird that the connector would start failing tests on the #connector-health check since they're built off of master. So maybe that is actually unrelated, though it started failing on the 19th, when the new version was released... confusion abounds |
Merged the contributor PR - someone had already released a newer version. Releasing this version should re-introduce the contributor's changes lost in the 1.0.0 version as well as add my changes. |
/publish connector=connectors/source-marketo run-tests=false
if you have connectors that successfully published but failed definition generation, follow step 4 here |
Airbyte Code Coverage
|
See #21888 for description