Here are the steps to install Zig Compiler in Termux Android...
Install Termux from F-Droid, because the Google Play version is outdated...
Launch Termux on Android and enter...
/* wide */ | |
.wide .markdown-preview-sizer { | |
max-width: unset !important; | |
} | |
.life-calendar p a.internal-link { | |
display: inline-block; | |
} |
Here are the steps to install Zig Compiler in Termux Android...
Install Termux from F-Droid, because the Google Play version is outdated...
Launch Termux on Android and enter...
Important
THIS IS NOW OBSOLETE WITH KERNEL VERSIONS ≥ 6.7.0
A recent announcement in the kernel mail list by Cirrus developers will solve the problem described here. Therefore, the proposed solutions will be soon obsolete. See this comment (thanks, @flukejones, for the tip).
I got the speakers working on my Asus Zenbook 14 OLED UX3402, the one with Intel CPU and the two CS35L41
audio amplifiers connected over SPI (not the UM3402YA, with AMD and I²C). The amplifiers are supported by the snd_hda_scodec_cs35l41
module in recent kernel versions, but they require some model-specific configuration paramaters, that should be provided by
## | |
# These commands can all be run as Tasker shell commands, or through adb | |
# NOTE ON ROOT: I noticed many commands work through the adb shell, but fail in tasker unless using ROOT. If you tasks fail, try enabling root for it | |
## | |
## SETTING THINGS | |
# Enable deep doze | |
dumpsys deviceidle force-idle |
func sadd(key string, val string) error { | |
// get conn and put back when exit from method | |
conn := pool.Get() | |
defer conn.Close() | |
_, err := conn.Do("SADD", key, val) | |
if err != nil { | |
log.Printf("ERROR: fail add val %s to set %s, error %s", val, key, err.Error()) | |
return err | |
} |
The following outlines how to setup Heroku + Cloudflare with a full SSL certificate. What this means is that communication between the browser and the Cloudflare CDN is encrypted as well as communication between Cloudflare and Heroku’s origin server. Follow these steps exactly and the setup is a breeze.
First you want to add the root domain and the www domain to heroku. You do this by clicking into your production application, then going to settings and then scrolling down to Domains and certificates.
Here you will add <your_domain>.com
and www.<your_domain>.com
. This will give you two CNAME records. They will look something like <your_domain>.com.herokudns.com
and www.<your_domain>.com.herokudns.com
.
# non root user example for alpine | |
# | |
# usage: | |
# $ docker build --build-arg "USER=someuser" --tag test . | |
# $ docker run --rm test | |
FROM alpine | |
ARG USER=default | |
ENV HOME /home/$USER |
var i = 0; | |
var orphans = 0; | |
db.fs.chunks.find({}, { files_id: 1 }).forEach(function(chunk) { | |
i++; | |
if (i % 100 === 0) { | |
print(i); | |
} | |
if (!db.fs.files.findOne({ _id: chunk.files_id }, { _id: 1 })) { | |
print("orphan " + chunk._id); | |
db.fs.chunks.remove({ _id: chunk._id }); |
package main | |
import ( | |
"database/sql" | |
"fmt" | |
"log" | |
"math/rand" | |
"sync" | |
"time" |