fix: Fix socket hang
Refer to https://github.com/Magickbase/neuron-public-issues/issues/389
/package Packaging for test is done in 8983636524. @yanguoyu
@Keith-CY Please prioritize this PR for review and merge because the related issue may block syncing.
Can not sync ,always show sync not start yet.
main.log
node log:
![]()
Hi, do you use the package from https://github.com/nervosnetwork/neuron/actions/runs/8983636524? I had no issues with socket hang after using this package. @silySuper
Can not sync ,always show sync not start yet.
main.log node log:
![]()
Hi, do you use the package from https://github.com/nervosnetwork/neuron/actions/runs/8983636524? I had no issues with
socket hangafter using this package. @silySuper
yes,i am using this package
Sorry for replying late. I wanted to let you know that starting from [email protected], you can now customize the fetch of the package @ckb-lumos/rpc using https://github.com/ckb-js/lumos/pull/574. You can achieve this by using the following code:
new RPC('https...', { fetch: globalThis.fetch })
I suggest trying out the NodeJS's native fetch, which is stable from Node@21, although Neuron is currently using [email protected].
Sorry for replying late. I wanted to let you know that starting from [email protected], you can now customize the fetch of the package
@ckb-lumos/rpcusing ckb-js/lumos#574. You can achieve this by using the following code:new RPC('https...', { fetch: globalThis.fetch })I suggest trying out the NodeJS's native fetch, which is stable from Node@21, although Neuron is currently using [email protected].
Hi, the Indexer constructor doesn't have the fetch option. And the Neuron throws socket hang at https://github.com/nervosnetwork/neuron/blob/v0.114.3/packages/neuron-wallet/src/block-sync-renderer/sync/indexer-cache-service.ts#L81.
Hi, the Indexer constructor doesn't have the fetch option. And the Neuron throws socket hang at
Lumos needs to allow for customizing the fetch function in the Indexer. Therefore, the node-fetch override is still necessary now
ckb node V114.0 to run v108 data can not sync,I tried ckb node v115 can sync
/package Packaging for test is done in 9072905547. @silySuper
@silySuper This PR should be merged first, it will block testing other PRs that use full-node synchronized
new data can sync ,but old data can not sync in my computer
new data can sync ,but old data can not sync in my computer
From your provider log, your old data has broken. I guess it's normal because your ckb node can't run success with old data.
socket hang fix verified

new data can sync ,but old data can not sync in my computer