Hi! I have been trying the connector builder UI a ...
# replication-troubleshooting
m
Hi! I have been trying the connector builder UI a few times and now after an upgrade it seems my trials have left the builder in a state that it is unable to recover from. I get an error message when i visit http://localhost:8000/connector-builder. Can I reset the state in any way? This is a test instance so truncating stuff is not a problem. Just need help in how to do it. Thanks
n
Hi Martin! There isn't a well documented way to reset state right now. Since this is a test instance, I would just remove everything and reinstall - that would probably be the most straightforward solution!
m
OK, thanks. And when you say remove everything you men delete all files from my local copy of the repository? There isnt some folder somewhere else storing the state? I will try it in the mean time.
I have deleted all containers, images and volumes in docker desktop. Deleted (moved) the repo and cloned it again. Still I get the error message when visiting the connector builder.
Any help would be appreciated
m
@Martin Larsson can you open the web broswer console or check the network tab and see if there is any api response? Or maybe
docker logs airbyte-connector-builder-server
m
In chrome console I first get a 401 on manifest.json then this error message:
Copy code
TypeError: Cannot read properties of undefined (reading 'type')
    at builderAuthenticatorToManifest (ConnectorBuilderPage-225ac3da.js:32:7437)
    at builderStreamToDeclarativeSteam (ConnectorBuilderPage-225ac3da.js:32:9250)
    at ConnectorBuilderPage-225ac3da.js:32:9944
    at Array.map (<anonymous>)
    at convertToManifest (ConnectorBuilderPage-225ac3da.js:32:9937)
    at ConnectorBuilderPage-225ac3da.js:32:12528
    at Object.useMemo (index-01f874f4.js:37:58659)
    at z.useMemo (index-01f874f4.js:12:5877)
    at ConnectorBuilderFormStateProvider (ConnectorBuilderPage-225ac3da.js:32:12503)
    at bo (index-01f874f4.js:37:52767)
In docker desktop in the airbyte-connector-builder-server container logs is only this:
Copy code
INFO:     Started server process [1]

INFO:     Waiting for application startup.

INFO:     Application startup complete.

INFO:     Uvicorn running on <http://0.0.0.0:80> (Press CTRL+C to quit)
After clearing browser history I am in! 😀
Now that I am able to test it I found a shortcoming that makes it unusable in my particular use case. Should I create an issue in git?
m
Please @Martin Larsson! Product issues always should be reported in Github 🙏
m
Thanks