Ps: The current setup was done on 01-04-19
Project Dependency Versions at the time 👇
"react": "^16.7.0",
"react-dom": "^16.7.0",
"react-scripts": "2.1.3",
"typescript": "^3.2.2"
"tslint": "^5.12.0",
"tslint-config-prettier": "^1.17.0",Ps: The current setup was done on 01-04-19
Project Dependency Versions at the time 👇
"react": "^16.7.0",
"react-dom": "^16.7.0",
"react-scripts": "2.1.3",
"typescript": "^3.2.2"
"tslint": "^5.12.0",
"tslint-config-prettier": "^1.17.0",| #!/usr/bin/env sh | |
| # Multiple vulnerabilities have been disclosed in RubyGems: | |
| # https://www.ruby-lang.org/en/news/2018/02/17/multiple-vulnerabilities-in-rubygems/ | |
| # | |
| # And again in March 2019: | |
| # https://blog.rubygems.org/2019/03/05/security-advisories-2019-03.html | |
| # | |
| # If you're an Rbenv user, here's any easy one-liner to upgrade to a | |
| # safe version of Rubygems (2.7.8 / 3.0.3 or later) for each installed Ruby version: |
A list of commonly asked questions, design decisions, reasons why Clojure is the way it is as they were answered directly by Rich (even when from many years ago, those answers are pretty much valid today!). Feel free to point friends and colleagues here next time they ask (again). Answers are pasted verbatim (I've made small adjustments for readibility, but never changed a sentence) from mailing lists, articles, chats.
How to use:
It's now here, in The Programmer's Compendium. The content is the same as before, but being part of the compendium means that it's actively maintained.
There's a couple of ways, one way is
SPC / and type in your search stringSPC x S and search string - where x is your scope indicator (p for project, d for directory, etc..)C-c C-e inside the helm buffer to put all your match occurences and puts them into a special buffer called the edit buffer or something like thatC-c C-c to commit your changes.Installation procedure for pre-build actions to automatically populate Xcode Info.plist with dynamic data.
Edit Xcode Scheme and add a pre-action script.
Copy the contents of preaction.sh into the pre-action script box.
Hi Zach :D
Modals are funny beasts, usually they are a design cop-out, but that's okay, designers have to make trade-offs too, give 'em a break.
First things first, I'm not sure there is such thing as a "simple" modal that is production ready. Certainly there have been times in my career I tossed out other people's "overly complex solutions" because I simply didn't understand the scope of the problem, and I have always loved it when people who have a branch of experience that I don't take the time
| defmodule Async do | |
| def run do | |
| task1 = Task.async(fn -> :timer.sleep(10000); :slow end) | |
| task2 = Task.async(fn -> :timer.sleep(2000); :fail end) | |
| task3 = Task.async(fn -> :timer.sleep(1000); :fail end) | |
| await([task1, task2, task3]) | |
| end |
| wait4eth1() { | |
| CNT=0 | |
| until ip a show eth1 | grep -q UP | |
| do | |
| [ $((CNT++)) -gt 60 ] && break || sleep 1 | |
| done | |
| sleep 1 | |
| } | |
| wait4eth1 |