Mike Chaberski mike10004

Visual Studio v140 toolset linker error from Googletest

This example demonstrates a linker error observed when building a Google Test project with the v140 platform toolset.

On JDK11, you may see an error with the following description

// [ERROR] JSR-303 validator failed to initialize: Unable to instantiate Configuration. (see http://aspects.jcabi.com/jsr-303.html)

Adjust the plugin dependencies as follows:

<pluginManagement>
    <plugins>
        <plugin>

com.github.mike10004

Setup on Ubuntu 18.04

Prerequsities

Install Anaconda 3 from https://www.anaconda.com.

Install the build-essential package. // TODO install gcc 6 instead of 7

NVIDIA prep

Ant build helpers for user-scoped Python 3 program installation

Sometimes I have projects that contain number of Python programs that I use for data processing. I want to be able to execute these programs from any working directory, but I don't want to pollute my filesystem outside of my home directory with the sources and executables.

For such a use case, I use Ant with build files like those contained in this gist.

The typical structure of a project that can take advantage of these helpers looks like:

VMWare Linux Guest - script and systemd unit to print IP address to file in shared folder

Preparation

Set up shared folders through the VMWare Player GUI on the host.

On the guest, create an /etc/fstab entry like

.host:/ /mnt/hgfs fuse.vmhgfs-fuse allow_other,auto_unmount,defaults 0 0

exams

This is a single-file ES6 module for unit testing. The reason it exists is that I became frustrated one day when I tried to learn how to run unit tests for ES6 modules in Node. I discovered that Node doesn't like ES6 modules and neither do any unit testing libraries. The JavaScript ecosystem has some peculiar pathologies. The answer to any problem seems to be to use Babel to make your new code become old.

	package manualwebdrivingharness;

	import com.github.mike10004.seleniumhelp.*;

	import io.github.mike10004.nanochamp.server.NanoControl;
	import io.github.mike10004.nanochamp.server.NanoResponse;
	import io.github.mike10004.nanochamp.server.NanoServer;
	import org.openqa.selenium.By;
	import org.openqa.selenium.WebDriver;
	import org.openqa.selenium.WebElement;

	import javax.annotation.Nullable;
	import java.time.Duration;
	import java.time.temporal.ChronoUnit;
	import java.util.Iterator;
	import java.util.Objects;
	import java.util.function.BooleanSupplier;
	import java.util.function.Predicate;
	import java.util.function.Supplier;
	import java.util.function.UnaryOperator;
	import java.util.stream.Stream;

	#!/bin/bash
	#
	# socket_wait.sh
	#
	# Script that runs a command after a socket can be opened. Tests the socket
	# using netcat and runs the command once a connection succeeds.
	#
	# Requires that environment variables SOCKET_WAIT_HOST and SOCKET_WAIT_PORT
	# are defined and nonempty.
	#

	#!/usr/bin/python3

	"""
	WARNING: The code you are about to view is DISGUSTING

	I wrote most of it months ago, so don't ask me what it's doing, or why.
	"""

	import struct
	import sys