nodes.js | nodes.js is a nodes/particles animation | Animation library

The problem is the TLS certs will have hostnames such as "peer0.org1.example.com" and yet you are declaring the remote host as "localhost" in the node files and as they don't match, the TLS connection will fail. The reason it works for the connection profiles is that they have the option to specify a hostname override.

As far as I know you don't have that option in the blockchain extension node files. But you can easily solve the problem by updating your hosts (/etc/hosts) file to map names such as peer0.org1.example.com, peer1.org1.example.com to localhost. Then you can change your node files to use the expected host names rather than localhost.

Thanks to some commentors, I've found that nesting with open() outside of iterparse() does the trick.

My antivirus program was likely the culprit, accessing the file each time it was closed, which occasionally caused an access conflict on the next file open operation.

I didn't like opening and closing the file for each element because of the operation cost, and I originally had parsed the XML from within the file open when I was writing to a single file. But, when I decided to write to multiple files, I didn't want to parse the XML over again for each JSON file I wanted to write from it.

Seems like a no-brainer now, but nesting file opens works and saves compute. It might build up the indents if you want to write a lot of files, but c'est la vie.

CBC mode generally (including this case) needs padding, and your encryption uses padding where only the last byte specifies the length and the other bytes are random. node-forge evidently accepts this, but nodejs builtin crypto uses OpenSSL (specifically the EVP_Decrypt* API, as you can see in the error message) which by default implements PKCS5/7 padding where all bytes must contain the length.

OpenSSL, and crypto, does have an option to not do any padding and unpadding at all, leaving you to do it yourself. You can use that option here as follows:

list.append returns None since it is an in-place operation, so

I have no idea what's going on with the server, but I am going to concentrate on how you can recover from parsing a stream of independent JSON blocks. The issue is you are probably getting malformed data which Newtonsoft.Json can not recover from. Once that happens, you are out of luck. Not even adding error handling to your routine will work in this case. So, what you should consider is something like this:

There is no json parser I know that has an IAsyncEnumerbale deseralizer (yet)

However, we should be able to do this with a regular iterator as long as you don't dispose the stream

There are duplicate paths in your API definition, for example:

You can simply use + operator: