-
From what I can make out, Snowflake CLI uses config.toml - https://docs.snowflake.com/en/developer-guide/snowflake-cli/connecting/configure-cli . Not sure why superset wants config.toml . Might be a question for the uptsream project?
-
Hi, do you need any information from me ?
-
@rapmac13160 we don't have experience with snowflake and don't have a set up to test. So, you will have to help us debug this further.
You said "suddenly stopped to operate" . Does this mean it worked before and just stopped working recently? What changed?
-
Sure. Yes the connection worked well in the past month. I did not check superset for few months and when i connected few days ago, this message appeared. It can possibly be linked to an update of superset.
It was working fine at that time https://forum.cloudron.io/topic/11457/install-prophet-package/10?_=1732531616852
-
@rapmac13160 do you think you can generate some test snowflake credentials / database for us to test? If you can send them to support@cloudron.io, we can test it .
I signed up at snowflake.com but tbh I couldn't make much sense of it. Can't even figure how to set up a database and generate access tokens.
-
Hi @girish, they are sent to the adress
-
@rapmac13160 thanks, the issue is https://github.com/snowflakedb/snowflake-connector-python/issues/2108 . I have left a note there. I am updating the package with a workaround - https://git.cloudron.io/cloudron/superset-app/-/merge_requests/4
-
@girish thanks for the investigation, let me know when ok.
-
@rapmac13160 new package is out
-
@girish it works perfectly fine thanks!
-
N nebulon marked this topic as a question
-
N nebulon has marked this topic as solved
-
Hi, just did the upgrade of Superset and the error is back
-
@rapmac13160 Not exactly the same but it seems very similar
-
R rapmac13160 referenced this topic
