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
This may already be fixed since we moved the default config to use 127.0.0.1 instead of localhost for the postgres host. Will leave this issue open for now and close it later if we don't hear anything new.
Sorry for a big delay. I finally managed to start it out.
I wonder what would be a point when we can decide if it works for macOS. I have successfully started it, logged in and had some debug logs identifying that postgres connection is working (I suppose).
[2024-03-12T17:54:41.130] [DEBUG] postgres -
UPDATE notifications
SET status = 'pending', updated_at = current_timestamp
WHERE id in (
SELECT id FROM notifications
WHERE status = 'new'
ORDER BY updated_at ASC
LIMIT 25
)
RETURNING *
[2024-03-12T17:54:41.151] [DEBUG] NotificationSender - No new notifications to send
@Pulko as long as you can start it, login via the webapp, I think that's fine and we can close this issue. What was missing here was someone with a Mac to test it. Thanks for taking the time :)
Connectivity between postgres container and the Gram API seems to fail.
The text was updated successfully, but these errors were encountered: