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

Flaky: js-kernel-webview goBack()/goForward() fails with "a navigation is already pending"

Open Beginner friendly
#4,917 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@code-yeongyu is already working on this.

Since Oct 30, 2026.

  • #5054 by @code-yeongyu — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
bun, typescript
Domain
testing

Research direction

Start with packages/senpi-codemode/test/js-kernel-webview.test.ts and inspect the history-walk test named in the issue. Check how it observes navigation completion, then run that test repeatedly under load. Done means each back or forward step waits for its navigation-complete event and the test passes reliably.

Written by the indexing model from the issue text.

Description

Summary

packages/senpi-codemode test test/js-kernel-webview.test.ts > Bun.WebView from an eval cell > walks the default-backend view's history with goBack() and goForward() failed in hosted CI with Invalid state: a navigation is already pending.

Evidence

FAIL test/js-kernel-webview.test.ts > Bun.WebView from an eval cell > walks the default-backend view's history with goBack() and goForward()
Error: JavaScript parity cell failed: Invalid state: a navigation is already pending
Tests 1 failed | 16 passed | 2 skipped (19)

- PR #4620 touches no senpi-codemode file.

## Hypothesis (unverified)
The test issues goBack()/goForward() before the previous navigation settles; the parity cell needs to await the navigation-complete signal (not a timer) between history steps.

## Expected / acceptance
The history walk awaits each navigation's completion event before the next call; the test passes repeatedly under load.
Dominant language
TypeScript
Stars
500
Forks
155
Avg merge
22h 6m
Merged PRs (30d)
677

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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 code-yeongyu/senpi

All issues in code-yeongyu/senpi

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.