You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I confirm this is a bug with Supabase, not with my own application.
I confirm I have searched the Docs, GitHub Discussions, and Discord - just the public docs and discussions.
Describe the bug
Stopping the postgres-meta container takes more than 10 seconds every time and prints a warning, unlike the postgres and postgrest containers, which stop immediately and print nothing.
To Reproduce
On a clean Fedora 39 system without other containers, install podman and podman-compose, then run the following script as user. The postgrest service without access control is there to show that the issue doesn't affect it, only postgres-meta.
The postgres-meta container should take at most 1 second to stop, like postgrest and postgres, and print no warning.
Screenshots
Relevant part of the output of the commands run by the script above:
podman stop -t 10 postgres-meta-slow-stop_meta_1
WARN[0010] StopSignal SIGTERM failed to stop container postgres-meta-slow-stop_meta_1 in 10 seconds, resorting to SIGKILL
postgres-meta-slow-stop_meta_1
exit code: 0
System information
OS: Fedora Silverblue 39
podman-compose version: 1.0.6
podman version: 4.8.0
Additional context
The Silverblue clarification isn't relevant here I think, on Debian the stop was also slow. But the reason I use the container at all, rather than the npm package, is that installing the dependencies of the npm package throws an error on Silverblue: launchql/libpg-query-node#25
The text was updated successfully, but these errors were encountered:
Bug report
and Discord- just the public docs and discussions.Describe the bug
Stopping the postgres-meta container takes more than 10 seconds every time and prints a warning, unlike the postgres and postgrest containers, which stop immediately and print nothing.
To Reproduce
On a clean Fedora 39 system without other containers, install podman and podman-compose, then run the following script as user. The postgrest service without access control is there to show that the issue doesn't affect it, only postgres-meta.
Expected behavior
The postgres-meta container should take at most 1 second to stop, like postgrest and postgres, and print no warning.
Screenshots
Relevant part of the output of the commands run by the script above:
System information
Additional context
The Silverblue clarification isn't relevant here I think, on Debian the stop was also slow. But the reason I use the container at all, rather than the npm package, is that installing the dependencies of the npm package throws an error on Silverblue: launchql/libpg-query-node#25
The text was updated successfully, but these errors were encountered: