Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Local end-to-end runs trip the API's login throttle

Open Beginner friendly
  • Is something wrong?
#1,835 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
70/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
node.js, playwright, typescript
Domain
authentication, backend, testing

Research direction

Start with testing/playwright.config.ts and the API's dev:test configuration described in the issue; trace how the test API receives its throttle settings. Compare raising or disabling the login limit for test runs with capping local workers. Done when local end-to-end runs avoid login throttling while production settings remain unaffected.

Written by the indexing model from the issue text.

Description

Area: Infrastructure Chore Difficulty: Low Priority: Medium

A local pnpm test:e2e run had 49 of 327 tests fail, every one on a login:

  • The api-client.ts fixtures got 429 ThrottlerException: Too Many Requests from
    POST /v1/auth/login.
  • Logins through the UI were bounced back to /auth/login.

The failures began partway through the run and hit every later spec that logs in, including static
pages such as About and Contact. Re-running the same 49 tests with --workers=2, they passed. CI is
unaffected because it runs one worker.

Cause

  • testing/playwright.config.ts sets workers: process.env.CI ? 1 : undefined with
    fullyParallel: true, so a local run uses half the machine's cores.
  • Each worker logs in for its own fixtures (adminToken, roleAccount), and some specs log in
    through the UI.
  • The API that Playwright starts (apps/api's dev:test) reads the normal .env, which has
    THROTTLER_ENABLED=true. LOGIN_REQUEST_THROTTLER_LIMIT falls back to 50 logins per 60 seconds
    per IP, and every worker shares one IP.

Possible fixes

  • Raise or disable the login throttle for the dev:test API only. This keeps local runs parallel and
    changes nothing in production.
  • Or cap the number of local workers.
Dominant language
TypeScript
Stars
119
Forks
19
Avg merge
4d 11h
Merged PRs (30d)
35

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DouglasNeuroInformatics/OpenDataCapture

All issues in DouglasNeuroInformatics/OpenDataCapture

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.