Skip to content

Instantly share code, notes, and snippets.

View aeneasr's full-sized avatar
💭
I may be slow to respond.

hackerman aeneasr

💭
I may be slow to respond.
View GitHub Profile
hello world
{
"token_url": "http://127.0.0.5/from-remote"
}
package main
import (
"encoding/json"
"errors"
"fmt"
"net/http"
"net/url"
"os"
"sort"

Keybase proof

I hereby claim:

  • I am aeneasr on github.
  • I am aeneas (https://keybase.io/aeneas) on keybase.
  • I have a public key whose fingerprint is 89B1 A40F A0A1 14D7 CF16 F94A 998E 76A6 74F4 A689

To claim this, I am signing this object:

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
@aeneasr
aeneasr / metadata
Last active May 15, 2019 09:50
Ory Contributor License Agreement
{
"name": {
"title": "Full Name",
"type": "string",
"githubKey": "name"
},
"email": {
"title": "E-Mail",
"type": "string",
"githubKey": "email",
@aeneasr
aeneasr / ory-icla.md
Last active May 11, 2019 11:46
Ory Individual Contributor License Agreement

I am acting

  1. as an individual.
  2. on behalf of an entity.

Ory Individual Contributor License Agreement

In order to clarify the intellectual property license granted with Contributions from any person or entity, Ory GmbH ("Ory") must have a Contributor License Agreement ("CLA") on file that has been signed by each Contributor, indicating agreement to the license terms below. This license is for your protection as a Contributor as well as the protection of Ory; it does not change your rights to use your own Contributions for any other purpose.

You accept and agree to the following terms and conditions for Your present and future Contributions submitted to Ory. Except for the license granted herein to Ory and recipients of software distributed by Ory, You reserve all right, title, and interest in and to Your Contributions.

@aeneasr
aeneasr / resolve-git-merge-conflicts.md
Last active December 23, 2018 15:29
Resolving issues with git merge conflicts

Sometimes, maintainers choose to, for example, squash commit PRs into master. When you base off another branch of the PR, this may lead to serious merge conflicts which seem unresolvable (because the commit has been rewritten). In that case, the easiest path forward is to create a patch and apply it to a new branch based off master:

$ git fetch origin # assuming "origin" is the main repo, not your fork
$ git add -A
$ git commit -a -m "unstaged" # make sure everything is committed before you go ahead.
$ git diff origin/master > ~/patch.p # This must be outside of your repo
$ git checkout origin/master -b patch-1
import React from 'react'
import Enzyme from 'enzyme'
import { mount } from 'enzyme'
import Adapter from 'enzyme-adapter-react-16'
import DropDown from './index'
Enzyme.configure({ adapter: new Adapter() })
describe('DropDown input', () => {
const config = [{ title: 'one', value: '1' }, { title: 'two', value: '2' }, { title: 'three', value: '3' }]