From d5d8ff1539a6427ba347b442af658d7c5f46fb1b Mon Sep 17 00:00:00 2001 From: Yuki Kondo <57741286+yukiknd@users.noreply.github.com> Date: Thu, 8 Jul 2021 05:40:46 +0900 Subject: [PATCH] Fix off_chain_data to put data to off-chain database (#457) The off_chain_data sample fails to put data to the off-chain database. The application does not read fetched blocks because it uses the old interface of `addBlockListener()` to handle block events. This PR fixes the application to use the latest block listener and build the off-chain database. Signed-off-by: Yuki Kondo --- off_chain_data/blockEventListener.js | 21 +++++++-------------- 1 file changed, 7 insertions(+), 14 deletions(-) diff --git a/off_chain_data/blockEventListener.js b/off_chain_data/blockEventListener.js index 697cf8ef..43749c3b 100644 --- a/off_chain_data/blockEventListener.js +++ b/off_chain_data/blockEventListener.js @@ -116,20 +116,13 @@ async function main() { // Get the network (channel) our contract is deployed to. const network = await gateway.getNetwork('mychannel'); - const listener = await network.addBlockListener( - async (err, blockNum, block) => { - if (err) { - console.error(err); - return; - } - // Add the block to the processing map by block number - await ProcessingMap.set(block.header.number, block); - - console.log(`Added block ${blockNum} to ProcessingMap`) - }, - // set the starting block for the listener - { filtered: false, startBlock: parseInt(nextBlock, 10) } - ); + const listener = async (event) => { + // Add the block to the processing map by block number + await ProcessingMap.set(event.blockNumber, event.blockData); + console.log(`Added block ${event.blockNumber} to ProcessingMap`); + }; + const options = { filtered: false, startBlock: parseInt(nextBlock, 10) }; + await network.addBlockListener(listener, options); console.log(`Listening for block events, nextblock: ${nextBlock}`);