mistercrunch commented on issue #31890: URL: https://github.com/apache/superset/issues/31890#issuecomment-2644031731
@drummerwolli that's super key information, it points in the direction that there's something in the filesystem that's throwing off your environment. That's as opposed to something funky happening in your docker state for instance (bad images, ...) Trying to think through what might be in the filesystem... - a `.env` or `.env-local` file that's been modified (I think .env-local are ".gitignored") - similarly, something under `superset_config_docker.py` or similar - something that has to do with env vars (though that one should be easy to rule out by starting a new terminal/shell, or comparing the output of `env`) - something around numerous frontend build caches, running `npm run prune` will clean up `node_modules/` and other frontend-related caches Troubleshooting ideas: - compare the output of `env` - look for local superset_config getting loaded up - comparing the filesystem between the two cloned git repos (?) some sort of filesystem diffing tool or crafty shell commands - maybe some git-fu like running some `git clean` `git reset`-type commands to identify or clean up some local files that are git-ignored. -- 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]
