Fish is a smart and user-friendly command line (like bash or zsh). This is how you can instal Fish on MacOS and make your default shell.
Note that you need the https://brew.sh/ package manager installed on your machine.
brew install fish
notify: | |
if: always() | |
name: Notify | |
needs: | |
- job1 | |
- job2 | |
- job11 | |
- job3 | |
- job4 | |
runs-on: ubuntu-latest |
on: | |
pull_request: | |
types: [closed] | |
branches: | |
- master | |
jobs: | |
docker: | |
runs-on: ubuntu-latest | |
if: github.event.pull_request.merged | |
steps: |
set ignorecase | |
set smartcase | |
set scrolloff=3 " 3 lines above/below cursor when scrolling | |
" Emulated Plugins | |
set surround | |
" set easymotion | |
set NERDTree | |
" Copy to system clipboard as well |
Fish is a smart and user-friendly command line (like bash or zsh). This is how you can instal Fish on MacOS and make your default shell.
Note that you need the https://brew.sh/ package manager installed on your machine.
brew install fish
// Place your key bindings in this file to overwrite the defaults | |
[ | |
{ | |
"key": "cmd+t cmd+t", | |
"command": "workbench.action.tasks.runTask", | |
"args": "Run All Tests" | |
}, | |
{ | |
"key": "f5", | |
"command": "workbench.action.tasks.runTask", |
> Thank you for reaching out to Autonomous! I am sorry to hear that you are having some trouble with your SmartDesk | |
> but I will be glad to assist. It sounds like your system needs a "hard reset" can I please have you follow these | |
> steps thoroughly. | |
Reset Steps: | |
1. Unplug the desk for 20 seconds. Plug it back in. Wait a full 20 seconds. | |
2. Press the up and down buttons until the desk lowers all the way and beeps or 20 seconds pass. | |
3. Release both buttons. | |
4. Press the down buttons until the desk beeps one more time or 20 seconds pass. |
Testing React components seems simple at first. Then you need to test something that isn't a pure interaction and things seem to break down. These 4 patterns should help you write readable, flexible tests for the type of component you are testing.
I recommend doing all setup in the most functional way possible. If you can avoid it, don't set variables in a
beforeEach
. This will help ensure tests are isolated and make things a bit easier to reason about. I use a pattern
that gives great defaults for each test example but allows every example to override props
when needed:
With the release of Node 6.0.0, the surface of code that needs transpilation to use ES6 features has been reduced very dramatically.
This is what my current workflow looks like to set up a minimalistic and fast microservice using micro and async
+ await
.
import Html exposing (text) | |
main = | |
text <| toString <| cartesian ["a", "b", "c"] [1..5] | |
cartesian : List a -> List b -> List (a,b) | |
cartesian xs ys = | |
List.concatMap | |
( \x -> List.map ( \y -> (x, y) ) ys ) | |
xs |
This is mainly for node.js but might apply to other environments. Unsure.
If you are running a AWS Lambda function that calls another AWS service and getting an error about invalid tokens or other access denied errors, do this:
The role assigned to your lambda function will need permission to perform the actions. Check IAM and make sure the role has all the permissions.