brew services start colima
. You can skip the following work-around.
- Create an executable script to run in foreground and manage colima:
cat <<-EOF | sudo tee /usr/local/bin/colima-start-fg
#!/bin/bash
brew services start colima
. You can skip the following work-around.
cat <<-EOF | sudo tee /usr/local/bin/colima-start-fg
#!/bin/bash
Currently if you try to use the TensorFlow rust bindings crate: tensorflow = "0.17.0", this crate's sub-crate: tensorflow-sys will try to build the underlying TensorFlow C library from the source as Google hasn't provided an official release for Apple M1, but unfortunately the building will fail.
This gist provides a full working instructions for you to build the TensorFlow C library on Apple M1 (darwin_arm64), and eventually use it with the TensorFlow rust bindings crate: tensorflow = "0.17.0".
This gist was tested on TensorFlow v2.8.0
, the other versions should work in the same way.
Some of you may ask why to use Bazel to build your project, aren't there already in-place solutions with CMake examples? And, to be honest, I thought the same, but in the end two major factors prevailed - curiosity and challenge! Also, as Bazel is slowly prying around the corner to be a popular build system, the syntax is more intuitive, readability is high and it's well documented on their official sites (but misses more examples IMHO). If you're interested what the cons and pros for Bazel against CMake are you can look up this page and check it in detail.
First of all, you need Bazel installed on your system. Bazel's documentation is generous in these manners and you can look up the installation page for your OS and or, in our case, it's
# How to uninstall Razer Synapse 2 ( https://www.razerzone.com/synapse-2 ) | |
# on OS X (10.11-10.13) (El Capitan, Sierra, High Sierra) | |
# without using Razer's official uninstall tool. | |
# Tested on OS X 10.11.5 in July 2016. | |
# Edited with additional steps for later OS X versions, | |
# contributed by commenters on this gist. | |
# Step 1: In your terminal: stop and remove launch agents | |
launchctl remove com.razer.rzupdater |
{0: 'tench, Tinca tinca', | |
1: 'goldfish, Carassius auratus', | |
2: 'great white shark, white shark, man-eater, man-eating shark, Carcharodon carcharias', | |
3: 'tiger shark, Galeocerdo cuvieri', | |
4: 'hammerhead, hammerhead shark', | |
5: 'electric ray, crampfish, numbfish, torpedo', | |
6: 'stingray', | |
7: 'cock', | |
8: 'hen', | |
9: 'ostrich, Struthio camelus', |
# sort array with regards to nth column | |
arr = arr[arr[:,n].argsort()] |
This specification is inspired by and supersedes the [AngularJS commit message format][commit-message-format].
We have very precise rules over how our Git commit messages must be formatted. This format leads to easier to read commit history.
Each commit message consists of a header, a body, and a footer.
import re | |
import os | |
def getpassword(service, account): | |
def decode_hex(s): | |
s = eval('"' + re.sub(r"(..)", r"\x\1", s) + '"') | |
if "" in s: s = s[:s.index("")] | |
return s |