profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/not-an-aardvark/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

not-an-aardvark/every-git-commit-shorthash 170

Git repository with a commit for every single shorthash

not-an-aardvark/eslint-plugin-eslint-plugin 102

An ESLint plugin for linting ESLint plugins

not-an-aardvark/eslint-rule-composer 37

A utility for composing ESLint rules from other ESLint rules

not-an-aardvark/eslint-plugin-rulesdir 15

An ESLint plugin to load project-specific ESLint rules

not-an-aardvark/eslint-plugin-self 12

Allows ESLint plugins to lint themselves

mit-plv/network-configurations 4

Using Coq to derive network configurations from declarative policies

not-an-aardvark/endian 1

Tests system endianness

ermain/d3-selection 0

Transform the DOM by selecting elements and joining to data.

not-an-aardvark/acorn 0

A small, fast, JavaScript-based JavaScript parser

issue commentRustCrypto/hashes

Use const generics instead of generic-array

I had a similar use case recently, and I found a decent workaround on stable Rust for this kind of thing:

pub trait Array<T>: Copy + Clone + AsRef<[T]> + AsMut<[T]> /* + (other array traits) + private::Sealed */ {}
impl<T: Copy, const N: usize> Array<T> for [T; N] {}

pub trait Digest {
    type Output: Array<u8>;
    const OutputSize: usize = std::mem::size_of::<Self::Output>();
}

pub struct Output<D: Digest> {
    bytes: D::Output
}

// ...

impl Digest for Sha256 {
    type Output = [u8; 32];
}

The difference between this approach and the current GenericArray approach is that Array here is a trait which is satisfied by "real" arrays, rather than being a struct. As a result, anyone who consumes a specific impl of Digest (e.g. a user of a hash function library) is only exposed to primitive arrays.

The disadvantage is that anything that consumes a Digest in a generic manner (i.e. with a <D: Digest> bound) needs to work with a Array<u8> trait bound rather than an actual [u8; N] parameter. This is mildly annoying because Array<u8> doesn't have the same auto-coercion behavior as real arrays. However, I found that this could generally be resolved with a one-line change around the use sites.

roblabla

comment created time in 3 days

push eventnot-an-aardvark/lucky-commit

Teddy Katz

commit sha 00000005ea40f4c3b3511509230b16c344878683

Simplify hash state representation

view details

Teddy Katz

commit sha 0000000c865f2902824f6bff765edf83a73f07fd

Rename GitHash trait to GitHashFn

view details

Teddy Katz

commit sha 00000009a4229ddd562f8a841a93d8715ce682b9

Clarify stability of underlying library

view details

push time in 3 days

issue closednot-an-aardvark/lucky-commit

vscode extension

can you make it a vscode extension

closed time in 12 days

5alidshammout

issue commentnot-an-aardvark/lucky-commit

vscode extension

I don't have any plans to turn this into a vscode extension, but you're certainly welcome to build a vscode extension yourself that uses this internally.

5alidshammout

comment created time in 12 days

push eventnot-an-aardvark/git-delete-squashed

Jonathan Ling

commit sha 201ad377384848c208dceb42d152115bbe38061a

