See how a minor change to your branch name style can make you a better programmer.
Format: <type>/#<issueNumber>-<alias>
#!/bin/bash | |
if [ -z "${SKIP_BRANCH}" ]; then | |
SKIP_BRANCH=(master develop release hotfix) | |
fi | |
NAME=$(git symbolic-ref --short HEAD) | |
NAME="${NAME##*/}" | |
# TODO: replace :token, :user, and :repo | |
curl -H "Authorization: token :token" \ | |
-H 'Accept: application/vnd.github.everest-preview+json' \ | |
"https://api.github.com/repos/:user/:repo/dispatches" \ | |
-d '{"event_type": "awesomeness", "client_payload": {"foo": "bar"}}' |
๊ทธ๋ฅ install ํ๋ฉด ./node_modules ๋๋ ํฐ๋ฆฌ์ ํจํค์ง ์ค์น๋ฅผ ํ๊ณ ๋.
--save, --save-dev ์ต์ ์ ./package.json ์ ๋ฐ์ดํธ๋ฅผ ๊ฐ์ดํด์ค๋ค.
dependencies์ devDepenencies ์ฐจ์ด๋ npm install์ ํ ๋ ๋ํ๋๋ค.
npm install โ$packageโ ๋ช ๋ น์ด๋ก ์ค์นํ ๋๋ --dev ์ต์ ์ ๋ถ์ฌ์ผ์ง๋ง ์ค์น๋๋ค.
aws emr create-cluster --auto-scaling-role EMR_AutoScaling_DefaultRole --termination-protected --applications Name=Hadoop Name=Hive Name=Spark --ebs-root-volume-size 10 --ec2-attributes '{"InstanceProfile":"EMR_EC2_DefaultRole","SubnetId":"subnet-xxxx","EmrManagedSlaveSecurityGroup":"sg-xxxxx","EmrManagedMasterSecurityGroup":"sg-xxxxx"}' --service-role EMR_DefaultRole --enable-debugging --release-label emr-5.12.0 --log-uri 's3n://aws-logs-xxxx/elasticmapreduce/' --name 'spark-cluster' --instance-groups '[{"InstanceCount":2,"BidPrice":"0.30","AutoScalingPolicy":{"Constraints":{"MinCapacity":0,"MaxCapacity":20},"Rules":[{"Action":{"SimpleScalingPolicyConfiguration":{"ScalingAdjustment":2,"CoolDown":300,"AdjustmentType":"CHANGE_IN_CAPACITY"}},"Description":"","Trigger":{"CloudWatchAlarmDefinition":{"MetricName":"YARNMemoryAvailablePercentage","ComparisonOperator":"LESS_THAN","Statistic":"AVERAGE","Period":300,"Dimensions":[{"Value":"${emr.clusterId}","Key":"JobFlowId"}],"EvaluationPeriods":1,"Unit":"PERCENT","Na |
// array buffer to JSON | |
const dataString JSON.stringify(Array.from(new Uint8Array(arrayBuffer))); | |
// send around | |
// JSON to ArrayBuffer | |
new Uint8Array(JSON.parse(dataString)).buffer |
Can I Remove MySQL Binary Log Yes, as long as the data is replicated to Slave server, itโs safe to remove the file. Itโs recommend only remove MySQL Binary Log older than 1 month. | |
Besides, if Recovery of data is the main concern, itโs recommend to archive MySQL Binary Log. | |
There are several ways to remove or clean up MySQL Binary Log, itโs not recommend to clean up the file manually, manually means running the remove command. | |
Remove MySQL Binary Log with RESET MASTER Statement Reset Master statement is uses for new database start up during replication for Master and Slave server. This statement can be used to remove all Binary Log. | |
To clean up Binary Log on Master Server |
""" | |
Given a dictionary, transform it to a string. Then byte encode that string. Then base64 encode it and since this will go | |
on a url, use the urlsafe version. Then decode the byte string so that it can be else where. | |
""" | |
data = base64.urlsafe_b64encode(json.dumps({'a': 123}).encode()).decode() | |
# And the decode is just as simple... | |
data = json.loads(base64.urlsafe_b64decode(query_param.encode()).decode()) | |
# Byte encode the string, base64 decode that, then byte decode, finally transform it to a dictionary |
import sys | |
import smtplib | |
from email.MIMEMultipart import MIMEMultipart | |
from email.MIMEText import MIMEText | |
name = "Ruan" | |
from_address = "[email protected]" | |
to_address = "[email protected]" | |
subject = "Test" |