sequence.js | modular web3 stack and smart wallet | Cryptocurrency library

UPDATE

This bug exists on node v10.24.0, upgrade node to 12+ can solve it.

I have different result as I stated in the comment. So I examine different node versions and find that v10 is not handling the error correctly and return the same error you mentioned.

May I ask if you are using node 10?

If yes, can you try the next LTS node 12 or the latest node 16 to see if the problem is gone.

There is a typo. In the frontend code :

Your for loop is attempting to start a whole bunch of fs.writeFile() operations such that they are ALL trying to write to the file at the same time. This will clearly cause problems and conflicts. It doesn't really make sense to be calling fs.writeFile() over and over on the same file in a loop because each new write will just overwrite what was previously written, even if you sequence them one at a time.

In addition, you're passing two strings to JSON.stringify() where the second string would be interpreted as a replacer which is supposed to be either a function or an array, but you're passing a string. So, that doesn't make sense either.

Then, you appear to be calling addCount() recursively forever. That also doesn't make sense.

I honestly cannot tell exactly what you're trying to accomplish with your sequence.json file so I'll offer a small tutorial on writing a new item to that sequence.

Let's suppose you have a sequence.json that initially contains:

Well, I have been using a similar method. Except the fact that I don't insert all the rows at once but execute insertion of each row by executing query in each iteration of a loop.

Note: I'm using MVC server architecture

Here's the code.

1. Controller

In your code, you're calling response.end(), which will disconnected the event stream.

Normally, you would want to keep the event stream open indefinitely, unless you had a reason to close it. The client will disconnect itself if the browser tab is closed, connection is lost, etc.

Also, you might consider using an existing module like express-sse: https://www.npmjs.com/package/express-sse This can save you some time in implementing the protocol.

The waypoint sequence API has a restriction of 10 calls per day. If you have exceeded that, you will be able to make another call after 24 hours. Please take a look at some of the other restrictions on point 8

So you are getting this error as connection is not being established. As a good you need to check for any err and only if no error you need to call connection.query in callback function of pool.getConnection.

In your case you are getting PROTOCOL_SEQUENCE_TIMEOUT. By default, this module sets a 10 second timeout to opening a new connection. If your server and network needs more than 10 seconds to establish the connection, you can adjust that with the connectTimeout option.

error message indicate to error in '/app/routes/awards.routes.js' in line 20 there might be some thing wrong in making connection can you put the code of it

users_basket does exist

No: users_Basket exists, but users_basket doesn't (B ≠ b)!

Changing your query to SELECT * FROM users_Basket WHERE users_user_id=?; (with capital B) should fix it.

The reason why it works on your computer anyway is probably because your computer is using a case-insensitive file system, and database tables are stored as files!