Searching for WAL resume position
No records were returned by Debezium in the timeout seconds 1200, closing the engine and iterator

Kustomer

NAMEDATALEN

_airbyte_raw_...__user_course_performance_scd

..._us___ourse_performance_scd

io.grpc.StatusRuntimeException: DEADLINE_EXCEEDED: Deadline CallOptions will be exceeded in 9.996874017s

.env

docker ps

Running generator...
While trying to generate a connector, an error occurred on line 39 of generate.sh and the process aborted early. This is probably a bug.

0.3.20

0.39.36-alpha

0.43.29

call-heartbeat-server Terminated
main Using existing AIRBYTE_ENTRYPOINT: /airbyte/base.sh
main Waiting on CHILD_PID 7
main PARENT_PID: 1
main EXIT_STATUS: 0
relay-stderr 2023/02/28 01:24:32 socat[8] N reading from and writing to stdio
relay-stderr 2023/02/28 01:24:32 socat[8] E TCP: wrong number of parameters (9 instead of 2)
relay-stderr 2023/02/28 01:24:32 socat[8] N exit(1)
init All files copied successfully, exiting with code 0...
relay-stdout 2023/02/28 01:24:32 socat[8] N reading from and writing to stdio
relay-stdout 2023/02/28 01:24:32 socat[8] E TCP: wrong number of parameters (9 instead of 2)
relay-stdout 2023/02/28 01:24:32 socat[8] N exit(1)
Stream closed EOF for airbyte2/n-local-json-check-57b98b6d-867d-4f38-878c-33b5cb1beabb-0-ymcce (main)
Stream closed EOF for airbyte2/n-local-json-check-57b98b6d-867d-4f38-878c-33b5cb1beabb-0-ymcce (init)
Stream closed EOF for airbyte2/n-local-json-check-57b98b6d-867d-4f38-878c-33b5cb1beabb-0-ymcce (relay-stderr)
Stream closed EOF for airbyte2/n-local-json-check-57b98b6d-867d-4f38-878c-33b5cb1beabb-0-ymcce (call-heartbeat-server)
Stream closed EOF for airbyte2/n-local-json-check-57b98b6d-867d-4f38-878c-33b5cb1beabb-0-ymcce (relay-stdout)

This version included a bug. Use 0.40.30 instead.

0.40.32

request_body_json()

supportsNormalization

update_postgres_schema() {
  { export SQL_PASSWORD=${POSTGRES_PWD}; } 2> /dev/null

  CONTAINER_ALREADY_STARTED="CONTAINER_ALREADY_STARTED_PLACEHOLDER"
  if [ ! -e $CONTAINER_ALREADY_STARTED ]; then
      touch $CONTAINER_ALREADY_STARTED
      temporal-sql-tool --plugin postgres --ep "${POSTGRES_SEEDS}" -u "${POSTGRES_USER}" -p "${DB_PORT}" create --db "${DBNAME}"
      temporal-sql-tool --plugin postgres --ep "${POSTGRES_SEEDS}" -u "${POSTGRES_USER}" -p "${DB_PORT}" --db "${DBNAME}" setup-schema -v 0.0


      temporal-sql-tool --plugin postgres --ep "${POSTGRES_SEEDS}" -u "${POSTGRES_USER}" -p "${DB_PORT}" create --db "${VISIBILITY_DBNAME}"
      temporal-sql-tool --plugin postgres --ep "${POSTGRES_SEEDS}" -u "${POSTGRES_USER}" -p "${DB_PORT}" --db "${VISIBILITY_DBNAME}" setup-schema -v 0.0
  fi
  echo "Starting to update the temporal DB"
  temporal-sql-tool --plugin postgres --ep "${POSTGRES_SEEDS}" -u "${POSTGRES_USER}" -p "${DB_PORT}" --db "${DBNAME}" update-schema -d "${SCHEMA_DIR}"
  echo "Update the temporal DB is done"

  echo "Starting to update the temporal visibility DB"
  temporal-sql-tool --plugin postgres --ep "${POSTGRES_SEEDS}" -u "${POSTGRES_USER}" -p "${DB_PORT}" --db "${VISIBILITY_DBNAME}" update-schema -d "${VISIBILITY_SCHEMA_DIR}"
  echo "Update the temporal visibility DB is done"

}