RaSi96 opened a new issue, #19925: URL: https://github.com/apache/superset/issues/19925
Hello team, This is my first issue ever here on GitHub, so please let me know if anything is amiss. I am a bit apologetic that my problems have something to do with this fantastic software, but my questions have been mounting over the last few days. The source of my issue here is that superset, as of the time of my writing, still for some reason doesn't support simple scatterplots. 1. Since bubble charts aren't a 1:1 replacement for a scatter for for me (they require 3 mandated variables?) [as recommended here](https://github.com/apache/superset/issues/7274), I decided to use a line plot and arrived at [PULL 17917](https://github.com/apache/superset/pull/17917). However, starting a non-dev superset instance using `docker-compose -f docker-compose-non-dev.yml` unfortunately still asks me for a temporal dimension - is this because I am running the non-dev branch or is it something else? 2. I then assumed that the dev branch would be a bit further ahead, so I updated my superset folder using `git pull origin master` and `docker-compose -f docker-compose-non-dev.yml pull` (both of which succeeded), but using `docker-compose -f docker-compose.yml pull` succeeds with everything except superset-websocket: **WARNING: Some service image(s) must be built from source by running: `docker compose build superset-websocket`. pull access denied for superset-websocket, repository does not exist or may require 'docker login': denied.** Running `docker compose build superset-websocket` succeeds, but retrying `docker-compose -f docker-compose.yml` pull returns the same error. 3. Deciding to go with whatever I have, using `docker-compose -f docker-compose.yml` up struck me with [ISSUE 7800](https://github.com/apache/superset/issues/7800). I followed the instructions there, but nothing worked: - changed the docker-compose.yml db.port from 5432:5432 to 5433:5432 and restarted, - changed the docker-compose.yml db.port from 5432:5432 to 5433:5432, commented out the entire superset-tests-worker section and restarted, - commented out the docker-compose.yml db.port line and restarted, - commented out the docker-compose.yml db.port line and the superset-tests-worker section and restarted, - tried using some of the settings from the non-dev.yml file and restarted; But each and every time superset or the container kept going into an error loop where one "image" would exit with error [1] and cause all the other images to fail with error [1], constantly printing out their error messages to my terminal until it freezes: - either my postgres instance can't be found at all (Are you sure the server is running at <IP> and listening on port 5432?), or I get the following messages: - **From superset_worker, superset_worker_beat, superset_app:** (psycopg2.OperationalError) could not translate host name "db" to address: Name or service not known - **From superset_db:** FATAL: database files are incompatible with server superset_db; DETAIL: The data directory was initialized by PostgreSQL version 10, which is not compatible with this version 14.2 (Debian 14.2-1.pgdg110+1). I am a bit adamant on not modifying my PostgreSQL instance because I have a few other applications for work and academia running locally and remotely that depend on it. Additionally if I may, I feel like these questions should really be addressed in the documentation for superset: 4. do the dev and non-dev branches differentiate between development of the superset software or development of data visualisations? 5. when I use openssl rand -base64 42 I get numbers and symbols, using this as my secret key doesn't work due to the symbols. Am I supposed to include them? 6. Another warning that keeps popping up is `the $CYPRESS_CONFIG variable is not set. Defaulting to a blank string.` when using `docker-compose -f docker-compose.yml up`. Is this something I should be setting? I have searched in docker-compose.yml as well as superset_config.py, but haven't found anything that's the `$CYPRESS_CONFIG`. 7. running superset in a docker container means using `localhost:5432` to connect to a postgresql database won't work even if psql is listening on the applicable port because `localhost` to the docker container means it only sees itself, not the actual host machine. Instead, pg_hba.conf should be configured to listen on the container's IP and superset should be given the host machine's ipv4/ipv6:5432 to successfully connect [see this article that helped me](https://vantakusaikumar562.medium.com/integrating-superset-with-postgres-database-using-docker-c773304ec85e). This little detail took me a rather surprising amount of time to digest :) Once again I apologise for bringing what seems to be an exhaustive list of problems with superset, but any help with these issues would be tremendously appreciated. I'm quite certain it's something very elementary that I'm overlooking, because updating my superset copy and using the non-dev branch is smooth as butter; only the dev branch causes an issue. I came across this project a week ago and have since thoroughly enjoyed using it whenever I can, and I'm very excited to see this project succeed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
