Summary
The user is facing an issue while trying to add a custom connector into Airbyte. The error ‘Internal Server Error: Get Spec job failed’ is encountered during the process.
Question
Unable to add Custom connector into Airbyte: get spec job failed error
- After taking a docker build, will create a new source from Airbyte UI and enter docker repositoty details. i’m facing issue in this step only
- Error details - Internal Server Error: Get Spec job failed.
airbyte-worker | 2024-07-03 16:01:35 platform > Preparing command: docker run --rm --init -i -w /data/2b5da00b-9814-44d9-a10e-36b651e17e00/0 --log-driver none --name source-np-hubspot-spec-2b5da00b-9814-44d9-a10e-36b651e17e00-0-rtmvm --network host -v airbyte_workspace:/data -v oss_local_root:/local -e DEPLOYMENT_MODE=OSS -e WORKER_CONNECTOR_IMAGE=airbyte/source-np-hubspot:1.0.0 -e AUTO_DETECT_SCHEMA=true -e LAUNCHDARKLY_KEY= -e SOCAT_KUBE_CPU_REQUEST=0.1 -e SOCAT_KUBE_CPU_LIMIT=2.0 -e FIELD_SELECTION_WORKSPACES= -e USE_STREAM_CAPABLE_STATE=true -e WORKER_ENVIRONMENT=DOCKER -e AIRBYTE_ROLE=dev -e APPLY_FIELD_SELECTION=false -e WORKER_JOB_ATTEMPT=0 -e OTEL_COLLECTOR_ENDPOINT=http://host.docker.internal:4317 -e FEATURE_FLAG_CLIENT=config -e AIRBYTE_VERSION=0.63.3 -e WORKER_JOB_ID=2b5da00b-9814-44d9-a10e-36b651e17e00 airbyte/source-np-hubspot:1.0.0 spec
airbyte-temporal | {“level”:“warn”,“ts”:“2024-07-03T16:01:38.924Z”,“msg”:“Unspecified task queue kind”,“service”:“frontend”,“wf-task-queue-name”:“SYNC”,“wf-namespace”:“default”,“logging-call-at”:“workflow_handler.go:3772”}
airbyte-worker | 2024-07-03 16:01:39 platform > Unable to detect Protocol Version, assuming protocol version 0.2.0
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.