You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Error when connecting from JDBC MariaDB driver #807
gsc-gitbase-spark-connector-jupyter | Exception in thread "main" java.sql.SQLNonTransientConnectionException: Could not connect to gitbase:3306 : unexpected end of stream, read 0 bytes from 4 (socket was closed by server)
gsc-gitbase-spark-connector-jupyter | at org.mariadb.jdbc.internal.util.exceptions.ExceptionMapper.get(ExceptionMapper.java:234)
gsc-gitbase-spark-connector-jupyter | at org.mariadb.jdbc.internal.util.exceptions.ExceptionMapper.getException(ExceptionMapper.java:165)
gsc-gitbase-spark-connector-jupyter | at org.mariadb.jdbc.internal.protocol.AbstractConnectProtocol.connectWithoutProxy(AbstractConnectProtocol.java:1199)
gsc-gitbase-spark-connector-jupyter | at org.mariadb.jdbc.internal.util.Utils.retrieveProxy(Utils.java:560)
gsc-gitbase-spark-connector-jupyter | at org.mariadb.jdbc.MariaDbConnection.newConnection(MariaDbConnection.java:174)
...
Only happening with the latest v0.20.0-beta4 release
What query are you making? Can you provide more specific details. I've been trying to reproduce this with both 0.20.0-beta4 and master and it works for me.
Activity
erizocosmico commentedon Apr 26, 2019
What query are you making? Can you provide more specific details. I've been trying to reproduce this with both 0.20.0-beta4 and master and it works for me.
ajnavarro commentedon Apr 26, 2019
From https://github.com/src-d/gitbase-spark-connector repo:
srcd/gitbase:v0.20.0-beta3tosrcd/gitbase:v0.20.0-beta4/path/to/reposto a valid path with repositorieserizocosmico commentedon Apr 26, 2019
Ok, got to reproduce this.
erizocosmico commentedon Apr 30, 2019
There's an error parsing connection attributes, which has been reported for a couple months:
vitessio/vitess#4603
I added more details to the issue and a reproduction case.
We have two options here:
I think we should fix vitess, but no idea how much that's gonna take.
WDYT @ajnavarro?
ajnavarro commentedon May 31, 2019
Not fixed in gitbase.
kuba-- commentedon May 31, 2019
vitessio/vitess#4897
erizocosmico commentedon Oct 9, 2019
Will be fixed once we upgrade to latest vitess version.