ps filter for Chrome processes running longer than 10 minutes (600s):
ps -e -o pid,etimes,command | awk '{ if ( $2 > 600 && $3 ~ /chrome/) print $0 }'If the last print $0 is changed to print $1, it will just show the first column, the PID.
Copied from Nestor U. - https://unix.stackexchange.com/questions/531040/list-processes-that-have-been-running-more-than-2-hours/592472#592472
One liner to find processes that have been running for over 2 hours
Mirror of https://old.reddit.com/r/Velo/comments/84z9p9/a_brief_history_of_shimano_compatibility/
I promised /u/thirty-five- that I would give him another writeup for the wiki, and I've got some time today so I figured why the hell not tackle drivetrain and derailleur compatibility?
As usual, the late great Sheldon Brown is a fantastic resource, but following his passing in 2008 it is rather hit or miss whether you can find compatibility information on newer stuff.
To start off with a disclaimer, this information is compiled from a variety of sources and while I believe it to be correct, there could be mistakes. Feel free to point them out and I will correct them.
To start off, we must explain how a derailleur works. At the simplest level, the point of the derailleur is to move the chain sideways at the point where it meshes with the chainrings or sprockets, forcing the chain onto the adjacent chainring or sprocket. In ye olde
extension_id=jifpbeccnghkjeaalbbjmodiffmgedin # change this ID
curl -L -o "$extension_id.zip" "https://clients2.google.com/service/update2/crx?response=redirect&os=mac&arch=x86-64&nacl_arch=x86-64&prod=chromecrx&prodchannel=stable&prodversion=44.0.2403.130&x=id%3D$extension_id%26uc"
unzip -d "$extension_id-source" "$extension_id.zip"Thx to crxviewer for the magic download URL.
| #!/usr/bin/env bash | |
| set -Eeuo pipefail | |
| trap cleanup SIGINT SIGTERM ERR EXIT | |
| script_dir=$(cd "$(dirname "${BASH_SOURCE[0]}")" &>/dev/null && pwd -P) | |
| usage() { | |
| cat <<EOF | |
| Usage: $(basename "${BASH_SOURCE[0]}") [-h] [-v] [-f] -p param_value arg1 [arg2...] |
alexpareto commented on Jul 22, 2019
An ugly, but workable solution to find out what exceptions are available on each client from the command line:
import boto3
client = boto3.client('sns') # or whatever client you're using
# client.exceptions.__dict__
| #!/usr/bin/env python3 | |
| # parallel_lambda_test.py | |
| import random | |
| import pendulum | |
| import time | |
| from concurrent import futures | |
| # The problem is that the AWS boto3 lambda invoke function is not truly asynchronous |
| #!/usr/bin/env python3 | |
| # concurrent_map_test.py | |
| import random | |
| import pendulum | |
| import time | |
| from concurrent import futures | |
| from functools import reduce | |
| netsh interface portproxy show all | |
| netsh interface portproxy add v4tov4 listenport=8081 listenaddress=127.0.0.1 connectport=8081 connectaddress=[remote-ip] | |
| netsh interface portproxy reset |
Mirror of You Don't Know JS: this & Object Prototypes, this All Makes Sense Now!
this All Makes Sense Now!In Chapter 1, we discarded various misconceptions about this and learned instead that this is a binding made for each function invocation, based entirely on its call-site (how the function is called).
To understand this binding, we have to understand the call-site: the location in code where a function is called (not where it's declared). We must inspect the call-site to answer the question: what's this this a reference to?
Mirror of You Don't Know JS: Scope & Closures, Appendix C: Lexical-this
Though this title does not address the this mechanism in any detail, there's one ES6 topic which relates this to lexical scope in an important way, which we will quickly examine.
ES6 adds a special syntactic form of function declaration called the "arrow function". It looks like this: