faucet | OpenFlow controller for multi table | Networking library

Essentially the only problem with your code is that you don't await the results from you async function comp(). map() will return an array of Promises and you will need to await all those promises which you can do by using Promise.all(). Promise.all() returns a Promise which will resolve when all Promises in the array passed to Promise.all() are settled. If you await that your children array will be propagated as you expect it to.

Here is your code with using Promise.all(). Because I don't have a suitable database ready at the moment I replaced all your asynchronous calls to the database with an asynchronous call to a function which has an artificial delay built-in so you can see how to actually await those and that the result is actually awaited.

Send ETH to your chainlink oracle address.

In response to this question, this issue was fixed in the xrpl4j codebase. See https://github.com/XRPLF/xrpl4j/issues/223 for more details.

Gas estimation error is a common error meaning that you don't have enough of "something" to send your transaction, maybe it's layer 1 (ETH) gas, or an ERC20 token like LINK (technically, erc677, but I digress...)

Whenever you work with a Chainlink feature that uses the request and receive method of using chainlink, you need to fund the consumer contract with LINK token.

The issue here is you sent LINK to the oracle address and not the address of your deployed contract.

If you copy the address of your deployed contract and send the LINK there, it should work for you.

You can try this one https://www.rinkebyfaucet.com/ you can get something like 0.1 Eth

https://rinkeby-faucet.com/ gives you 0.001

You are close with what you have so far. I've updated the contract a bit and included notes below. The main change was a new mapping to store the request id -> address. This lets the fulfillRandomness function update the correct address -> randomNumber mapping.

I see a few problems here.

It seems that the default value of maxPriorityFeePerGas was changed from 1.0 gwei to 2.5 gwei due to some incentive mechanism for miners.

Follow this issue for more detailed information.

Hence, if we don't set the maxPriorityFeePerGas parameter, the default value 2.5 gwei would larger than maxFeePerGas, which is 1.0 gwei we set and violate the rule.

We can solve this issue by either setting maxPriorityFeePerGas smaller than 1.0 gwei or changing maxFeePerGas larger than 2.5 gwei.

After a week I have finally found a solution.

First I tried reinstalling an older versions of node and npm, which did not fix my issue. Then I reinstalled the versions I stated above.

Somehow my project became corrupted, potentially because I updated Node/NPM while it was open. I then tried carrying over my code into a new create-react-app. After doing this I went to my package.json folder and came to find my final steps was with the version I have of react in my dependencies.

The version of react I was using ( "react": "^17.0.2") is not compatiable with a lot of the node modules I'm using in my project, which caused them to not be found in NPM.

I was able to fix this by reverting to an older version of react by updating to the following in my dependencies for my package.json file: