Skip to content

Instantly share code, notes, and snippets.

Avatar

Joshua Harlow harlowja

View GitHub Profile
@harlowja
harlowja / arm64-on-Win10.md
Created Feb 8, 2021 — forked from billti/arm64-on-Win10.md
ARM64 Linux on Win10
View arm64-on-Win10.md

Below are the steps to get an ARM64 version of Ubuntu running in the QEMU emulator on Windows 10.

Install QEMU

Install for Windows from https://qemu.weilnetz.de/w64/ (I used qemu-w64-setup-20181211.exe)

Put C:\Program Files\qemu on your PATH, and run the below to check it's working (which will list out the CPUs the AArch64 emulator can emulate):

qemu-system-aarch64 -M virt -cpu help
View gist:405e255065f3236b4d0db5a8d94d1825
void Bag::reindexChunk(uint64_t chunk_pos) {
map<uint32_t, multiset<IndexEntry> >::iterator cit;
std::map<uint32_t, uint32_t>::iterator it;
ChunkHeader chunk_header;
ChunkInfo chunk_info;
bool chunk_ok = false;
uint32_t data_size = 0;
uint8_t op = 0xff;
readChunkHeader(chunk_header);
if (chunk_header.compressed_size == 0) {
View mime-multipart.txt
From nobody Mon Apr 20 12:02:54 2015
Content-Type: multipart/mixed; boundary="===============0102662315=="
MIME-Version: 1.0
--===============0102662315==
MIME-Version: 1.0
Content-Type: text/cloud-config; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="log_debug.yaml"
#cloud-config
# Enable full debug logging...
View gist:556fc9e0dcece4c677c50c768cc16a2d
import requests
import time
import sys
urls = [
#"http://releases.ubuntu.com/19.04/ubuntu-19.04-live-server-amd64.iso",
"http://www.ovh.net/files/10Gb.dat",
"http://speedtest-ca.turnkeyinternet.net/1000mb.bin",
]
@harlowja
harlowja / gist:892567e234c511f4347630f8ce40f6ba
Created Apr 11, 2019
/media/josh/film111/2019-04-11/_usr_bin_crash.1000.crash
View gist:892567e234c511f4347630f8ce40f6ba
ProblemType: Crash
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Apr 11 10:46:31 2019
DistroRelease: Ubuntu 16.04
ExecutablePath: /usr/bin/crash
ExecutableTimestamp: 1554417043
ProcCmdline: crash
ProcCwd: /home/josh/Dev/tools
ProcEnviron:
View os.svg
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
View junk.py
def not_indented(fh):
fh.write("b")
def close_it_and_call(filename, mode, func):
with open(filename, mode) as fh:
func(fh)
def main():
close_it_and_call("blob", "w", not_indented)
@harlowja
harlowja / pr_etiquette.md
Created Nov 9, 2018 — forked from naupaka/pr_etiquette.md
Pull Request Etiquette
View pr_etiquette.md

Pull Request Etiquette

Why do we use a Pull Request workflow?

PRs are a great way of sharing information, and can help us be aware of the changes that are occuring in our codebase. They are also an excellent way of getting peer review on the work that we do, without the cost of working in direct pairs.

Ultimately though, the primary reason we use PRs is to encourage quality in the commits that are made to our code repositories

Done well, the commits (and their attached messages) contained within tell a story to people examining the code at a later date. If we are not careful to ensure the quality of these commits, we silently lose this ability.

View gist:b7621aece1ce1b3fda012816ed72be87
running build_ext
building 'carla.libcarla' extension
clang-5.0 -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Idependencies/include -I/usr/lib/gcc/x86_64-linux-gnu/7/include -I/usr/include/python2.7 -c source/libcarla/libcarla.cpp -o build/temp.linux-x86_64-2.7/source/libcarla/libcarla.o -fPIC -std=c++14 -Wno-missing-braces -DBOOST_ERROR_CODE_HEADER_ONLY -DLIBCARLA_WITH_PYTHON_SUPPORT -DLIBCARLA_ENABLE_LIFETIME_PROFILER -DLIBCARLA_IMAGE_WITH_PNG_SUPPORT=true
In file included from source/libcarla/libcarla.cpp:109:
In file included from source/libcarla/SensorData.cpp:9:
In file included from dependencies/include/carla/image/ImageIO.h:9:
In file included from dependencies/include/carla/image/ImageIOConfig.h:50:
In file included from dependencies/include/boost/gil/extension/io/png_io.hpp:35:
In file included from /usr/include/png.h:321:
/usr/include/pngconf.h:383:12: error: unknown type nam
View gist:134610b124826ac8631f7739d3a5be84
======================================================================
ERROR: Failure: ImportError (libpng16.so.16: cannot open shared object file: No such file or directory)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/loader.py", line 418, in loadTestsFromName
addr.filename, addr.module)
File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 47, in importFromPath
return self.importFromDir(dir_path, fqname)
File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 94, in importFromDir
mod = load_module(part_fqname, fh, filename, desc)