libuv | Cross-platform asynchronous I/O | Socket library

Yeah, plus 1 to this issue. OP, the --skip-broken flag will only temporarily fix your currently running servers though. If you're baking any new AMIs or spinning up any new EC2s with Terraform, CDK, etc, that --skip-broken flag won't work as its not available as part of the aws cloud.init script. This will cause any new AMI or EC2 creations to timeout and fail.

One potential work around is to try compiling libuv directly from source as > 1.39 sadly isn't currently available from any linux distro.

After a few days I was able to find the solution

Firstly, my code needed to be fixed to correctly call the params needed with the proper name

File IO in nodejs uses a thread pool. By default, there are 4 threads in the pool.

When some Javascript calls a file operation such as fs.open() in nodejs, the call is routed to some native code within the libuv library in the nodejs implementation. That code adds the specific file operation to a queue of items waiting for an OS thread. If an OS thread is immediately available, then that OS thread is given the task of carrying out the file operation and then the original libuv function returns which returns back to the original Javascript and nodejs continues running other Javascript.

Then, sometime later the thread finishes the file operation and has a result. It inserts an event into the nodejs event queue with the completed result and the original callback passed with the original file operation.

When nodejs has finished executing any other Javascript it was running, it pulls the next event from the event queue and calls the Javascript callback associated with that event and passes it the data associated with the event. This triggers the Javascript callback that was originally passed to fs.open() to get called.

If, in the second step above, there were no available threads in the thread pool, then the task is added to a queue and libuv immediately returns control back to nodejs so it can run other Javascript. Sometime later when one of the existing threads in the pool completes and finishes its work of adding an event to the event queue, then it will pull the next item out of the the thread pool queue, give it the now-available thread and let it start running its operation.

In this way, all file operations appear to be non-blocking and asynchronous from the Javascript side of things. They either get started immediately if there is an available thread in the thread pool or they sit in a thread pool queue until a thread is available. That part is invisible to the Javascript side of things. Either way, the operation is initiated or queued and control immediately returns back to nodejs to continue running other Javascript. And, either way, the operation completes sometime later and the Javascript callback associated with the file operation gets called via the Javascript event queue. This provides the asynchronous, non-blocking, event-driven mechanism that nodejs uses for all file I/O.

This command: gcc file.o -o a.out does not link to a python library.

You need to add (append) -lpython3 and possibly -L${CONDA_PREFIX}/lib/python3.9 to it.

Unfortunately it turned out - that Libcurl multi_socket mode cannot work with Windows IOCP.

As you said, uvloop is written in Cython (equivalent to c) on top of libuv.

Writing code in Cython is almost guaranteed to give you a noticeable speed boost which is exactly what's happening here. No need for any other difference. It's much like numpy doing operations faster than writing normally in Python.

For your other question: The difference between asyncio and asyncio-streams is that streams are built on top of the basic asyncio.

Asyncio uses transports and protocols, the first responsible for writing to the socket, and the second for handling data received by the socket.

Streams are simple constructs built on top of both, and have an easier to use interface that mimics regular files or sockets.

Hm, it appears Homebrew tried to upgrade c-ares from version 1.17.1 to 1.18.1 but failed for some reason. Try running brew upgrade c-ares before brew install node.

If that doesn't work, what is your output for brew list --versions c-ares? Perhaps you have multiple c-ares versions installed. If that is the case, run brew unlink c-ares to unlink the old version and then brew link c-ares to link the newer one. The old version can be uninstalled by running brew cleanup c-ares

Node is a program where its C/C++, static libraries it uses (such as libuv) and various other resources it uses are compiled into node.exe (on Windows). So, the things you're asking about are inside of node.exe.

They are not separately available in your file system when you just install the runnable version of nodejs.

If you cloned the source repository and built it yourself, you'd have all the components in your local source repository that are then compiled into node.exe. But, if you install an already built version of nodejs, then you will just get the binary executable files that already have the components built into them.

Build tags in you environment.yml are quite strict requirements to satisfy and most often not needed. In your case, changing the yml file to