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

Two web host product paths fail end to end

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
playwright, swift, typescript
Domain
backend-api-design, testing

Research direction

The failing tests are in tests/e2e/unary.spec.ts and tests/e2e/subscription.spec.ts. Start by running the end-to-end job locally to reproduce the timeouts. Examine the iframe communication and the stream entry locator in the web host's product path. Check the host's iframe source at localhost:3000 and the data-testid='stream-entry' element. Done when both tests pass and the e2e job is re-enabled.

Written by the indexing model from the issue text.

Description

The end-to-end job that runs the playground inside the web host reports two failures when it is allowed to run. Both time out waiting for a stream entry inside the host's iframe, so a call reaches the product and nothing comes back.

[chromium] › tests/e2e/unary.spec.ts:5:3 › unary call › feature_supported runs to completion without login
[chromium] › tests/e2e/subscription.spec.ts:5:3 › subscription › connection_status delivers an event and completes

Locator: locator('iframe[src^="http://localhost:3000"]').contentFrame().locator('[data-testid="stream-entry"]').first()
Error: element(s) not found

Two of the four tests pass, so the harness itself works: the submodule checks out, dotli and the playground build, and Playwright runs. The failures are in the product path rather than the setup.

Evidence: https://github.com/paritytech/host-rust-core/actions/runs/35781235590

These have been invisible since the job was disabled on 8 May. #910 carries the change that re-enables it and stays in draft until these pass, because e2e is in the required set and would otherwise block every pull request.

Blocks #685.

Dominant language
Swift
Stars
10
Forks
3
Avg merge
1d 9h
Merged PRs (30d)
211

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 paritytech/host-rust-core

All issues in paritytech/host-rust-core

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.