Automattic / Automattic/matrix-env

go-neb doesn't start working when I start containers again

Open
#4 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Shell
Stars
21
Forks
5
PR merge metrics
No merged PRs in 30d

Description

Starting my day, when I start those containers back up again using `docker compose up` everything starts as it should except the go-neb bot doesn't seem to do anything. Only when I stop containers once and start them again, it starts responding to events. Perhaps a timing issue of some sorts?

I should mention that I am using an external go-neb instance and not the one in this repo.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the restart sequence with `docker compose up`, using the external go-neb instance described in the issue. Inspect the Compose service startup and readiness ordering; done means the bot responds to events after the first container restart without a second stop/start cycle.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker-compose
Domain
devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.