Salesforce Connection failing on undecodable byte at end of stream and extra props

  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: Linux (Debian on GCP)
  • Memory / Disk: 64Gb
  • Deployment: Docker
  • Airbyte Version: 0.36.0-alpha
  • Source name/version: Salesforce@latest
  • Destination name/version: BigQuery@latest
  • Step: During Sync
  • Description: Our connection is failing consistently across 4 different sync attempts.

errors: $.credential: is not defined in the schema and the schema does not allow additional properties, $.part_size_mb: is not defined in the schema and the schema does not allow additional properties, $.gcs_bucket_name: is not defined in the schema and the schema does not allow additional properties, $.gcs_bucket_path: is not defined in the schema and the schema does not allow additional properties, $.keep_files_in_gcs-bucket: is not defined in the schema and the schema does not allow additional properties, $.method: must be a constant value Standard

Here is a failure from the recent attempt using BigQuery with GCS staging.

This error is preceded by this:
UnicodeDecodeError: 'utf-8' codec can't decode bytes in position 12173-12174: unexpected end of data
which has happened on both using GCS and without. This failure bubbles up and causes resource not to be cleaned up like the GCS buckets or the created tmp tables. And the whole process fails and retires.

logs-6.txt (609.6 KB)

Actually its happening in all of my connections

errors: $.credential: is not defined in the schema and the schema does not allow additional properties, $.part_size_mb: is not defined in the schema and the schema does not allow additional properties, $.gcs_bucket_name: is not defined in the schema and the schema does not allow additional properties, $.gcs_bucket_path: is not defined in the schema and the schema does not allow additional properties, $.keep_files_in_gcs-bucket: is not defined in the schema and the schema does not allow additional properties, $.method: must be a constant value Standard

This is hugely problematic

JsonSchemaValidator

This specifically FYI.

Bumping this topic in hopes it doesn’t get buried. Its really blocking adoption.

We aren’t actively adopting anymore. Bumping anyway since there are so many recent replies on other threads but this thread hasn’t gotten one.

Sorry @z3z1ma we’re implementing Discourse and try to adopt a tool to help us manage all tickets created here.

Hello Alexander can you test the latest version of Salesforce 1.0.7?
See PR here: https://github.com/airbytehq/airbyte/pull/12552