Is Google Chrome redirecting you to onelogin whenever you try to login into any Google account? This is how to fix it:
A new macbook pro comes installed with bash version 3. I needed to install bash 4 to be able to use the bash debug vs code extension. To do this run
brew install bash
once its done you will need to edit /etc/shells file so that it looks like following:
WITSC02X6385JGH:temp sjain68$ cat /etc/shells # List of acceptable shells for chpass(1). # Ftpd will not allow users to connect who are not using # one of these shells. # 4.x of bash /usr/local/bin/bash # 3.x of bash /bin/bash /bin/csh /bin/ksh /bin/sh /bin/tcsh /bin/zsh
showing how to add an attribute named manufacturer and set its value to true. file helper.js in balance-transfer app. see https://fabric-sdk-node.github.io/release-1.3/FabricCAServices.html#register__anchor
later on you can check this attribute as follows in your chaincode:
Goto Code -> Preferences -> Settings -> TSLint and uncheck Enable
for bonus also uncheck Javascript > Validate: Enable
There are several problems you will run into. First problem is this
you won’t be able to run ts-node after npm installing it. To fix it modify the PATH environment variable
PATH=$PATH:./node_modules/.bin
Next problem is when you try to run ./runApp.sh it will give
============== node modules installed already =============
(node:714) DeprecationWarning: grpc.load: Use the @grpc/proto-loader module with grpc.loadPackageDefinition instead
However that is plain wrong. In fact you will need to have Node v8 installed (nothing more and nothing less) since the async-await was introduced only in v8 of Node.
The gossip service outputs very verbose and useless logs in Fabric. These messages can be seen if one tries to view the logs of a peer container.
How can one get rid of them? Today i tried 2 ways none of which worked.
Method 1: This was based on what I read on the official documentation
so I added it to the base.yaml file as follows:
command: peer logging setlevel ^gossip error && peer node start
this actually caused some problem at runtime and the container did not start properly. Then somewhere on stackoverflow I read to use bash – c “” so I tried that:
command: bash -c "peer logging setlevel ^gossip error && peer node start"
That also did not work. Then somewhere I read not to use bash but use /bin/bash. So I tried that and no surprise that too did not work. Note to self: try running the command from the docker container of the peer and see if it works then
Method 2: This method is based on what I read here. Accordingly I added CORE_LOGGING_GOSSIP=WARNING in base.yaml and that too did not work.
11/30/18: I have now tried all possible permutations and combinations. using bash, /bin/bash, changing the order of commands, running peer logging setlevel ^gossip error from inside the peer container and none of the options will silence the gossip debug logs. So frustrated with HL Fabric.
below is error message when I try to run peer logging setlevel ^gossip error from inside the container:
screenshot of base.yaml (have tried all possible permutations)
Making this note to remind myself of the constant problems I keep running into with HL Fabric. Should have chosen Quorum to develop my blockchain.
How to debug typescript app in VS Code?
2. cd to the directory where app.ts is located and from there run
$ /usr/local/bin/node --nolazy -r ts-node/register --inspect-brk=49528 app.ts
It should display a message
Debugger listening on ...
3. In VS Code go to View -> Debug and click on green button to launch Attach
4. The terminal should now display a message saying
Debugger Attached.
5. The debugger is attached now but the execution is paused. In VS Code click on the button to continue the execution (or press F5)
6. That’s it you should be able to debug now
Make sure the loaded scripts window shows your code.
In debug console you should be able to debug variables
