- Bash v5+ checkout Upgrading Bash on macOS
- bash-completion@2
{ | |
"workbench.colorCustomizations": { | |
"terminal.foreground": "#839496", | |
"terminal.background": "#002833", | |
"terminal.ansiBlack": "#003541", | |
"terminal.ansiBlue": "#268bd2", | |
"terminal.ansiCyan": "#2aa198", | |
"terminal.ansiGreen": "#859901", | |
"terminal.ansiMagenta": "#d33682", | |
"terminal.ansiRed": "#dc322f", |
private static Map<String, String> parameterStore() { | |
final AWSSimpleSystemsManagement client = AWSSimpleSystemsManagementClientBuilder.defaultClient(); | |
GetParametersRequest request = new GetParametersRequest(); | |
request.withNames("driver", "host", "port", "schema", "username", "password").setWithDecryption(true); | |
GetParametersResult result = client.getParameters(request); | |
Map<String, String> store = new HashMap<>(); |
/** | |
* Generate Case class from DataFrame.schema | |
* | |
* val df:DataFrame = ... | |
* | |
* val s2cc = new Schema2CaseClass | |
* import s2cc.implicit._ | |
* | |
* println(s2cc.schemaToCaseClass(df.schema, "MyClass")) | |
* |
This is an example realtime data visualization method using Zeppelin, NiFi and Kafka together.
Since NiFi 1.1.0, it provides components to act as a WebSocket server. This example contains a Zeppelin notebook paragraph which uses %angular
interpreter to establish a WebSocket connection with NiFi, and draw a pie chart using D3, refreshed automatically as it received updated data from NiFi in realtime manner.
And also, a NiFi template to run a WebSocket server, which exposes latest data for the pie chart. The data can be passed through a Kafka topic.
Having seen @pirapira's sketch of Bamboo ( https://github.com/pirapira/bamboo/ ), which proposed to add better control about the "smart contract program flow", even across calls, I thought that this should certainly be added to Solidity, and actually, it might even be possible now to a certain degree using inline assembly.
The problem is that with many functions in a contract, it is not always clear which can be called at which stage in the contract's lifetime. Certain smart contracts would be easier to understand if written as follows:
package rxgorm.demo | |
import grails.artefact.Controller | |
import grails.rx.web.Rx | |
import grails.validation.ValidationException | |
import groovy.transform.CompileStatic | |
import static org.springframework.http.HttpStatus.* | |
import static grails.rx.web.Rx.* | |
import static rx.Observable.* |
import {disableDeprecatedForms, provideForms} from '@angular/forms'; | |
... | |
bootstrap(App, [ | |
disableDeprecatedForms(), | |
provideForms(), | |
... | |
]); |
@Grab('org.codehaus.groovy.modules.http-builder:http-builder:0.7') | |
@Grab('oauth.signpost:signpost-core:1.2.1.2') | |
@Grab('oauth.signpost:signpost-commonshttp4:1.2.1.2') | |
import groovy.json.JsonOutput | |
import groovyx.net.http.RESTClient | |
import static groovyx.net.http.ContentType.* | |
import org.apache.http.params.HttpConnectionParams | |
import com.crossbusiness.nifi.processors.NiFiUtils as util |