Fetch Error

✗ HTTP_RPC_ENDPOINT=http://office.nkg:20000 npm start

> fork-off-substrate@1.0.0 start /home/xavier/Documents/paritytech/fork-off-substrate
> node index.js

We are intentionally using the HTTP endpoint. If you see any warnings about that, please ignore them.
2021-03-02 12:18:28        API/INIT: Api will be available in a limited mode since the provider does not support subscriptions
2021-03-02 12:18:28        API-HTTP: HTTP Provider does not have 'on' emitters, use WebSockets instead
2021-03-02 12:18:28        API-HTTP: HTTP Provider does not have 'on' emitters, use WebSockets instead
2021-03-02 12:18:28        API-HTTP: HTTP Provider does not have 'on' emitters, use WebSockets instead
2021-03-02 12:18:29        API/INIT: RPC methods not decorated: balances_usableBalance, headerMMR_genProof, staking_powerOf
Unable to resolve type Status, it will fail on construction
Unknown signed extensions CheckEthereumRelayHeaderParcel found, treating them as no-effect
Unknown types found, no types for Status
Fetching current state of the live chain. Please wait, it can take a while depending on the size of your chain.

/home/xavier/Documents/paritytech/fork-off-substrate/node_modules/node-fetch/lib/index.js:272
				return Body.Promise.reject(new FetchError(`invalid json response body at ${_this2.url} reason: ${err.message}`, 'invalid-json'));
				                           ^
FetchError: invalid json response body at http://office.nkg:20000/ reason: Cannot create a string longer than 0x1fffffe8 characters
    at /home/xavier/Documents/paritytech/fork-off-substrate/node_modules/node-fetch/lib/index.js:272:32
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:94:5)
    at async HttpProvider.send (/home/xavier/Documents/paritytech/fork-off-substrate/node_modules/@polkadot/rpc-provider/http/index.js:149:20)
    at async main (/home/xavier/Documents/paritytech/fork-off-substrate/index.js:65:17) {
  type: 'invalid-json'
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! fork-off-substrate@1.0.0 start: `node index.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the fork-off-substrate@1.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/xavier/.npm/_logs/2021-03-02T04_22_46_261Z-debug.log

[maxsam4]

@AurevoirXavier Delete ./data/storage.json and try running FORK_CHUNKS_LEVEL=2 HTTP_RPC_ENDPOINT=http://office.nkg:20000 npm start. It splits the the download into even smaller chunks.

ps Do you have an Idea how large your blockchain’s state is?

[maxsam4]

OMG. But my machine only got 4M upload bandwidth. Do you have to download 500mb+ data?

Lol, yes. I need to download the full state of your blockchain. Perhaps it might be best that I just make the changes and test against our blockchain and then you can test against yours on your own.