It looks like that it was caused by some internal changes on the server side, and this prevents databricks-connect from working. You can always disable this check by setting environment variable
DEBUG_IGNORE_VERSION_MISMATCH to value
export DEBUG_IGNORE_VERSION_MISMATCH=1 in the console before executing
databricks-connect test) – you can also set this environment variable in the PyCharm.
Update: it should be fixed by Databricks Connect 6.4.2 that was just released.
CLICK HERE to find out more related problems solutions.