profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/sharpner/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.
Nino sharpner Germany, Munich Ηellഠ, World

sharpner/pobin 9

a template loader for pongo2

sharpner/php-multiprocess-proxy 3

a multiplexer for the stupid php single threaded server

dazorni/9tac 2

A simple multi tic tac toe game (reactjs, golang and docker)

sharpner/dotfiles-ng 1

next gen dotfiles

sharpner/matcher 1

a collection of gomega matcher

sharpner/bluetooth-example-app 0

just the flutter example app with flutter_ble_lib

sharpner/cddatree 0

a visual representation of crafting in c:dda

sharpner/dotfiles 0

my dotfiles and installation scripts

sharpner/flutter_confetti 0

A Flutter widget that shoots confetti all over the screen.

MemberEvent

push eventgoogle/git-appraise

Omar Jarjur

commit sha bd714f195655234a69e167a3d3edf21f2b7db282

Add a CI check that we are not importing the builtin "os/exec" package anywhere

view details

Omar Jarjur

commit sha 3cdef93a49b5e486cc96433bb10ee04b127d0661

Add a message to the exec-vs-execabs check

view details

Omar Jarjur

commit sha cb8ed581e8dc59a03a452c421646745088f9b293

Replace the remaining usages of "os/exec" with the "execabs" package.

view details

Omar Jarjur

commit sha 3ab479a9ac378d9f0de72a616d136ea487424eb5

Fix Travis CI check for the use of the os/exec package

view details

Omar Jarjur

commit sha f552474f91c8c172ffb9834315e576d6071bc2f6

Submitting review bd714f195655 Remove remaining usages of `os/exec` in favor of `execabs`

view details

push time in 14 hours

issue openedgoogle/git-appraise

Comment location parameters are checked after invoking editor

In the git-appraise repo, I did

$ git appraise comment -f .travis.yml -l 10 bd714f195655

and composed a review comment in my editor. After I was done I got

Unable to comment on the given location: Line number 10 does not exist in file ".travis.yml"

This was just my off-by-one error, I should have used -l 9.

Unfortunately, .git/APPRAISE_COMMENT_EDITMSG was deleted despite the error, so I had to write it again. I think we should either check for errors upfront, or preserve APPRAISE_COMMENT_EDITMSG in case of errors.

