nghttp2 | nghttp2 - HTTP/2 C Library and tools | HTTP library

Try to use http instead of https, run this command to change the npm configuration.

npm config set registry http://registry.npmjs.org/

after that run

npm install -g @angular/cli

I'm not familiar with the SMTP feature of curl, but I know quite a bit about SMTP. curl apparently failed to authenticate. I haven't found a documentation about which authentication mechanisms it supports, but GSSAPI doesn't seem to be one of them (at least not with the options that you specified). (I know nothing about GSSAPI either.)

My guess about what went wrong is that you're not using TLS with curl (STARTTLS is still listed as one of the supported extensions). What I take from this documentation is that you should either specify --ssl or --ssl-reqd, or change smtp to smtps (smtps://mymailserver.com), which switches from Explicit TLS to Implicit TLS. The list of supported authentication mechanisms often changes once TLS is enabled and will likely include PLAIN afterwards.

Sooo after an nigth of trying to mess with SSL certificates, I discovered the only thing I needed to do, was to go to Insomnia, click on to the Application tab, select preferences and dismark the Validate certificates during authentication checkbox on the Security section.

Application>preferences

I knew I needed to dismark validate certificates(unde the Request and Response section)but i didnt know there was an checkbox just for auth requests.

This solution fits for my needs,but I am still curios how someone could do that by adding certificates in the collection settings of Insomnia, if thats possible for this case at all. God knows I tried.

Welp, I at least hope this post helps someone who is beggining on Insomnia as me.

I've been really racking my brain with this problem for a long time. After researching a lot I ended up discovering that in my case, this same problem was due to the network MTU.

I solved it by just lowering the MTU directly on my WSL distribution. If you don't use a linux distribution, you can just try to change it directly through the router. (Decreasing or increasing until it works)

Answering my own question.

Please see the discussion here https://github.com/pycurl/pycurl/issues/721

Apparently PyCurl does not play well with Python multi-threading when thread count is large enough, but works fine in single thread. For scenarios requiring concurrent API calls it is recommended to use pycurl.CurlMulti

Recommendation: https://github.com/pycurl/pycurl/issues/721#issuecomment-992632719

Test Code: https://github.com/pycurl/pycurl/issues/721#issuecomment-994475703

That error is from the Sentry script itself. You do have curl installed otherwise that script wouldn't have been downloaded and run in the first place.

The Sentry script is itself doing a check for curl and saying that it can't find it. Likely because it's doing the check with hash which is a Bash built-in command. You are running Alpine. Issues like this tend to crop up on Alpine and you really need to know what you're doing to get things to work.

I suggest run a custom version of the Sentry script yourself that's Alpine friendly or, my preferred option, base your image off of Ubuntu or Debian and not Alpine.

ok, looks like i found my solution here: https://gitlab.alpinelinux.org/alpine/aports/-/issues/12406

quote from Lyle Franklin:

I hit this error when trying to build a cross-platform ARM64 docker image from a AMD64 host. However, running docker run --rm --privileged linuxkit/binfmt:v0.8 or update-binfmts --enable prior to running the build seems to avoid the issue. My understanding Docker will try to use upstream QEMU if it is installed and registered with the kernel, otherwise Docker will fallback to using a built-in forked version of QEMU. The build error above only showed up for me with the forked QEMU.

So I will probably add docker run --rm --privileged linuxkit/binfmt:v0.8 && update-binfmts --enable to my pipeline file if I encounter the error again, for now running it once solved the issue.

There were three problems with my approach:

1. I needed to install buildx extension

Use the Buildpack's lifecycle directly inside your .gitlab-ci.yml here's a fully working example):