It's not immediately obvious how to pull down the code for a PR and test it locally. But it's pretty easy. (This assumes you have a remote for the main repo named upstream.)
Getting the PR code
Make note of the PR number. For example, Rod's latest is PR #37: Psiphon-Labs/psiphon-tunnel-core#37
Fetch the PR's pseudo-branch (or bookmark or rev pointer whatever the word is), and give it a local branch name. Here we'll name it pr37:
$ git fetch upstream pull/37/head:pr37
These are instructions for setting up git to authenticate with GitHub when you have 2-factor authentication set up. This authentication should be inherited by any GUI client you are using. These are intentionally brief instructions, with links to more detail in the appropriate places.
Download and install the git command-line client (if required).
Open the git bash window and introduce yourself to git (if required):
git config --global user.name 'Firstname Lastname'
git config --global user.email 'firstname.lastname@gov.bc.ca'
| // ==UserScript== | |
| // @name A9 - Are the items exact? - Keybinds | |
| // @version 1.0.1 | |
| // @include hit_set_id:3NE6EBGK58WRF4Y79I0YPEOFMAE3EQ | |
| // @require https://gist.github.com/salembeats/7148acc820cdbc73f9c6d1f5a74f2844/raw/bc19f574867153816ca011a495284eddf1f12fac/mturk-hit-shorthand.user.library.js | |
| // ==/UserScript== | |
| const settings = { autoSubmit: false }; | |
| const submit = () => $('#submitButton').click(); |
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
When hosting our web applications, we often have one public IP
address (i.e., an IP address visible to the outside world)
using which we want to host multiple web apps. For example, one
may wants to host three different web apps respectively for
example1.com, example2.com, and example1.com/images on
the same machine using a single IP address.
How can we do that? Well, the good news is Internet browsers
| // ==UserScript== | |
| // @name Public -Testing Headers | |
| // @namespace salembeats forked by jrw254 (sabedth) | |
| // @version 1.1 | |
| // @description Links to whatever you want on the Overview & Earnings Bar Original code by salembeats with a small tweak to place inside this specific navbar | |
| // Combine this with Forking Panda Links on mTurk Dashboard for double the links! | |
| // @author Cuyler Stuwe (salembeats) forked by jrw254 (sabedth) | |
| // @include https://worker.mturk.com/dashboard* | |
| // @include https://worker.mturk.com/tasks* | |
| // @include https://worker.mturk.com/projects* |
I’m looking for any tips or tricks for making chrome headless mode less detectable. Here is what I’ve done so far:
Set my args as follows:
const run = (async () => {
const args = [
'--no-sandbox',
'--disable-setuid-sandbox',
'--disable-infobars',
| { | |
| "global": { | |
| "check_for_updates_on_startup": true, | |
| "show_in_menu_bar": false, | |
| "show_profile_name_in_menu_bar": false | |
| }, | |
| "profiles": [ | |
| { | |
| "complex_modifications": { | |
| "parameters": { |