Skip to content

Reverting to code from 1.2.0 in versions 1.3.1 and 1.3.2 breaks streams from syncing #45

@nickhamlin

Description

@nickhamlin

I wish I had a clearer sense of the root cause to pass along here and I'm happy to share more info if it's helpful. We had things running fine in 1.3.0, but then tried upgrading to 1.3.2. Following the upgrade, the tap ran "successfully" but did not extract any actual data. Reverting to 1.3.0 resolved the issue. In addition, reverting back to 1.2.0 caused it to occur again, so I'm confident the issue lies somewhere in that release (it looks like there were a lot of changes made between 1.2.0 and 1.3.0). Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions