Trying to delete a plugin, but receive an error requiring authentication "login api:mrsm". Can not recall setting credentials for this connector and unable to locate reference for default credentials in docs.

.

I'm opening this issue as a note to myself and others who are using Dockerized Meerschaum. Changes to the virtual environment system in v1.1.0 mean that dependencies are more strictly enforced to be installed within the specified virtual environment. The behavior of the latest and full images relies on installing all of the dependencies in the user environment, so this change reverts its behavior to the same as the minimal image.

A temporary workaround for this is to persist a docker volume mounted at /meerschaum (the container's root), and run the command mrsm upgrade packages -y which will install everything into the virtual environment.

I will be working on a more permanent solution in the coming days, mainly considering a package as "not installed" when it's detected in the user environment if it fails the version check. Admittedly, I added the stricter behavior to avoid having to go the long way around and verify the version, but now I realize there's no easy way to get around that.

Expect a patch in v1.1.1 to be out soon!

Currently, datetime bounds are set to None if a datetime value cannot be determined from an incoming dataframe. To avoid this behavior, this logic needs to be broken up into several checks: one for if a datetime index is set, another for if the dataframe is empty, and finally if the dateframe contains the datetime column.

Primary issue appears to indicate that MRSM and TimescaleDB are not able to communicate. I have verified that mrsm_db_1 is running in Docker.

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
c3a41726b5b9 timescale/timescaledb:latest-pg13-oss "docker-entrypoint.s…" 12 hours ago Restarting (1) 25 seconds ago mrsm_db_1

Previous communication
"You can use the preconfigured docker-compose stack, just run mrsm stack up -d db to get TimescaleDB up. You can first set the password with mrsm edit config before running mrsm stack up -d db or you can change the password later (default is username: mrsm and password: mrsm)."

Note: there is no mrsm user on the system only my azureuser

Distributor ID: Ubuntu
Description: Ubuntu 20.04.3 LTS
Release: 20.04
Codename: focal

Setup/Install Notes:

1. Setup DOCKER on Azure VM (needed to add "azureuser", sudo usermod -a -G docker azureuser)
2. pip install meerschaum (mrsm was installed in /home/.local/bin and needed to add to PATH)
3. mrsm stack up -d db
4. test mrsm install "$mrsm" successfully starts mrsm session (everything looks good)
5. mrsm show pipes generates the following error:

⚠️ (psycopg2.OperationalError) could not connect to server: Connection refused
Is the server running on host "localhost" (127.0.0.1) and accepting
TCP/IP connections on port 5432?
(Background on this error at: https://sqlalche.me/e/14/e3q8)
warn(str(e))
💢 Failed to execute 'show pipes' with exception:
' 🛑 (psycopg2.OperationalError) could not connect to server: Connection refused
Is the server running on host "localhost" (127.0.0.1) and accepting
TCP/IP connections on port 5432?
(Background on this error at: https://sqlalche.me/e/14/e3q8)'.
Run again with '--debug' to see a full stacktrace.

Hi Bennett! I see on your dev branch that you have a header for a quick start, but no content there. Want some help writing something here? What's a minimal usage of this package look like? :)