paritytech/hardhat-polkadot

process in port 8000 continues running after kill when using forking

Open

#278 opened on Aug 14, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)TypeScript (10 forks)auto 404
P2 - Mediumgood first issue

Repository metrics

Stars
 (16 stars)
PR merge metrics
 (PR metrics pending)

Description

🔄 Reproduction Steps

  1. Following hardhat.config
networks: {
        hardhat: {
            polkavm: true,
            docker: true,
            forking: {
                url: "https://testnet-passet-hub.polkadot.io",
            },
        },
        localNode: {
            polkavm: true,
            url: `http://127.0.0.1:8545`,
        },
    },
  1. npx hardhat node
  2. Ctr+C
  3. npx hardhat node

🤔 Expected Behavior

Server listens on 8000 Server listens on 8000

😯 Current Behavior

Server listens on 8000 Server listens on 8001

Contributor guide

Research direction
Check how the forking process is spawned and why it does not terminate properly on SIGINT. Look for missing signal forwarding or orphaned child processes.
Tech stack
typescriptnodejs
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
githardhatnode.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75