Postgres: remaining cross-instance and full-suite tests from #105
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- docker-compose, github-actions, postgresql, sqlite, typescript
- Domain
- authentication, ci-cd, database, infrastructure, testing
Research direction
Read issue #105 for the exact PG-xx case descriptions, then inspect the existing Postgres tests and CI configuration added in PR #164. Start by identifying which deferred cases are already covered and how the app, queue, and Docker Compose tests are run. Done means the listed cross-instance, full-suite, time-zone, and large-topology cases are tested as described, with each test retaining its #105-PG-xx id.
Written by the indexing model from the issue text.
Description
Follow-up of #105 (PR #164). PR #164 adds Postgres support, the Postgres job claim, the database lock for the integration sync (PG-12) and the large-topology example. These test cases of #105 were deferred and are tracked here:
- PG-04 Run the full app test suite against Postgres in CI (today only the new Postgres tests run there).
- PG-08 Parameterise the queue suite so it runs against both SQLite and Postgres.
- PG-10 Two app instances share the webhook secret (state lives in
secrets; prove it with a two-instance test). - PG-11 Rate limits are shared across instances (state lives in
rate_limits; two-instance test). - PG-15 Time zones: timestamps written and read identically on Postgres and SQLite.
- PG-17 / PG-18 Docker ops smoke test of
compose.large.yml(two app replicas, two runners, Postgres) in CI. - PG-19 A session created on one instance is valid on the other (state lives in
sessions; two-instance test).
The exact case descriptions are in #105. Each case keeps its id (#105-PG-xx) in the test comment.
Out of scope: anything already merged with #164.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 1
- Avg merge
- 1h 18m
- Merged PRs (30d)
- 186
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ExpidetGames/code-reviewer
-
area: app type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
ExpidetGames/code-reviewer#308 ·
Maintainers usually reply within 1 day
-
type: docs
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ExpidetGames/code-reviewer#94 ·
Maintainers usually reply within 1 day
-
area: app post-mvp type: feature
Difficulty 5/5 Over a week Newbie friendliness 12/100
ExpidetGames/code-reviewer#339 ·
Maintainers usually reply within 1 day
-
area: runner post-mvp type: feature
Difficulty 5/5 Over a week Newbie friendliness 18/100
ExpidetGames/code-reviewer#338 ·
Maintainers usually reply within 1 day
-
area: runner post-mvp type: feature
Difficulty 5/5 Over a week Newbie friendliness 12/100
ExpidetGames/code-reviewer#337 ·
Maintainers usually reply within 1 day
All issues in ExpidetGames/code-reviewer
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
aws/agentcore-cli#2606 ·
Maintainers usually reply within 1 day
-
ai-driven-qa bug Cosmetic
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
ai-driven-qa bug claude Minor
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
linagora/twake-mail-admin#301 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
reproduced
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
anomalyco/opencode#56038 · 1 comment ·
Maintainers usually reply within 1 day