krschacht
commented
1 month ago I've spent more time trying to debug this. I normally run my development environment within a simple Docker setup in my Mac. When I try running my app with this gem outside of Docker, then I don't get this exception. I have not been able to isolate any difference between the two which would explain it. I'll paste my Docker setup below in case you'd like to examine it.
In addition, when I am running my app within Docker, I get this exception the first time it attempts to send a turbo stream response. All subsequent times there is no exception, but there also is no successful streaming. If I kill the app and restart it, then I again get this exception on the first attempt and all subsequent attempts fail silently.
My Dockerfile
ARG RUBY_VERSION=3.2.3
FROM ruby:${RUBY_VERSION}-alpine AS development
RUN apk add --no-cache git build-base postgresql-dev curl-dev gcompat tzdata vips-dev imagemagick
ENV BUNDLE_CACHE=/tmp/bundle \
BUNDLE_JOBS=2 \
PORT=3000
WORKDIR /rails
COPY Gemfile Gemfile.lock .ruby-version ./
RUN --mount=type=cache,id=gems,target=/tmp/bundle \
bundle install
RUN apk add --no-cache postgresql-client
ENTRYPOINT ["/rails/bin/docker-entrypoint"]
CMD ["./bin/rails", "server", "-b", "0.0.0.0"]And my docker-compose
version: '3.1'
services:
postgres:
image: postgres:16
restart: always
environment:
POSTGRES_USER: app
POSTGRES_DB: app_development
POSTGRES_PASSWORD: secret
volumes:
- hostedgpt_pgdata:/var/lib/postgresql/data
healthcheck:
test: ["CMD", "pg_isready", "-U", "app", "-d", "app_development"]
interval: 1s
retries: 5
base: &base
depends_on: ["postgres"]
restart: on-failure:3
tty: true
build:
context: .
target: development
environment:
- DATABASE_URL=postgres://app:secret@postgres/app_development
- DEV_HOST=${DEV_HOST:-localhost} # Set if you want to use a different hostname
ports: ["3000:3000"]
volumes:
- .:/rails
- /rails/tmp
worker:
<<: *base
restart: on-failure:3
tty: false
ports: []
command: bin/rails solid_queue:start
volumes:
hostedgpt_pgdata:
lachappers
I changed my adapter from redis to this gem's
enhanced_postgresqland tried the app. At first it worked! I was excited but as I'm testing it more I get random failures with this exception:I'm trying to make sense of the source within
enhanced_postgresql.rbbut I don't have any ideas yet as to why this fails occasionally.