Catherine Noll
Catherine Noll
Hi @ethomson, I've opened a [PR](https://github.com/libgit2/libgit2/pull/6399) that should fix this but would like feedback on the approach when you've got time.
@nurikk thanks for submitting this! In your PR description, should "2. Fixes connection validation loop" link to a different issue? I want to make sure I have the full context.
Thanks @bazarnov this is getting really close! In addition to the new comments, can you also upgrade the S3 connector (and other file-based connectors if it's not too much trouble)...
@bazarnov please start by migrating a couple of the less-used of the connectors (maybe azure-blob-storage first, then gcs) and monitor for errors, before migrating the others.
Great, thank you @lazebnyi!
@brianjlai the manifest changes were done manually, as there weren't too many. I made the suggested changes if you want to rereview.
Thanks for the review @dandavison! I made the updates you suggested.
Hey @brianjlai & @askarpets, we definitely don't intend to be checking the stream order. I actually thought we'd fixed this. Will look into it, and sorry for the confusion!
@aaronsteers the main logic that I'm concerned with is making sure that we can't unpin or pin over a pin that already exists without "good reason". I'm not sure exactly...
This issue has been fixed because we are no longer validating the stream prefix. In [this PR](https://github.com/airbytehq/airbyte-platform-internal/pull/14503), we removed `SyncCatalog` v1 - related code and obsolete components, including the `DestinationStreamNamesModal`,...