Skip to content
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

Merged
merged 5 commits into from
Jan 31, 2023

Conversation

erohmensing
Copy link
Contributor

@erohmensing erohmensing commented Jan 27, 2023

See #21888 for description

@octavia-squidington-iv octavia-squidington-iv added area/connectors Connector related issues area/documentation Improvements or additions to documentation connectors/source/marketo labels Jan 27, 2023
@erohmensing erohmensing requested a review from a team January 27, 2023 21:51
@erohmensing erohmensing changed the title Turn off default for source-marketo (GA) Turn off default httpavailabilitystrategy for source-marketo (GA) Jan 27, 2023
@erohmensing
Copy link
Contributor Author

erohmensing commented Jan 27, 2023

/test connector=connectors/source-marketo

🕑 connectors/source-marketo https://github.com/airbytehq/airbyte/actions/runs/4028652092
❌ connectors/source-marketo https://github.com/airbytehq/airbyte/actions/runs/4028652092
🐛 https://gradle.com/s/rwuxmyodblnng

Build Failed

Test summary info:

=========================== short test summary info ============================
FAILED test_core.py::TestBasicRead::test_read[inputs0] - Failed: Stream progr...
SKIPPED [1] ../usr/local/lib/python3.9/site-packages/source_acceptance_test/tests/test_core.py:94: The previous and actual specifications are identical.
SKIPPED [1] ../usr/local/lib/python3.9/site-packages/source_acceptance_test/tests/test_core.py:377: The previous and actual discovered catalogs are identical.
====== 1 failed, 28 passed, 2 skipped, 31 warnings in 2274.47s (0:37:54) =======

> Task :airbyte-integrations:connectors:source-marketo:sourceAcceptanceTest FAILED

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

See https://docs.gradle.org/7.6/userguide/command_line_interface.html#sec:command_line_warnings

Execution optimizations have been disabled for 1 invalid unit(s) of work during this build to ensure correctness.
Please consult deprecation warnings for more details.
48 actionable tasks: 23 executed, 25 up-to-date

Publishing build scan...
https://gradle.com/s/rwuxmyodblnng

The remote build cache was disabled during the build due to errors.
S3 cache writes: 1, elapsed: 701ms, sent to cache: 446 B

@erohmensing
Copy link
Contributor Author

erohmensing commented Jan 28, 2023

/test connector=connectors/source-marketo

🕑 connectors/source-marketo https://github.com/airbytehq/airbyte/actions/runs/4029848981
❌ connectors/source-marketo https://github.com/airbytehq/airbyte/actions/runs/4029848981
🐛 https://gradle.com/s/7l3ydtm4c3pcw

Build Failed

Test summary info:

=========================== short test summary info ============================
FAILED test_core.py::TestBasicRead::test_read[inputs0] - Failed: Stream progr...
SKIPPED [1] ../usr/local/lib/python3.9/site-packages/source_acceptance_test/tests/test_core.py:94: The previous and actual specifications are identical.
SKIPPED [1] ../usr/local/lib/python3.9/site-packages/source_acceptance_test/tests/test_core.py:377: The previous and actual discovered catalogs are identical.
====== 1 failed, 28 passed, 2 skipped, 31 warnings in 2273.91s (0:37:53) =======

> Task :airbyte-integrations:connectors:source-marketo:sourceAcceptanceTest FAILED

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

See https://docs.gradle.org/7.6/userguide/command_line_interface.html#sec:command_line_warnings

Execution optimizations have been disabled for 1 invalid unit(s) of work during this build to ensure correctness.
Please consult deprecation warnings for more details.
48 actionable tasks: 23 executed, 25 up-to-date

Publishing build scan...
https://gradle.com/s/7l3ydtm4c3pcw

The remote build cache was disabled during the build due to errors.
S3 cache writes: 1, elapsed: 728ms, sent to cache: 448 B

@erohmensing
Copy link
Contributor Author

Same failure as in #connector-health

@evantahler
Copy link
Contributor

Then I think it's probably OK to merge

@erohmensing
Copy link
Contributor Author

Thanks, will do. Double-checking all others for which this is the case and posting those as well!

@erohmensing
Copy link
Contributor Author

erohmensing commented Jan 30, 2023

/publish connector=connectors/source-marketo run-tests=false

🕑 Publishing the following connectors:
connectors/source-marketo
https://github.com/airbytehq/airbyte/actions/runs/4045182674


Connector Did it publish? Were definitions generated?
connectors/source-marketo

if you have connectors that successfully published but failed definition generation, follow step 4 here ▶️

@erohmensing
Copy link
Contributor Author

Apparently this version was published 11 days ago without a changelog, coming back to look into it

@erohmensing
Copy link
Contributor Author

It was released off of this PR that was never merged: #20973. Seems to have been published by a contributor while skipping the tests

@erohmensing
Copy link
Contributor Author

erohmensing commented Jan 30, 2023

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

@evantahler
Copy link
Contributor

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?

Yep! Although, it's a shame we got into this position.

Alternatively, you could merge in #20973 and then merge this after?

@erohmensing
Copy link
Contributor Author

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

@erohmensing
Copy link
Contributor Author

erohmensing commented Jan 30, 2023

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

@erohmensing
Copy link
Contributor Author

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.

@erohmensing
Copy link
Contributor Author

erohmensing commented Jan 31, 2023

/publish connector=connectors/source-marketo run-tests=false

🕑 Publishing the following connectors:
connectors/source-marketo
https://github.com/airbytehq/airbyte/actions/runs/4058180228


Connector Did it publish? Were definitions generated?
connectors/source-marketo

if you have connectors that successfully published but failed definition generation, follow step 4 here ▶️

@erohmensing erohmensing enabled auto-merge (squash) January 31, 2023 20:57
@octavia-squidington-iii octavia-squidington-iii temporarily deployed to more-secrets January 31, 2023 20:59 — with GitHub Actions Inactive
@octavia-squidington-iii octavia-squidington-iii temporarily deployed to more-secrets January 31, 2023 20:59 — with GitHub Actions Inactive
@github-actions
Copy link
Contributor

Airbyte Code Coverage

There is no coverage information present for the Files changed

Total Project Coverage 24.51%

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/connectors Connector related issues area/documentation Improvements or additions to documentation connectors/source/marketo
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants