| #!/usr/bin/env python3 | |
| import yaml | |
| import json | |
| POSTFIX_VIRTUAL_FILENAME = '/etc/postfix/virtual' | |
| def get_blocked_domain_string(blocked_domains): |
| // ==UserScript== | |
| // @name Confluence Cloud Inline Code Styling like GitHub | |
| // @namespace http://cs.cementhorizon.com | |
| // @include https://mozilla-hub.atlassian.net/wiki/* | |
| // @grant GM_addStyle | |
| // @version 1.0 | |
| // @author Gene Wood | |
| // @description Cause inline code in Confluence Cloud to be styled like inline code in GitHub | |
| // ==/UserScript== |
| REM /E : recursive including empty directories | |
| REM /R:1 : retry once on failure | |
| REM /W:1 : wait 1 second between tries | |
| REM /LOG+ : append to a log file | |
| REM /TEE : output to the log file and the screen | |
| robocopy C:\source C:\destination /E /R:1 /W:1 /LOG+:C:\robocopy-2022-01-01.txt /TEE |
| Generated at 2022-06-26 22:26:03 -0700 | |
| ArgumentError: snap_package[plex-htpc] (wendy::packages line 321) had an error: ArgumentError: wrong number of arguments (given 1, expected 2) | |
| /opt/chef/embedded/lib/ruby/gems/3.0.0/gems/chef-17.10.3/lib/chef/provider/package/snap.rb:266:in `install_snaps' | |
| /opt/chef/embedded/lib/ruby/gems/3.0.0/gems/chef-17.10.3/lib/chef/provider/package/snap.rb:69:in `install_package' | |
| /opt/chef/embedded/lib/ruby/gems/3.0.0/gems/chef-17.10.3/lib/chef/provider/package.rb:120:in `block (3 levels) in <class:Package>' | |
| /opt/chef/embedded/lib/ruby/gems/3.0.0/gems/chef-17.10.3/lib/chef/provider/package.rb:267:in `multipackage_api_adapter' | |
| /opt/chef/embedded/lib/ruby/gems/3.0.0/gems/chef-17.10.3/lib/chef/provider/package.rb:119:in `block (2 levels) in <class:Package>' | |
| /opt/chef/embedded/lib/ruby/gems/3.0.0/gems/chef-17.10.3/lib/chef/mixin/why_run.rb:51:in `add_action' | |
| /opt/chef/embedded/lib/ruby/gems/3.0.0/gems/chef-17.10.3/lib/chef/provider.rb:293:in `converge_by' | |
| /opt/chef/embedded/lib/ruby/ge |
This is an easy method to spawn a portable DHCP server. It uses the https://github.com/networkboot/docker-dhcpd docker container.
mkdir datawget -O data/dhcpd.conf https://gist.githubusercontent.com/gene1wood/381582ec03d63b0b4770ed831de8e667/raw/cd2b61c64e04934ec41c38b7a3cc53ead48aea5c/dhcpd.confINTERFACE=eth0docker run -it --rm --init --net host -v "$(pwd)/data":/data networkboot/dhcpd $INTERFACE
| #!/bin/bash -e | |
| # https://gist.github.com/gene1wood/ddd66d79fc472f351a04c643aecbcf75 | |
| log() { | |
| echo -e "\e[92m${1}\e[0m" | |
| } | |
| if ! git status >/dev/null 2>&1; then | |
| log "Must be in a git repo" |
With the recent Travis CI security issue, it's again become necessary for Mozilla security folks to need to be able to contact maintainers of our GitHub repos (in this case to coordinate rotation of leaked credentials). I wanted to see if we (GitHub owners) could come up with a standard (either an existing one or make one) for how people can assert and communicate their role as a maintainer of a given GitHub repo. I don't know if an email thread is the best channel, but I thought I'd start this and we could switch to a zoom call if folks want. Here are some potential solutions that have come to mind
This standard ( https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository ) is so repo maintainers can assert how to report security vulnerabilities.
It looks like GitHub issues were disabled on the Duplicacy GitHub repo sometime between April and July this year (2021). I noticed this while checking back on a bug to see if I still needed to continue to use a workaround or if it had been fixed.
I searched through the repo README, on the duplicacy.com website and here in the forums but don't see any mention of the disabling of issues, or where one is meant to report or track bugs now.
Gilbert, if the intent is to prevent opening new issues (I'm guessing here, but as a maintainer of open source software I'm familiar with the challenges of getting low quality issues), would it be possible to, instead of disabling GitHub issues, re-enable GitHub issues and instead create a [6 month interac
| export person_api_client_id=xxx | |
| export person_api_client_secret=xxx | |
| export audience=api.sso.mozilla.com | |
| export api_domain=person.api.sso.mozilla.com | |
| if [ -z "$person_api_bearer_token" ]; then | |
| echo "Fetching bearer token" | |
| export person_api_bearer_token=$(curl \ | |
| --silent \ | |
| --request POST \ |