readable.js | A javascript library for readability analysis | Code Analyzer library

I have had the same issue. This is what I did:

1. I deleted the migrations folder as well as the dist folder
2. I ran npx mikro-orm migration:create --initial

After that, I restarted yarn watch and yarn dev and it worked for me.

Notice the --initial flag. I would recommend to check the official documentation. The migrations table is used to keep track of already executed migrations. When you only run npx mikro-orm migration:create, the table will not be created and therefore MikroORM is unable to check if the migration for the Post entity has already been performed (which includes creating the respective table on the database).

Ben does not use the --initial flag in his tutorial, he might have already ran it prior to the tutorial.

In order not to throw, use valudateStatus option:

Refering to this issue mentioned here: https://github.com/andris9/Nodemailer/issues/165

See if this helps, adding the tls cipher option to use SSLv3:

You haven't looked at what cURL is doing closely enough.

After reviewed your question, I did some R&D for the source URL which you have added the following is the possible solution to fetch images from the below URL.

Solution 1:

The below code is completely working fine, with the endless requests. I have reviewed the actual usda.gov site and review the headers and responses. I have used the Axios and verify that here the response received in-stream. I might not sure about canvas whether it will handle the stream response or not but, Axios works fine.

The reason to use Axios is that I have also tried with canvas somehow it failed to download an image. After studying the actual application and payload and tried with Axios which works fine and found most compatible.

That error is apparently coming from this line of code in the asar package's lib/filesystem.js:

I solve the error now, it is actually that you can create a user and password for a created database. And so I was using the username and password for the Atlas website and not that of the database itself. New that I created a new database and username and password for that database, I could use that database for my app and it worked fine!

But the steps that i used to arrive at the solution is not straigh forward. I actually started looking at how to implement a search engine for the mongoDB database and found a tutorial that ask me to connect via the mongoDB compass. I used the mongoDB compass to connect with the atlas username and password and it didn't work. but then I was like, this can't be possible. Then i removed the password completely and it seems to connect!.

Afterwards, I also tried again the Express tutorial and remove the password but it still give cannot have empty string password error. But then I was like I'm just gonna create a new account. and try it out. When I created the new account and the new database, they actually asked me to create a username and password for the new database! And this is where I found out that you also have a usernam and password for the created database.

I don't know what happen before, maybe it was cause I created the database long time ago and forget that a database uses a username and password as well.

SO it is solved and I'm moving on the 4th part of the tutorial.

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.

I finally solve my issue with this ssl code in my database file