Useful for comparing the fingerprint shown by github at https://github.com/settings/keys
against the public key on your machine to see whether it's a match:
ssh-keygen -l -E md5 -f ~/.ssh/id_rsa.pub
This lists the MD5 fingerprint
Useful for comparing the fingerprint shown by github at https://github.com/settings/keys
against the public key on your machine to see whether it's a match:
ssh-keygen -l -E md5 -f ~/.ssh/id_rsa.pub
This lists the MD5 fingerprint
lsof -nP | grep '(deleted)'
function parseSearchString () { | |
var qs = window.location.search | |
qs = qs.replace(/^\?/,'') | |
var parts = qs.split('&') | |
var params = {} | |
parts.forEach(function (part) { | |
var pair = part.split('=') | |
params[pair[0]] = decodeURIComponent(pair[1]) | |
}) | |
return params |
A third party Gradle plugin can be difficult to debug. In my case, I couldn't figure out why an input in my build.gradle file wasn't causing the plugin to add a desired task to a build. It's also not straightforward to inspect the source code of a plugin that arrives prebuilt. Fortunately if the plugin is open source, you can breakpoint in the source.
This thread forms the basis of these steps:
Attach to Remote JVM
./gradlew --no-daemon -Dorg.gradle.debug=true app:uploadBugsnagReleaseSourceMaps
, gradle will wait for a debugger to attachI have a NetCDF I downloaded from firesmoke.ca (Bluesky Canadian Wildfire Smoke Forecasting System) and I wanted to retrieve the PM 2.5 value fo a given geo coordinate or nearest lat / lon.
The NetCDF file can't be opened as a textfile as it's a binary format but there's a few tools I used to inspect the data model inside:
<!DOCTYPE html> | |
<html> | |
<head> | |
<title>Tournament Bracket Generator</title> | |
<script src="http://code.jquery.com/jquery-1.8.3.min.js"></script> | |
<script src="http://underscorejs.org/underscore-min.js"></script> | |
<script> | |
$(document).on('ready', function() { | |
var knownBrackets = [2,4,8,16,32], // brackets with "perfect" proportions (full fields, no byes) |
Written in typescript and can be run with ts-node
. You'll also need colordiff
(brew install colordiff
). Assumes much about the cdk.out
file structure and CLI output format which may certainly change. This should give you two prompts: one for your environment (and the stack to run the diff for), and one showing you a list of lambda functions where assets have changed for which you can run a colordiff.
Replace the inline stack names, in this case mine are BackgroundJobsStackStaging
and one for prod.
Useful for understanding the impact of deploying bundled code when it's changed. In my case, my lambda code bundles share common code with my API so it can change quite often with no impact on the lambda itself necessarily.
In my case I wanted to avoid importing unused modules into a built JS bundle for a lambda environment using a shared codebase. Using a nested eslint file I could prevent this kind of import: import {ModelA, ModelB} from 'src/models'
and instead encourage this kind of import: import {ModelA} from 'src/models/model-a'
{
"rules": {
"no-restricted-imports": [
"error",
{
// prevent barrel file imports to have more control over what ends up in the js bundle
"patterns": ["src/models", "!src/models/"]
Caveat
You're not going to get a beautiful EPUB out the other end - if that's what you're looking for, expect to do some manual clean-up work yourself.
Basic order of operations: