See how a minor change to your commit message style can make a difference.
git commit -m"<type>(<optional scope>): <description>" \ -m"<optional body>" \ -m"<optional footer>"
See how a minor change to your commit message style can make a difference.
git commit -m"<type>(<optional scope>): <description>" \ -m"<optional body>" \ -m"<optional footer>"
Resources: | |
ApiFunction: | |
Type: AWS::Serverless::Function | |
Properties: | |
Environment: | |
Variables: | |
# this is a standard lambda env var | |
user: "This is a regular env var" | |
# this is a var loaded from SSM |
This script will wait untill the last 2 sec of a vakantieveilingen.nl auction and place a bid as soon as you ar no longer the highest bidder. This while keeping the max value in to account. It will check the bidding every 0,2 sec.
maxBid
to the value you want to maximum spend. (whole euro's only)name: Create Release Branch | |
on: | |
workflow_dispatch: | |
inputs: | |
versionName: | |
description: 'Name of version (ie 5.5.0)' | |
required: true | |
versionCode: | |
description: 'Version number (50500)' | |
required: true |
These are just rough notes, maybe I'll clean them up later.
Fibers are an abstraction over sequential computation, similar to threads but at a higher level. There are two ways to think about this model: by example, and abstractly from first principles. We'll start with the example.
(credit here is very much due to Fabio Labella, who's incredible Scala World talk describes these ideas far better than I can)
Consider the following three functions
sandbox:111111111111
and prod:222222222222
dev
and sandbox
clusters in sandbox:111111111111
and beta
and prod
clusters in prod:222222222222
#!/bin/bash | |
# Props to https://gist.github.com/kaleksandrov/3cfee92845a403da995e7e44ba771183 from whom I took the code inside | |
# the conditional. | |
THIS_SCRIPT_INVOCATION=$0 | |
# The return status of this function will be 0 if globalprotect is running, 1 if not running because grep returns 0 | |
# if it finds a match and 1 if not. | |
# We basically grep for globalprotect but exclude all the matches we don't want |
dbt doesn't currently support var declarations outside of the dbt_project.yml
file - see relevant issue. This means that multiple users that use vars may run into conflicts or issues as they are all updating the dbt_project.yml
file at the same time.
This is a temporary workaround while the core team works on enabling the above functionality.
dbt_project.yml
file:# dbt_project.yml