Delete merged and squashed from other branches. (#11) This defaults to master currently, my change proposes that the script should take an argument and allow squashed branches to be pruned no matter where they were merged.

view details

push time in 13 days

PR merged not-an-aardvark/git-delete-squashed

Delete merged and squashed from other branches.

This defaults to master currently, my change proposes that the script should take an argument and allow squashed branches to be pruned no matter where they were merged.

+16 -6

1 comment

2 changed files

colonelpopcorn

pr closed time in 13 days

PullRequestReviewEvent

created tagnot-an-aardvark/lucky-commit

tagv2.1.0

Customize your git commit hashes!

created time in 17 days

PullRequestReviewEvent
PullRequestReviewEvent

push eventnot-an-aardvark/lucky-commit

Teddy Katz

commit sha 000000021b096da4060769a423b3f2cf53798bb2

v2.1.0

view details

push time in 17 days

issue closednot-an-aardvark/lucky-commit

Runtime crash on Windows

It seems that Rust chooses the wrong type for BASE_PADDING_SPECIFIER_ARG argument for some reason and it causes lucky_commit to crash.

NVIDIA stack trace:

> lucky_commit --benchmark

thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value:

################################ OPENCL ERROR ###############################

Error executing function: clSetKernelArg("scatter_padding_and_find_match")

Status error code: CL_INVALID_ARG_SIZE (-51)

Please visit the following url for more information:

https://www.khronos.org/registry/cl/sdk/1.2/docs/man/xhtml/clSetKernelArg.html#errors

#############################################################################
', C:\files\source\github\not-an-aardvark\lucky-commit\src/lib.rs:301:43
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Intel stack trace:

> lucky_commit --benchmark

thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Kernel argument type mismatch. The argument named: 'base_padding_specifier' at index: [3] should be a 'ulong' (ArgType { base_type: Ulong, cardinality: One, is_ptr: false }).', C:\files\source\github\not-an-aardvark\lucky-commit\src/lib.rs:301:43

Environment:

PS C:\Windows\system32> cargo --version
cargo 1.55.0 (32da73ab1 2021-08-23)
PS C:\Windows\system32> rustc --version
rustc 1.55.0 (c8dfcfe04 2021-09-06)

Windows 10 Pro x64 build 19043.1237

I've fixed the issue in #19.

closed time in 17 days

kasthack

issue commentnot-an-aardvark/lucky-commit

Runtime crash on Windows

Fixed in #19 (see https://github.com/not-an-aardvark/lucky-commit/pull/19#pullrequestreview-776754679 for details on what caused the crash)

kasthack

comment created time in 17 days

push eventnot-an-aardvark/lucky-commit

Konstantin Safonov

commit sha 0000000087a405fa1bd1e9c5d8d777971cb92f09

Fix runtime crash with 'CL_INVALID_ARG_SIZE' error due to type mismatch on windows

view details

push time in 17 days

PR merged not-an-aardvark/lucky-commit

Fix runtime crash on Windows due to type mismatch(Fixes #20 )

It seems that Rust chooses the wrong type for BASE_PADDING_SPECIFIER_ARG argument for some reason and it causes lucky_commit to crash. Full issue description: #20

This PR fixes this by explicitly specifying the argument type.

+1 -1

0 comment

1 changed file

kasthack

pr closed time in 17 days

PullRequestReviewEvent

issue closednot-an-aardvark/lucky-commit

Docker image

Would you consider releasing a Docker image for people who don't have rust installed?

For example this is the recommended way to use Go Swagger: https://goswagger.io/install.html

You just pull a Docker image, then create an alias that uses the docker image, instead of installing or compiling a binary.

Thanks!

closed time in 20 days

bokub

issue commentnot-an-aardvark/lucky-commit

Docker image

Thanks for the suggestion, but I'm going to close this for the reasons mentioned in https://github.com/not-an-aardvark/lucky-commit/pull/18#issuecomment-938839261.

bokub

comment created time in 20 days

PR closed not-an-aardvark/lucky-commit

Add Dockerfile and docker documentation

Fixes #17

Maybe the Dockerfile can be improved to run with OpenCL, but at least I was able to make something that works.

+25 -0

1 comment

2 changed files

bokub

pr closed time in 20 days

pull request commentnot-an-aardvark/lucky-commit

Add Dockerfile and docker documentation

Hi, thanks for the pull request!

Personally, I think this change is outside the scope of this repository. Running the Rust compiler within Docker seems like it's just an alternate way to fulfill the "install Rust somehow" requirement. Of course, I don't mind if people use Docker to run lucky-commit if that works best for them. But I don't think there's much value to providing an official Dockerfile for it at this point, because installing Rust the "normal" way typically isn't very difficult.

If a Dockerfile could allow someone to run the GPU version of lucky-commit in a cross-platform way (i.e. without needing to install OS-specific OpenCL libraries), then I think it would be worthwhile, because the process of installing OpenCL seems to be less consistent across platforms than the process of installing Rust. I'm not familiar enough with Docker or GPUs to know whether this is feasible.

bokub

comment created time in 20 days

pull request commentnot-an-aardvark/lucky-commit

chore: add funtoo linux instructions

Thanks!

invakid404

comment created time in 25 days

push eventnot-an-aardvark/lucky-commit

invakid404

commit sha 00000006f3cbaa8abb465f697c31e037a1b1f51c

chore: add funtoo linux instructions

view details

push time in 25 days

PR merged not-an-aardvark/lucky-commit

chore: add funtoo linux instructions

Hello 👋🏻,

Since I maintain the lucky-commit package in Funtoo Linux, I thought it'd be nice to have a few lines about it in the readme :^)

+8 -0

0 comment

1 changed file

invakid404

pr closed time in 25 days

push eventinvakid404/lucky-commit

invakid404

commit sha 00000006f3cbaa8abb465f697c31e037a1b1f51c

chore: add funtoo linux instructions

view details

push time in 25 days

PullRequestReviewEvent

issue commentnot-an-aardvark/every-git-commit-shorthash

error: wrong index v2 file size

Thanks for the report. What version of git are you using? From briefly looking just now, my understanding is that git 2.30.0 fixed some bugs relating to very large packfiles (e.g. https://github.com/git/git/commit/f86f769550ef7fb5162a9cd4be5e2be7981d063b). If your git version is older than 2.30.0, then updating git might fix the issue.

fionera

comment created time in a month

PullRequestReviewEvent

Pull request review commentnot-an-aardvark/git-delete-squashed

Delete merged and squashed from other branches.

 This is useful if you work on a project that squashes branches into master. Afte To run as a shellscript, simply copy the following command (setting up an alias is recommended). There's no need to clone the repo.  ```bash-git checkout -q master && git for-each-ref refs/heads/ "--format=%(refname:short)" | while read branch; do mergeBase=$(git merge-base master $branch) && [[ $(git cherry master $(git commit-tree $(git rev-parse $branch\^{tree}) -p $mergeBase -m _)) == "-"* ]] && git branch -D $branch; done+# Change $TARGET_BRANCH to your targeted branch, e.g. change from `master` to `main` to delete branches squased into `main`.
# Change $TARGET_BRANCH to your targeted branch, e.g. change from `master` to `main` to delete branches squashed into `main`.
colonelpopcorn

comment created time in a month

Pull request review commentnot-an-aardvark/git-delete-squashed

Delete merged and squashed from other branches.

 This is useful if you work on a project that squashes branches into master. Afte To run as a shellscript, simply copy the following command (setting up an alias is recommended). There's no need to clone the repo.  ```bash-git checkout -q master && git for-each-ref refs/heads/ "--format=%(refname:short)" | while read branch; do mergeBase=$(git merge-base master $branch) && [[ $(git cherry master $(git commit-tree $(git rev-parse $branch\^{tree}) -p $mergeBase -m _)) == "-"* ]] && git branch -D $branch; done+# Change $TARGET_BRANCH to your targeted branch, e.g. change from `master` to `main` to delete branches squased into `main`.+export TARGET_BRANCH=master && git checkout -q $TARGET_BRANCH && git for-each-ref refs/heads/ "--format=%(refname:short)" | while read branch; do mergeBase=$(git merge-base $TARGET_BRANCH $branch) && [[ $(git cherry $TARGET_BRANCH $(git commit-tree $(git rev-parse $branch\^{tree}) -p $mergeBase -m _)) == "-"* ]] && git branch -D $branch; done
TARGET_BRANCH=master && git checkout -q $TARGET_BRANCH && git for-each-ref refs/heads/ "--format=%(refname:short)" | while read branch; do mergeBase=$(git merge-base $TARGET_BRANCH $branch) && [[ $(git cherry $TARGET_BRANCH $(git commit-tree $(git rev-parse $branch\^{tree}) -p $mergeBase -m _)) == "-"* ]] && git branch -D $branch; done

I think this would avoid leaking the TARGET_BRANCH environment variable to subsequent commands.

colonelpopcorn

comment created time in a month

Pull request review commentnot-an-aardvark/git-delete-squashed

Delete merged and squashed from other branches.

 This is useful if you work on a project that squashes branches into master. Afte To run as a shellscript, simply copy the following command (setting up an alias is recommended). There's no need to clone the repo.  ```bash-git checkout -q master && git for-each-ref refs/heads/ "--format=%(refname:short)" | while read branch; do mergeBase=$(git merge-base master $branch) && [[ $(git cherry master $(git commit-tree $(git rev-parse $branch\^{tree}) -p $mergeBase -m _)) == "-"* ]] && git branch -D $branch; done+# Change $TARGET_BRANCH to your targeted branch, e.g. change from `master` to `main` to delete branches squased into `main`.+export TARGET_BRANCH=master && git checkout -q $TARGET_BRANCH && git for-each-ref refs/heads/ "--format=%(refname:short)" | while read branch; do mergeBase=$(git merge-base $TARGET_BRANCH $branch) && [[ $(git cherry $TARGET_BRANCH $(git commit-tree $(git rev-parse $branch\^{tree}) -p $mergeBase -m _)) == "-"* ]] && git branch -D $branch; done+# OR you can put this function in your shell config and call it like this+# `git-delete-squashed` OR `git-delete-squased main`+function git-delete-squashed() {+    local targetBranch = ${$1-:master}+    git checkout -q $targetBranch;
    git checkout -q $targetBranch &&

&& seems important here to avoid doing strange stuff and going off the rails if the branch doesn't exist. (I fixed this in the git alias recommendation above.)

colonelpopcorn

comment created time in a month