(I pushed my review to my fork, I'm not sure if that will reach the PR here?)

created time in a day

push eventgoogle/git-appraise

Omar Jarjur

commit sha 3ab479a9ac378d9f0de72a616d136ea487424eb5

Fix Travis CI check for the use of the os/exec package

view details

push time in a day

push eventgoogle/git-appraise

Omar Jarjur

commit sha cb8ed581e8dc59a03a452c421646745088f9b293

Replace the remaining usages of "os/exec" with the "execabs" package.

view details

push time in a day

push eventgoogle/git-appraise

Omar Jarjur

commit sha 3cdef93a49b5e486cc96433bb10ee04b127d0661

Add a message to the exec-vs-execabs check

view details

push time in a day

create barnchgoogle/git-appraise

branch : ojarjur/no-exec-calls

created branch time in a day

startedfrapposelli/wwhrd

started time in 2 days

startedgrahamshaw1972/a2000Keyboard

started time in 3 days

issue openedjice-nospam/doryen-rs

Error: platform::platform::x11::util::input::PointerState uninitialized

Hello,

Thank you very much for this amazing project. I'm trying to run a demo:

cargo run --example basic

With stable version of Rust (rustc 1.50.0 (cb75ad5db 2021-02-10) ) I have this error:

platform::platform::x11::util::input::PointerState uninitialized

If I downgrade to 1.47.0 it works.

It's seams to be linked to winit issue

I absolutely don't know how can I update winit here.

created time in 7 days

startedputnam/binmerge

started time in 7 days

startedpoljar/matrix-nio

started time in 8 days

fork valyala/awesome-monitoring

INFRASTRUCTURE、OPERATION SYSTEM and APPLICATION monitoring tools for Operations.

http://canuxcheng.com/awesome-monitoring/

fork in 9 days

fork valyala/awesome-sre-tools

A curated list of Site Reliability and Production Engineering Tools

fork in 9 days

release VictoriaMetrics/VictoriaMetrics

v1.59.0

victoria-metrics-amd64-v1.59.0-cluster.tar.gz 17.25MB

victoria-metrics-amd64-v1.59.0-cluster_checksums.txt 0.34KB

victoria-metrics-amd64-v1.59.0-enterprise-cluster.tar.gz 17.55MB

victoria-metrics-amd64-v1.59.0-enterprise-cluster_checksums.txt 0.36KB

victoria-metrics-amd64-v1.59.0-enterprise.tar.gz 8.29MB

victoria-metrics-amd64-v1.59.0-enterprise_checksums.txt 0.20KB

victoria-metrics-amd64-v1.59.0.tar.gz 8MB

victoria-metrics-amd64-v1.59.0_checksums.txt 0.19KB

victoria-metrics-arm-v1.59.0-enterprise.tar.gz 7.65MB

victoria-metrics-arm-v1.59.0-enterprise_checksums.txt 0.20KB

victoria-metrics-arm-v1.59.0.tar.gz 7.35MB

victoria-metrics-arm-v1.59.0_checksums.txt 0.19KB

victoria-metrics-arm64-v1.59.0-cluster.tar.gz 15.12MB

victoria-metrics-arm64-v1.59.0-cluster_checksums.txt 0.34KB

victoria-metrics-arm64-v1.59.0-enterprise-cluster.tar.gz 15.42MB

victoria-metrics-arm64-v1.59.0-enterprise-cluster_checksums.txt 0.36KB

victoria-metrics-arm64-v1.59.0-enterprise.tar.gz 7.54MB

victoria-metrics-arm64-v1.59.0-enterprise_checksums.txt 0.20KB

victoria-metrics-arm64-v1.59.0.tar.gz 7.25MB

victoria-metrics-arm64-v1.59.0_checksums.txt 0.19KB

vmutils-amd64-v1.59.0-enterprise.tar.gz 56.10MB

vmutils-amd64-v1.59.0-enterprise_checksums.txt 0.73KB

vmutils-amd64-v1.59.0.tar.gz 41.28MB

vmutils-amd64-v1.59.0_checksums.txt 0.56KB

vmutils-arm-v1.59.0-enterprise.tar.gz 52.16MB

vmutils-arm-v1.59.0-enterprise_checksums.txt 0.73KB

vmutils-arm-v1.59.0.tar.gz 38.30MB

vmutils-arm-v1.59.0_checksums.txt 0.55KB

vmutils-arm64-v1.59.0-enterprise.tar.gz 52.17MB

vmutils-arm64-v1.59.0-enterprise_checksums.txt 0.73KB

vmutils-arm64-v1.59.0.tar.gz 38.28MB

vmutils-arm64-v1.59.0_checksums.txt 0.56KB

vmutils-windows-amd64-v1.59.0-enterprise.zip 14.99MB

vmutils-windows-amd64-v1.59.0-enterprise_checksums.txt 0.58KB

vmutils-windows-amd64-v1.59.0.zip 12.38MB

vmutils-windows-amd64-v1.59.0_checksums.txt 0.47KB

released time in 11 days

startedcognitedata/victoriametrics2openmetrics

started time in 11 days

startedoptiz0r/energy-usage

started time in 11 days

fork NiklausHofer/quickmove-extension

Quick Folder Move Add-on for Thunderbird

fork in 13 days

created taggoogle/git-appraise

tagv0.7

Distributed code review system for Git repos

created time in 19 days

PR merged google/git-appraise

Reviewers
Require `git` to be run from a trusted path

On Windows, the current working directory is searched for a matching executable before the rest of the user's path.

This causes a potential issue where running git appraise from within a directory that has an executable file matching the command git will cause that (untrusted) file to be invoked instead of the expected git executable when git-appraise attempts to shell out to git.

This change prevents that by using the new execabs package instead of os/exec. With this change, that scenario would cause git appraise to report an error rather than invoking the wrong git binary.

More background on the related issue here

+1 -1

0 comment

1 changed file

ojarjur

pr closed time in 19 days

push eventgoogle/git-appraise

Omar Jarjur

commit sha 6a274cc166bed0dc70a4810f967ed1b01d58b534

Require `git` to be run from a trusted path On Windows, the current working directory is searched for a matching executable before the rest of the user's path. This causes a potential issue where running `git appraise` from within a directory that has an executable file matching the command `git` will cause that (untrusted) file to be invoked instead of the expected `git` executable when `git-appraise` attempts to shell out to `git`. This change prevents that by using the new `execabs` package instead of `os/exec`. With this change, that scenario would cause `git appraise` to report an error rather than invoking the wrong `git` binary. More background on the related issue [here](https://blog.golang.org/path-security)

view details

Omar Jarjur

commit sha 47054737e4b4a1472cd7f001f7abfaf7ad3136da

Submitting review 6a274cc166be Require `git` to be run from a trusted path On Windows, the current working directory is searched for a matching executable before the rest of the user's path. This causes a potential issue where running `git appraise` from within a directory that has an executable file matching the command `git` will cause that (untrusted) file to be invoked instead of the expected `git` executable when `git-appraise` attempts to shell out to `git`. This change prevents that by using the new `execabs` package instead of `os/exec`. With this change, that scenario would cause `git appraise` to report an error rather than invoking the wrong `git` binary. More background on the related issue [here](https://blog.golang.org/path-security)

view details

push time in 19 days

create barnchgoogle/git-appraise

branch : ojarjur/restrict-git-executable-path

created branch time in 20 days

PR opened google/git-appraise

Require `git` to be run from a trusted path

On Windows, the current working directory is searched for a matching executable before the rest of the user's path.

This causes a potential issue where running git appraise from within a directory that has an executable file matching the command git will cause that (untrusted) file to be invoked instead of the expected git executable when git-appraise attempts to shell out to git.

This change prevents that by using the new execabs package instead of os/exec. With this change, that scenario would cause git appraise to report an error rather than invoking the wrong git binary.

More background on the related issue here

+1 -1

0 comment

1 changed file

pr created time in 20 days

fork mguentner/react-qr-reader

React component for QR Scanning on web using Zxing library

fork in 25 days

startedMauriceConrad/iCloud-API

started time in 25 days

release uber/cadence

v0.19.2

released time in a month