parseArgs | fluent DSL for parsing arguments | Parser library

I found the solution to the above error, you need to create a folder inside the project directory googleapis->google->api then need to add an annotation.proto file from grpc-gateway GitHub like mention in this link Grpc-gateway

Next need to add a path as shown below.

Seems it's an undocumented part of boost::program_options, I have a quick look at the implementation of boost::program_options and find there is a global variable which is used to control the behavior, so we come up with one line code hack:

I'm guessing you selected typescript as the language for your chaincode/contract, and it looks like it didn't transpile the typescript code to javascript. I would suspect there is a build option in the package.json, so try running npm run build in a vscode terminal in the directory your smart contract is stored (there should be a package.json file in that directory). If that fails because it can't find tsc then you need to run npm install first to install all the pre-reqs, then you should be able to run npm run build.

Once your smart contract has transpiled successfully (there should be in index.js file in the dist directory which is what the error message you posted is complaining about) you should be able to package the chaincode/contract again and install it (you may need to change the version number of your new package before you try to install it again and that's the version field in your package.json file.

It seems that there is an issue with Flipper. I am not using Flipper so i just commented it out.

1. cd ios
2. comment Flipper out from podfile:

1. run "pod deintegrate"
2. pod install
3. cd ..
4. npm run ios

I think the issue is with the test discovery.

... all of the test files must be modules or packages (including namespace packages) importable from the top-level directory of the project ...

You are specifying src as the top-level directory (python -m unittest discover -s tests -t src) and the tests are not importable in the src directory.

Database transactions and the number of available connections in a pool are not related in the way your question indicates. The connection pool will work regardless of your queries using transactions - it will hand them off as needed. When you start a transaction it ensures that the changes you make within the transaction are atomic and don't conflict with updates from outside the transaction. As you are not passing the transaction you create into the subsequent queries, it will hang waiting for you to commit or rollback the changes from the transaction. This is easier to read if you use async/await.

Try putting the args separately, like:

According to the documentation and the error message, the rtp method expects named arguments. According to the code and your error message, you are passing a single argument of type Closure[String] instead. You can conform to the proper usage by converting the argument to named arguments like the following:

Have you tried running npm uninstall -g knex?