Hey Everyone! I'm developing a custom source conne...
# replication-troubleshooting
l
Hey Everyone! I'm developing a custom source connector in python, and I am having some trouble when trying to create a connection using it, I can use it to create a source successfully, but when creating a connection with it (destination to S3) Airbyte throws an unknow error, just like the image attached, I tried to validate the source using the
Copy code
docker run --rm airbyte/source-example-python:dev spec
docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-example-python:dev check --config /secrets/config.json
docker run --rm -v $(pwd)/secrets:/secrets airbyte/source-example-python:dev discover --config /secrets/config.json
docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/sample_files:/sample_files airbyte/source-example-python:dev read --config /secrets/config.json --catalog /sample_files/configured_catalog.json
and it works fine like this One thing I noticed is this error on the browser console when the error appears on screen
Copy code
index-01f874f4.js:39 TypeError: Cannot convert undefined or null to object
    at Function.keys (<anonymous>)
    at zl (SchemaError-3025fefa.js:72:6583)
    at bo (index-01f874f4.js:37:52767)
    at to (index-01f874f4.js:37:62191)
    at ra (index-01f874f4.js:37:61528)
    at di (index-01f874f4.js:37:61122)
    at wa (index-01f874f4.js:41:11784)
    at ya (index-01f874f4.js:41:932)
    at kc (index-01f874f4.js:41:863)
    at cn (index-01f874f4.js:41:722)
t
Hi Luan, this looks like a bug in the FE. No matter what the discovered catalog will be this shouldn't fail the frontend.
When the error appears in the browser there should be a link to the source code for each of the lines in the stacktrace. Could you possibly click the one for the first line in the stacktrace and the second and send me a screenshot of that (I'm trying to figure out where this exactly is happening)
l
Yup, just a sec
t
okay wait a moment, there's a
{}
icon on the bottom left, could you maybe click that first (so it formats the code a bit better)
l
Oh, ok
Marked the line for you
image.png
I also have the output of the
discover_schema
endpoint if that helps you
t
awesome thank you, that should help me. II'll have a look in a bit and will report
This actually happened to be fixed yesterday: https://github.com/airbytehq/airbyte/pull/22227 As soon as we release the next OSS version that error should no longer happen.
If possible could you give me the configured_catalog from your test? (Also feel free to share it in a DM, if you don't want to have it public), that might help us reproduce the root source of this.
l
Yes, of course! I'm going to send it to you on a DM
p
As soon as we release the next OSS version that error should no longer happen.
Running into the same issue. Do you know when this release will happen? (Or instructions on how I can build my own version with the change)
t
We're planning to release a version with the fix tomorrow. If you want to build it locally, you can just checkout the master branch of the repository and use gradle to build it: https://docs.airbyte.com/contributing-to-airbyte/developing-locally/ Basically:
Copy code
SUB_BUILD=PLATFORM ./gradlew build
VERSION=dev docker compose up
πŸ™ 1
p
@Tim Roes (Airbyte) β€” do you know if the release is still planned for today?
t
Sorry we extended an ongoing Code Freeze till Monday, So I'm waiting for this to run out before releasing the OSS version. So it will be Monday.
πŸ™ 1
p
Got it β€” any updates on the new release?
plus1 1
@Tim Roes (Airbyte) β€” any idea when the release will be? Would love to get a better sense for when I communicate with clients. Right now, my Stripe source isn’t working
m
@Tim Roes (Airbyte) Hi Tim, Has the release been deployed? I have the same error for my custom Netskope connector...
t
Hi, we're currently undergoing some larger repository restructuring, so we paused releases for several weeks while the migration is ongoing. Once we're done with the restructuring, we'll cut a new release. You can already continue running from master, if this is blocking your custom connector development.
πŸ‘ 1