has anyone else experienced failures to run discov...
# replication-troubleshooting
g
has anyone else experienced failures to run discover after upgrading airbyte? got
Copy code
Exception: ('Could not discover schema for source',
trying to run discovery in octavia cli. Tailing the logs in the temporal worker I see a null pointer exception
Copy code
java.lang.NullPointerException: null
	at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:889) ~[guava-31.1-jre.jar:?]
	at io.airbyte.workers.internal.VersionedAirbyteStreamFactory.<init>(VersionedAirbyteStreamFactory.java:65) ~[io.airbyte-airbyte-commons-worker-0.40.16.jar:?]
	at io.airbyte.workers.internal.VersionedAirbyteStreamFactory.<init>(VersionedAirbyteStreamFactory.java:56) ~[io.airbyte-airbyte-commons-worker-0.40.16.jar:?]
	at io.airbyte.workers.temporal.discover.catalog.DiscoverCatalogActivityImpl.lambda$getWorkerFactory$2(DiscoverCatalogActivityImpl.java:127) ~[io.airbyte-airbyte-workers-0.40.16.jar:?]
This also happens in the UI. Airbyte version 0.40.16
m
What connector are you using? Can you share the complete log file?
g
I am using the amazon-seller-partner source connector
this also happens on other sources
seems like it is resolved in a newer version of airbyte/helm. I upgraded to 0.40.22 and a connector was able to run discovery where it wasn't able to before
m
Great to hear, let me know if you need further assistance.