node_debug | HTTP based console and object explorer for node.js | Command Line Interface library

I'm new to N|Solid. I just got it running locally in my docker stack -- I can open the the console in my browser and it's successfully connecting to and reporting on my instances.

However, when I click "New Heap Snapshot" or "New CPU Profile" in the console I'm just met with a banner message that says e.g. "Working on CPU Profile: 0 of 1 complete". That message sits there indefinitely and the snapshot/profile never appears in the console.

In my docker logs when I trigger these via the console I see things like:

Application log

I have a project where I built several modules. After finding that nestjs has a lib cli command I ported all of them to use this style. Now my app can't find these modules when using npm run start:prod.

I am testing out a MEAN stack application. I have a Node.js backend which handles file upload (via fs/multer). However I'm receiving a 503 error when trying to hit it in production.

Locally everything is working fine. I am using Heroku's free tier; is that tier locked to not allow file upload?

The upload I'm trying currently (have tried several) is only 36kb (.png).

Went through my logs and found the 503-

2018-10-26T20:39:24.352297+00:00 heroku[router]: at=error code=H13 desc="Connection closed without response" method=POST path="/media/upload" host=www.example.co.uk request_id=5388711c-bc99-4e42-9dbd-7b645fbefb43 fwd="90.222.69.255" dyno=web.1 connect=1ms service=130ms status=503 bytes=0 protocol=http 2018-10-26T20:39:24.306975+00:00 app[web.1]: (node:20) [DEP0013] DeprecationWarning: Calling an asynchronous function without callback is deprecated. 2018-10-26T20:39:24.307037+00:00 app[web.1]: (node:20) [DEP0013] DeprecationWarning: Calling an asynchronous function without callback is deprecated. 2018-10-26T20:39:24.318818+00:00 app[web.1]: fs.js:113 2018-10-26T20:39:24.318822+00:00 app[web.1]: throw err; // Forgot a callback but don't know where? Use NODE_DEBUG=fs 2018-10-26T20:39:24.318824+00:00 app[web.1]: ^ 2018-10-26T20:39:24.318826+00:00 app[web.1]: 2018-10-26T20:39:24.318828+00:00 app[web.1]: Error: ENOENT: no such file or directory, mkdir './uploads/18'

I'm building an HTTP proxy in Node.js, which attempts to intercept HTTPS connections, using a self-signed certificate. I'm using a bare http.Server, instantiating my own tls.TLSSocket to upgrade sockets as required, and the functionality all works great when the CA is trusted by the client.

If the client isn't configured with the CA though, it obviously rejects the connection, complaining that there's a self-signed certificate in the chain.

That's all as it should be, but I'd like a way to detect that this has happened from the server-side, so I can prompt the user to correctly configure their client.

Is it possible to do this? It seems the TLS RFC (https://tools.ietf.org/html/rfc5246#section-7.2.2) has quite a few error alert messages about certificate rejections, which I would expect to cover this, but I can't see to see any debug info in Node about those even with NODE_DEBUG=tls.

Really I'd like to subscribe to TLS error alert events, so I can react to the various interesting cases in there directly. How can I do that?

I'd like to log which versions of TLS my Node app is using, if possible without changing any code.

I've tried both NODE_DEBUG=tls,http, and DEBUG=* which of course added lots of info to the logs, but nothing about the TLS versions in use.

Is this possible ?

So i am trying to initiliaze a node of a graph. The problem is that the value of the variable node->edges_capacity changes from 2 to some random int for no apparent reason, at least to my knowledge.

Moreover, when i use the debug mode of CLion, it prints 2 as expected!

Am i doing something wrong with malloc?