kaleido | Simple webapp state management with streams and lenses | Reactive Programming library

I believe the issue is that you are using fig.add_traces when you should be using fig.add_trace

The answer actually is very easy. Tough most of the charts can figure out the required size on their own, the sankey chart obviously can't. So basically you just have to set dimensions for all exports on sankey charts (yes even for vector graphics like eps and svg).

Also worth mentioning is that a minimum size is required. While my example now looks satisfying with 1920x1080, a size of 1280x720 looks broken even with vector-graphics.

I created a issue in official repository of library svglib, i speaking about this problem with a collaborate which detected this bug and start a resolution.

https://github.com/deeplook/svglib/issues/250

Problem resolved: https://github.com/deeplook/svglib/issues/250

Plotly + svglib + ReportLab = OK!

I'm the creator of the plugin. A couple of things:

• I think the dialect configuration is not correct, it should be under the key hibernate.dialect. Please take a look at the configuration section in the docs: https://github.com/kaleidos/grails-postgresql-extensions/tree/6.x#configuration
• Version 6.1.0 of the plugin is for Grails 3 and Hibernate 5.2. I haven't tested it with Hibernate 5.1 but the Hibernate team introduced some breaking changes in 5.2. You should try to upgrade to Hibernate 5.2 and use Grails Postgresql Extensions 6.1.0 or Hibernate 5.1 and Grails Postgresql Extensions 5.3.0 that supports Hibernate 5.1.

The plugin contains a few test domain classes. Take a look at TestMapJson https://github.com/kaleidos/grails-postgresql-extensions/blob/6.x/grails-app/domain/test/json/TestMapJson.groovy.
I also recommend you to use JsonB instead of Json as it is more powerful and provides more operators and queries.

The page of documentation you linked to has a section for troubleshooting at the bottom. You're directed to read there for help. It says:

If the service account ID used to sign tokens does not have the iam.serviceAccounts.signBlob permission, you may get an error message like the following:

The current version of Quorum deployed within Kaleido is V2.0.2. This has some problems with EIP155 external transaction signing (as used by Metamask). These have been resolved now in Quorum 2.1.0, and you can see the details in the release notes: https://github.com/jpmorganchase/quorum/releases We are currently in the process of migration testing Quorum 2.1.0 for Kaleido chains, and should be providing an updated release soon. In the meantime, if you create a second environment with Geth + PoA you should be able to try Metamask with Kaleido, and continue to explor other Quorum features on your existing chain. Regards, Peter

The solution is to Base64 encode the file and provide that string as the value of attachedFile (Thanks Jon Ruddlell for the tip).

The following call will create a record with an attachment called test.txt with the base64 encoded content "test test test" and with text/plain as the content type.

The account private keys are stored in the wallet on the Go-ethereum node. JSON/RPC and web3 do not provide an API to retrieve that private key, only to perform signing using it.

Kaleido is in the process of introducing a secure backup store, which can be configured at node creation time to point at an AWS S3 storage bucket. When a node has this configured, it will be possible to backup the filesystem of the node to the S3 Bucket (which can be encrypted using standard AWS features), including the wallet and access passwords for that wallet. If you have a KMS configured on the node, those passwords will be further protected by the master key in KMS.

This secure backup facility is coming very soon (the APIs are actually already live, but it's a dark feature as the docs/UI are not published). However, this won't allow you to perform a backup of an existing node. The configurations for Backup, Log streaming and KMS needs to be set at node creation time at the moment. It is on the Kaleido roadmap to allow Backup & Log streaming to be reconfigured on an existing node, but we aren't able to commit to a timeline on that.

I hope that helps explain the situation. Regards, Peter

You are hitting the limit of gas allowed to be spent per block. Information about gas limit is included into every block, so you can check what's this value is right now in your blockchain. Currently on Ethereum MainNet, GasLimit (per block) is about 8 millions (see here https://etherscan.io/blocks)

To fix this, you can start your blockchain with modified genesis file. Try to increase value of gasLimit parameter in your genesis file, which specifies the maximum amount of gas processed per block. Try "gasLimit": "8000000".