-
-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot add new connections #176
Comments
You can't remove a data-source if a widget is using it. This is the first error. for the second one, I guess you didn't start any database container. NOTE: This compose does not containers with test databases, they are commented and not started" You need a running instance of one of the supported data store. So,
|
Thanks for the hint for the widget! After removing it, then I could remove also the OrientDB pre-defined connection. However, I have still problem for adding a new connection. I've followed the documentation and tested with different DBs:
|
Just tested. I'm able to create datasources without any issues. Some questions:
|
Yes, I have an running instance of CosmosDB. As described above with both CosmosDB and local OrientDB3 (provided in this repo and started with See below the log of the arcade analytics process: |
Hi, I found the problem. I logged in as "user" with password "user", which seems to be able to create data sources, but strangely cannot see them (write-only behavior). Whereas, when logged-in with "admin", then I could both create and see data sources. |
moved here because it looks related to the web application, instead of the connectors |
Hello,
"arcade-standalone" is currently unusable for two problems.
First: I could not add new datasource connections. Even when the test connection works, then when I hit the save button nothing is saved. When I try to remove the pre-existing DemoDB (OrientDB) connection I get the following error:
Second: The connection check is another problem. I managed to get OK from test connection only for a CosmosDB instance, but not for Janus and OrientDB. E.g. for Janus I get the following error
All the config is set as in the docs. What might be the problem?
The text was updated successfully, but these errors were encountered: