| module tests | |
| go 1.18 | |
| require ( | |
| github.com/mattn/go-sqlite3 v1.14.12 | |
| modernc.org/sqlite v1.16.0 | |
| ) | |
| require ( |
| package tests | |
| import ( | |
| "context" | |
| "testing" | |
| "github.com/stretchr/testify/assert" | |
| "go.uber.org/fx" | |
| "go.uber.org/fx/fxtest" | |
| "go.uber.org/zap" |
| package main | |
| import ( | |
| "database/sql" | |
| "fmt" | |
| "net/url" | |
| "os" | |
| "reflect" | |
| "regexp" | |
| "strconv" |
08/16/17 by Sergey Grebenshchikov
This is a quick tutorial on how to test code using the GoMock mocking library and the standard library testing package testing.
GoMock is a mock framework for Go. It enjoys a somewhat official status as part of the github.com/golang organization, integrates well with the built-in testing package, and provides a flexible expectation API.
| #!/bin/sh | |
| set -e | |
| # You can get the latest commit SHA by looking at the latest tagged commit here: https://github.com/microsoft/vscode/releases | |
| commit_sha="08a217c4d27a02a5bcde898fd7981bda5b49391b" | |
| archive="vscode-server-linux-x64.tar.gz" | |
| owner='microsoft' | |
| repo='vscode' | |
| # Auto-Get the latest commit sha via command line. |
The Linux kernel is written in C, so you should have at least a basic understanding of C before diving into kernel work. You don't need expert level C knowledge, since you can always pick some things up underway, but it certainly helps to know the language and to have written some userspace C programs already.
It will also help to be a Linux user. If you have never used Linux before, it's probably a good idea to download a distro and get comfortable with it before you start doing kernel work.
Lastly, knowing git is not actually required, but can really help you (since you can dig through changelogs and search for information you'll need). At a minimum you should probably be able to clone the git repository to a local directory.
The repository for the assignment is public and Github does not allow the creation of private forks for public repositories.
The correct way of creating a private frok by duplicating the repo is documented here.
For this assignment the commands are:
git clone --bare git@github.com:usi-systems/easytrace.git
| // Test/check FNV-1(a) hash implementations | |
| var testvectors = new[] { "", "a", "b", "c", "d", "e", "f", "fo", "foo", "foob", "fooba", "foobar", "\0", "a\0", "b\0", "c\0", "d\0", "e\0", "f\0", "fo\0", "foo\0", "foob\0", "fooba\0", "foobar\0", "ch", "cho", "chon", "chong", "chongo", "chongo ", "chongo w", "chongo wa", "chongo was", "chongo was ", "chongo was h", "chongo was he", "chongo was her", "chongo was here", "chongo was here!", "chongo was here!\n", "ch\0", "cho\0", "chon\0", "chong\0", "chongo\0", "chongo \0", "chongo w\0", "chongo wa\0", "chongo was\0", "chongo was \0", "chongo was h\0", "chongo was he\0", "chongo was her\0", "chongo was here\0", "chongo was here!\0", "chongo was here!\n\0", "cu", "cur", "curd", "curds", "curds ", "curds a", "curds an", "curds and", "curds and ", "curds and w", "curds and wh", "curds and whe", "curds and whey", "curds and whey\n", "cu\0", "cur\0", "curd\0", "curds\0", "curds \0", "curds a\0", "curds an\0", "curds and\0", "curds and \0", "curds and w\0", "curds and wh\0 |
| /// <summary> | |
| /// A hash combiner that is implemented with the Fowler/Noll/Vo algorithm (FNV-1a). This is a mutable struct for performance reasons. | |
| /// </summary> | |
| public struct FnvHash | |
| { | |
| /// <summary> | |
| /// The starting point of the FNV hash. | |
| /// </summary> | |
| public const int Offset = unchecked((int)2166136261); |
| """ | |
| Simple Linear Probabilistic Counters | |
| Credit for idea goes to: | |
| http://highscalability.com/blog/2012/4/5/big-data-counting-how-to-count-a-billion-distinct-objects-us.html | |
| http://highlyscalable.wordpress.com/2012/05/01/probabilistic-structures-web-analytics-data-mining/ | |
| Installation: | |
| pip install smhasher | |
| pip install bitarray |
