vice.js | Versatile Commodore Emulator for JavaScript | Emulator library

Replace this line:

if you are using express for the server, then to read JSON data you need to add

The precise location of error properties is not specified. In some environments, it's on the error object itself - in some, it's on the prototype, or is a getter, or something like that.

JSON.stringify will only iterate over enumerable own properties. In Chrome, the .message property is not enumerable, so it won't be included when stringified:

All configurations seems good, however you have to upgrade explorer version to be compatible with hyperledger fabric version.

So please use v1.1.4 instead of v1.1.1

Also make sure that you have mounted crypto config correctly, try to access this path inside the container /tmp/crypto/peerOrganizations/acme.com/tlsca/tlsca.acme.com-cert.pem

Try to change tlsCACerts path to use peer tls ca.crt /tmp/crypto/peerOrganizations/acme.com/peers/peer1.acme.com/tls/ca.crt

You have mentioned that the same configurations works with hyperledger fabric v2, if you have tried it locally not on the same server so I please disable the firewall on the server and give it a try

To check if you can reach domain and port please try this

cat > /dev/tcp/peer1.acme.com/7051

Check this https://support.bluemedora.com/s/article/Using-Bash-to-test-if-a-TCP-port-on-a-remote-system-is-open

Please try this:

ng update @angular/cli

npm install

the error means you have sent data to the client at least twice. If you use express, it means you have called res.send (or equivalent res.render) multiple times.

therefore you have not given the right code sample in your question for me to help more.

Seems like your environment supports the top-level await proposal. The proposal is currently at stage 4 which means "finished" and can be included in the specs officially. But support may still vary.

Quoting the proposal:

Top-level await lets us rely on the module system itself to handle all of these promises, and make sure that things are well-coordinated. The above example could be simply written and used as follows:

You're not calling the created function that's why it's not working here!

Script tag:

Finally I was able to fix it.Looks like route on the tabs were not setup correctly. Here's what I changed:

1. Moved tabProps to compute() to update route on the fly.
2. Fired an event from child component to update the route which gets caught by the parent that updates the route.
3. I did not use this.$route to update the tab route dynamically since I wanted to retain the state of the second tab if a child node is selected on the tree but the user switches to the first tab which contains data for the parent. (I know its confusing). So its like a file explorer where first tab shows details of the folder and second tab shows details of the selected child in that folder.

Tab states are now maintained.

Here's the relevant code (not the most efficient but it works). Hopefully, it helps someone facing similar issue.

route.js