orlp

use std::collections::HashMap;
use rand::{Rng, seq::SliceRandom};
use std::time::Instant;

fn rand_input(rng: &mut impl Rng) -> String {
    let theirs = ["A", "B", "C"].choose(rng).unwrap();
    let ours = ["X", "Y", "Z"].choose(rng).unwrap();
    format!("{theirs} {ours}\n")
}

koakh

**As a developer you have complete control over the signup and signin functionality...**

```shell
$ surreal sql --conn http://localhost:8000 --user root --pass root --ns test --db test
```

```sql
-- optional : this is the default see --ns test --db test start server flags
-- USE NS test DB test;

mike-myers-tob

Debug with GDB on macOS 11

The big reason to do this is that LLDB has no ability to "follow-fork-mode child", in other words, a multi-process target that doesn't have a single-process mode (or, a bug that only manifests when in multi-process mode) is going to be difficult or impossible to debug, especially if you have to run the target over and over in order to make the bug manifest. If you have a repeatable bug, no big deal, break on the fork from the parent process and attach to the child in a second lldb instance. Otherwise, read on.

Install GDB

Don't make the mistake of thinking you can just brew install gdb. Currently this is version 10.2 and it's mostly broken, with at least two annoying bugs as of April 29th 2021, but the big one is https://sourceware.org/bugzilla/show_bug.cgi?id=24069

$ xcode-select install  # install the XCode command-line tools

Esya

import { eddsa } from 'elliptic';
import { sha512 } from 'js-sha512';
import { sha256 } from 'js-sha256';
import * as BN from 'bn.js';

export interface Ed25519Node {
    kL: Uint8Array;
    kR: Uint8Array;
    A: Buffer;
    c: Uint8Array;

eh-dub

// in $PROJECT_ROOT/typings/@sapper
declare module '@sapper/app' {
  // from sapper/runtime/src/app/types.ts
  // sapper doesn't export its types yet
  interface Redirect {
      statusCode: number
      location: string
  }
  // end

penglei

#!/bin/bash

#qemu-img create -f qcow2 disk.qcow2 20G
#qemu-img create -f qcow2 varstore.img 128M
debian_iso=debian-9.6.0-arm64-xfce-CD-1.iso
qemu-system-aarch64 -smp cpus=6 -M virt -cpu max -m 2G -nographic \
    -drive file=QEMU_EFI.img,if=pflash,format=raw \
    -drive file=varstore.img,if=pflash \
    -drive file=disk.qcow2,if=virtio \
    -drive file=$debian_iso,if=virtio,format=raw

brianredbeard

QEMU arm64 cloud server emulation

This is basically a rehash of an original post on CNXSoft - all credit (particularly for the Virtio device arguments used below) belongs to the author of that piece.

Download the latest uefi1.img image. E.g. ubuntu-16.04-server-cloudimg-arm64-uefi1.img from https://cloud-images.ubuntu.com/releases/16.04/release/

Download the UEFI firmware image QEMU_EFI.fd from https://releases.linaro.org/components/kernel/uefi-linaro/latest/release/qemu64/

Determine your current username and get your current ssh public key:

danielepolencic

3 Virtual Machines Kubernetes cluster

Dependencies

You should install VirtualBox and Vagrant before you start.

Creating the cluster

You should create a Vagrantfile in an empty directory with the following content:

jasonbrooks

Start with CentOS 7

Set up the virt-sig repo:

# cat <<EOF > /etc/yum.repos.d/virt7-container-common-candidate.repo
[virt7-container-common-candidate]
name=virt7-container-common-candidate
baseurl=http://cbs.centos.org/repos/virt7-container-common-candidate/x86_64/os/
enabled=1

oznu

QEMU + Ubuntu ARM aarch64

These are the steps I used to get Ubuntu ARM aarch64 running with QEMU on OSX.

Get Ubuntu Image and QEMU EFI:

wget https://cloud-images.ubuntu.com/releases/16.04/release/ubuntu-16.04-server-cloudimg-arm64-uefi1.img
wget https://releases.linaro.org/components/kernel/uefi-linaro/latest/release/qemu64/QEMU_EFI.fd