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

flaky: long-lists events feed p95 frame bound on WebKit

Open
  • Is something wrong?
#730 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
Half a day
Newbie friendliness
58/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
playwright, typescript
Domain
performance, testing

Research direction

Start with e2e/console/long-lists.spec.ts around lines 703 and 754, then inspect the WebKit frame-time measurements from CI run 39243173049. Check why p95 lands exactly at the 50 ms limit while Chromium and Firefox pass; done when the WebKit check handles this boundary reliably and the feed still shows no blank rows.

Written by the indexing model from the issue text.

Description

flaky-test

e2e/console/long-lists.spec.ts:703 › "the events feed scrolls through 5,000 events smoothly and the newest stays first" failed on WebKit only in CI run 39243173049 (PR #727). The PR does not touch this spec or the events screen.

  • The failing number: WebKit's frame-time p95 was exactly 50 ms, and the bound at :754 is toBeLessThan(50).
  • Why it looks like a boundary hit, not drift: WebKit's frame times come in steps (median 24, p95 50, worst 86 ms).
  • The other browsers: Chromium and Firefox passed the same test, with p95 16.8 ms and 17.1 ms.
  • The rest of the check: there were no blank rows.

Written by an agent.

Dominant language
TypeScript
Stars
20
Forks
2
Avg merge
8h 17m
Merged PRs (30d)
273

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 callstackincubator/simlock

All issues in callstackincubator/simlock

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.