Links:
How do we stop execution of functions if one fails?
def process_checkout(order) do
{ | |
"ab":{ | |
"name":"Abkhaz", | |
"nativeName":"аҧсуа" | |
}, | |
"aa":{ | |
"name":"Afar", | |
"nativeName":"Afaraf" | |
}, | |
"af":{ |
Links:
How do we stop execution of functions if one fails?
def process_checkout(order) do
Using perf:
$ perf record -g binary
$ perf script | stackcollapse-perf.pl | rust-unmangle | flamegraph.pl > flame.svg
NOTE: See @GabrielMajeri's comments below about the
-g
option.
# GPG on Tower |
// BrowserRouter is the router implementation for HTML5 browsers (vs Native). | |
// Link is your replacement for anchor tags. | |
// Route is the conditionally shown component based on matching a path to a URL. | |
// Switch returns only the first matching route rather than all matching routes. | |
import { | |
BrowserRouter as Router, | |
Link, | |
Route, | |
Switch, | |
} from 'react-router-dom'; |
This repo is my experiment in deploying a basic Phoenix app using the
release
feature from elixir 1.9 (https://elixir-lang.org/blog/2019/06/24/elixir-v1-9-0-released/)
and docker, via a multi-stage Dockerfile (https://docs.docker.com/develop/develop-images/multistage-build/)
leveraging bitwalker's docker images for Elixir and Phoenix.
The simplest way to manage Elixir versions is to use asdf
.
import socket | |
import asyncio | |
import websockets | |
import time | |
import logging | |
import argparse | |
import threading | |
import sys | |
I've experimented with Kotlin and coroutines in programming Akka. And I must say, I really like the combination so far.
But before I go into it some brief preliminaries for those who don't know Akka and actors.
Actors are a programming model that fits cloud native architectures particularly well. Being highly available and scaling horizontally. All while embracing the realities of multiple servers collaborating, server instances coming and going and the network having hickups.
On the JVM Akka is the prominent actor framework. It's been around for a while now and as a result it's highly reliable, well thought out and offers a wide programming eco system. My own interest in Akka is because of its suitability for software systems that can only be built with business events as a key construct and thinking model. And then of course materialized views, CQRS and near real-time data streams play a big role in constructing those systems.
/** | |
* JENKINS_HOST/job/pipeline-job/pipeline-syntax/gdsl | |
* https://gist.github.com/Mr-LiuDC/8a1fbe27e8fbd42361185b06085ef4c3 | |
* | |
* All pipeline steps can be found here: https://www.jenkins.io/doc/pipeline/steps/ | |
*/ | |
// The global script scope | |
def ctx = context(scope: scriptScope()) |