[telegram] <Sara> Hi! So, they checked the error - it is definitely a connection error, it's set up here in the code of the library (re @exru: According to error logs the problem lays in /lib/queries/index.js:36:20
at Timeout._onTimeout (/var/www/nhterminal/node_modules/iroha-helpers/lib/queries/index.js:36:20)
at listOnTimeout (node:internal/timers:559:17)
at processTimers (node:internal/timers:502:7))
- try to establish connection with telnet(or nc).
- You can try to run iroha-cli or make telnet connection from the same VM where iroha is running to be sure that connection can be established
- check firewall options if it is used
- check packets are transferring from library to iroha with wireshark or smth similar
[telegram] <exru> I've used next code:
npm install is-port-reachable
import isPortReachable from 'is-port-reachable';
console.log(await isPortReachable(50051, {host: 'localhost'}));
result is true (re @Alexander: 1. check port redirection if client and iroha on different VM or in container
- try to establish connection with telnet(or nc).
- You can try to run iroha-cli or make telnet connection from the same VM where iroha is running to be sure that connection can be established
- check firewall options if it is used
- check packets are transferring from library to iroha with wireshark or smth similar)
- try to establish connection with telnet(or nc).
- You can try to run iroha-cli or make telnet connection from the same VM where iroha is running to be sure that connection can be established
- check firewall options if it is used
- check packets are transferring from library to iroha with wireshark or smth similar)
[telegram] <exru> exru@524889-cu15907:~$ telnet 127.0.0.1 50051
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
▒@@ ?
connected too (re @Alexander: 1. check port redirection if client and iroha on different VM or in container
- try to establish connection with telnet(or nc).
- You can try to run iroha-cli or make telnet connection from the same VM where iroha is running to be sure that connection can be established
- check firewall options if it is used
- check packets are transferring from library to iroha with wireshark or smth similar)
- try to establish connection with telnet(or nc).
- You can try to run iroha-cli or make telnet connection from the same VM where iroha is running to be sure that connection can be established
- check firewall options if it is used
- check packets are transferring from library to iroha with wireshark or smth similar)
[telegram] <exru> According https://iroha.readthedocs.io/en/main/develop/libraries/javascript.html
I start my script from console node script.mjs=========
Maybe error is in here? How I would to start the script?
But still:
import isPortReachable from 'is-port-reachable';
console.log(await isPortReachable(50051, {host: 'localhost'})); // ok
[telegram] <exru> But still:
import isPortReachable from 'is-port-reachable';
console.log(await isPortReachable(50051, {host: 'localhost'})); // ok (re @exru: According https://iroha.readthedocs.io/en/main/develop/libraries/javascript.html
I start my script from console node script.mjs
Maby error is in here? How I would to start the script?)
[telegram] <Sara> Forwarded from Hyperledger Iroha news: 👀 Very late reminder: community meeting in 10 minutes!
Just enough time to grab a cuppa and join us for Iroha updates: https://zoom.us/my/hyperledger.community.3
Password: 475869
[telegram] <Sara> Forwarded from Hyperledger Iroha news: By the way, if you haven't read it yet, Iroha Team wrote a blogpost about Iroha 2 for Hyperledger: https://www.hyperledger.org/blog/2022/05/19/new-long-term-support-version-of-hyperledger-iroha-creates-on-ramp-for-v2-adoption
Take a look to learn more about why and how we are creating Iroha 2!
function main() {
var client = new hello_proto.Greeter('localhost:50051',
grpc.credentials.createInsecure());
client.sayHello({name: 'you'}, function(err, response) {
console.log('Greeting:', response.message);
});
} (re @Stepan: yes, this way was considered, but I would like to force ERP to run an external script for connect.)
Hello. next step for newbie✋ I deal with the installation of gRPC on a client machine with ERP under win10 and check if there is already an installation in ubuntu on the server side. for this, it was necessary to install node.js on Win10 in order for PowerShell to execute the npm install grpc command, and apparently, you also need to run spare parts from the npm i iroha-helpers framework.
It is a one time paid-freelancer based project. If you are interested, kindly revert back with your contact details.
Thank you.
"target": "esnext",
"module": "commonjs",
...where should it be located in win10? (re @♌︎ Leo: This is a JS issue not an iroha issue. import is ES6, normally you'll need to use a transpiler like babel/typescript to use ES6 features in node.js. the iroha example uses ts.)
[telegram] <Stepan> The bug was fixed by updating the nearest parent package.json file with the following entry:
{
"type": "module",
...} (re @Stepan: #gRPC #nodeJS
Hi. JS script when executed gives an error on import grpc from ('grpc'); "SyntaxError: Cannot use import statement outside a module". how to fix? ...example for the client side is not the most successful and simple, where is the kaizen concept)
it's simple: https://t.me/hyperledgeriroha/23128
and it's not easy anymore:
import grpc from 'grpc'
import {
QueryService_v1Client,
CommandService_v1Client
} from '../iroha-helpers/lib/proto/endpoint_grpc_pb'
import { commands, queries } from 'iroha-helpers'
const IROHA_ADDRESS = 'localhost:50051' ...)
[telegram] <Stepan> do you think such an example of a client script in JS will take off? )
...
var PROTO_PATH = __dirname + '/../../shared_model/endpoint.proto';
var grpc = require('@grpc/grpc-js');
var protoLoader = require('@grpc/proto-loader');
var packageDefinition = protoLoader.loadSync(
PROTO_PATH,
{keepCase: true,
longs: String,
enums: String,
defaults: true,
oneofs: true
});
var CommandService_v1= grpc.loadPackageDefinition(packageDefinition).grpc.CommandService_v1;
var commandService = new CommandService_v1(
IROHA_ADDRESS,
grpc.credentials.createInsecure()
) (re @Alexander: shared_model/endpoint.proto)
- Solana smart contract development (Unit test, solana-program-library, Solana-web3, Raydium swap and orca) by using Rust and Anchor framework
2.Cardano smart contract by using Haskell and CosmWasm smart contract by using Rust CosmWasm. - Smart contract development in networks (Ethereum, BSC, Matic/Polygon) by using Solidity.
- Front-end development interactive with smart contract by using Web3, truffle, React(Redux / Thunk / Saga), Angular and Vue.
- ICO, IDO, Defi Swap, Reward system for staking, AOM(Olympus DAO Fork), Hyperledger Fabric
- NFT minting and NFT marketplace development(Create listing by admin, flat & Crypto payment, Bundle Sale/ Bulk Transfers, Drops, Rating, Bidding & Auction)
-Minter in Candy machine and 10% royalty moved to burn and other wallets
-Burn mechanism with kind of sharing rewards back to the holders
-Minting by user randomly NFTs, Upload the NFT arts and Traits(metadata) to IPFS
7.Bot development for sale monitoring bot OS and Niftygateway - Cryto game development with crypto payment gateway
Let's discuss your project together.
Thanks.)
[telegram] <♌︎ Leo> Makes sense if u only need a few of the iroha APIs and don’t wish to add the iroha-helpers as a dependency. But, if u need a lot more APIs, then you run the of risk reinventing the whole iroha-helpers. (re @Stepan: do you think such an example of a client script in JS will take off? )
...
var PROTO_PATH = __dirname + '/../../shared_model/endpoint.proto';
var grpc = require('@grpc/grpc-js');
var protoLoader = require('@grpc/proto-loader');
var packageDefinition = protoLoader.loadSync(
PROTO_PATH,
{keepCase: true,
longs: String,
enums: String,
defaults: true,
oneofs: true
});
var CommandService_v1= grpc.loadPackageDefinition(packageDefinition).grpc.CommandService_v1;
var commandService = new CommandService_v1(
IROHA_ADDRESS,
grpc.credentials.createInsecure()
))
[telegram] <Grouvie> Is Hyperledger Burrow still supported by Iroha or is it suggested to use other solutions to implement smart contract functionality?
The Hyperledger Burrow Github states:
"Hyperledger Burrow has been moved to End of Life status by the original project maintainers."
[telegram] <Sara> Hi So, we discussed this with the team and decided to not remove the code that allows to work with Burrow as for now I do not think there is an alternative (unless @baziorek has something that could help in one of his mentorship projects?). So, you can use the last version of the Burrow but we cannot guarantee it will work well because the project is being closed. (re @Grouvie: Is Hyperledger Burrow still supported by Iroha or is it suggested to use other solutions to implement smart contract functionality?
The Hyperledger Burrow Github states:
"Hyperledger Burrow has been moved to End of Life status by the original project maintainers.")