Short (72 chars or less) summary
More detailed explanatory text. Wrap it to 72 characters. The blank
line separating the summary from the body is critical (unless you omit
the body entirely).
Write your commit message in the imperative: "Fix bug" and not "Fixed
bug" or "Fixes bug." This convention matches up with commit messages
#!/usr/bin/perl | |
BEGIN { | |
if ($^O eq "MSWin32") | |
{ | |
require Win32; Win32::->import(); | |
require Win32::API; Win32::API::->import(); | |
require Win32::TieRegistry; Win32::TieRegistry::->import(); | |
} | |
} | |
use List::Util 'first'; |
#!/usr/bin/python3 | |
""" | |
Copyright 2021 Mygod | |
Licensed under the Apache License, Version 2.0 (the "License"); | |
you may not use this file except in compliance with the License. | |
You may obtain a copy of the License at | |
http://www.apache.org/licenses/LICENSE-2.0 |
xquery version "3.1"; | |
(:~ Validate, compare, sort, parse, and serialize Semantic Versioning (SemVer) | |
: 2.0.0 version strings, using XQuery. | |
: | |
: SemVer rules are applied strictly, raising errors when version strings do | |
: not conform to the spec. | |
: | |
: @author Joe Wicentowski | |
: @version 2.1.0 |
#!/usr/bin/env node | |
console.log('yay gist') |
On low memory devices like the arduino and esp8266 you do not want strings to be stored in RAM. This occurs by default on these systems. Declare a string const char * xyz = "this is a string"
and it will use up RAM.
The solution on these devices is to allow strings to be stored in read only memory, in Arduino this is the PROGMEM macro. Most of my experience is with the ESP8266 which is a 32bit micros controller. This device stores PROGMEM data in flash. The macro PROGMEM on ESP8266 is simply
#define PROGMEM ICACHE_RODATA_ATTR
// Related to https://issues.jenkins-ci.org/browse/JENKINS-26481 | |
abcs = ['a', 'b', 'c'] | |
node('master') { | |
stage('Test 1: loop of echo statements') { | |
echo_all(abcs) | |
} | |
stage('Test 2: loop of sh commands') { |
FWIW: I (@rondy) am not the creator of the content shared here, which is an excerpt from Edmond Lau's book. I simply copied and pasted it from another location and saved it as a personal note, before it gained popularity on news.ycombinator.com. Unfortunately, I cannot recall the exact origin of the original source, nor was I able to find the author's name, so I am can't provide the appropriate credits.
- By Edmond Lau
- Highly Recommended 👍
- http://www.theeffectiveengineer.com/
#!/bin/sh | |
# "include: /etc/unbound/ad-blacklist.conf" in /var/unbound/etc/unbound.conf | |
# run this script as a daily cron | |
# | |
# The list URLs were taken from the pi-hole project. | |
# More experimental lists are at https://github.com/pi-hole/pi-hole/blob/master/adlists.default | |
TMPFILE=$( mktemp get_dns_blacklists-XXXXXXXXX ) | |
trap 'rm -f $TMPFILE; exit 1' EXIT KILL INT QUIT TERM |
#To Decrypt Jenkins Password from credentials.xml | |
#<username>jenkins</username> | |
#<passphrase>your-sercret-hash-S0SKVKUuFfUfrY3UhhUC3J</passphrase> | |
#go to the jenkins url | |
http://jenkins-host/script | |
#In the console paste the script | |
hashed_pw='your-sercret-hash-S0SKVKUuFfUfrY3UhhUC3J' |