profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/bes/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.
Erik Zivkovic bes Sweden 82 'Til Infinity

bes/KeystoreBrute 45

A Keystore Brute-force attacker.

bes/StarField 4

Android Live Wallpaper

bes/googauth 2

Login as a Google user using OpenID (OAuth) and get tokens from the command line

bes/css-module-selector-exists 1

Webpack plugin that makes dev builds crash if a CSS Module selector does not exist

bes/bes.github.io 0

Necessity is the mother of bad blog posts

bes/Brain 0

Use this repository instead of your brain. Super helpful?

bes/chrome-video-slowmo 0

Chrome playback is SLOW MOTION if the computer can not keep up - should skip frames!

bes/chrome-video-texture-upload-slow 0

Proof of concept for showing that video texture upload is slow on Chrome 77

bes/CocoaPods 0

The Cocoa Dependency Manager.

pull request commenttaehwanno/warnings-to-errors-webpack-plugin

TypeScript typings for WarningsToErrorsPlugin

Thank you!

bes

comment created time in a month

issue commenttaehwanno/warnings-to-errors-webpack-plugin

TypeScript typings

Awaiting review.

bes

comment created time in a month

PR opened taehwanno/warnings-to-errors-webpack-plugin

TypeScript typings for WarningsToErrorsPlugin

The new file typings.d.ts contains TypeScript typings for webpack that should be usable for a webpack version that is compatible with typescript configuration.

If you open typings.d.ts in an IDE you will se a warning that webpack isn't installed, or that types are missing. This is because this repository has webpack as a peer dependency, so the user of this library will have to select a webpack version and install that. At that point the typings will be available at the client side (the one that does npm install or yarn add of warnings-to-errors-webpack-plugin).

Fixes taehwanno/warnings-to-errors-webpack-plugin#58

+9 -0

0 comment

2 changed files

pr created time in a month

create barnchbes/warnings-to-errors-webpack-plugin

branch : typescript-typings

created branch time in a month

issue commenttaehwanno/warnings-to-errors-webpack-plugin

TypeScript typings

As an example https://github.com/jantimon/html-webpack-plugin has typings.

bes

comment created time in a month

issue openedtaehwanno/warnings-to-errors-webpack-plugin

TypeScript typings

Nice plugin! I am using a webpack-config.ts (TypeScript for Webpack).

Would it be possible to add TypeScript types to this project?

If possible, I would prefer if the types are added to the repo directly and not to the @types/-project.

Do you take contributions? In that case I might be able to do it.

created time in a month

issue commenttrunnion/cargo-acap

README instructions are outdated?

@willglynn Don't want to take up any of your time unnecessarily (I know how precious one's time is) - but if you have the chance & are willing, I would love to take a look at your ACAP bindings <3

bes

comment created time in a month

issue closedprettier/prettier

SyntaxError when using Template Literal Type

Prettier 2.4.1 Playground link

# Options (if any):
{
  "trailingComma": "all",
  "tabWidth": 4,
  "semi": true,
  "singleQuote": false,
  "jsxBracketSameLine": false,
  "arrowParens": "always",
  "printWidth": 120
}

Input:

type TypeAbc = "a" | "b" | "c";
type TypeAbcEnabled = `${TypeAbc}Enabled`;

Output:

SyntaxError: Type expected. (2:23)
  1 | type TypeAbc = "a" | "b" | "c";
> 2 | type TypeAbcEnabled = `${TypeAbc}Enabled`;
    |                       ^
  3 | 
  4 | 
  5 | 
    at t (/Users/unknown/repo/node_modules/prettier/parser-typescript.js:1:287)
    at Object.parse (/Users/unknown/repo/node_modules/prettier/parser-typescript.js:14:2633274)
    at Object.parse (/Users/unknown/repo/node_modules/prettier/index.js:11370:19)
    at coreFormat (/Users/unknown/repo/node_modules/prettier/index.js:14784:25)
    at format (/Users/unknown/repo/node_modules/prettier/index.js:15019:75)
    at formatWithCursor (/Users/unknown/repo/node_modules/prettier/index.js:15035:12)
    at /Users/unknown/repo/node_modules/prettier/index.js:51620:12
    at Object.format (/Users/unknown/repo/node_modules/prettier/index.js:51640:12)
    at performFormat (/Users/unknown/Library/Application Support/JetBrains/Toolbox/apps/WebStorm/ch-0/212.5080.54/WebStorm.app/Contents/plugins/prettierJS/prettierLanguageService/prettier-plugin.js:66:29)
    at PrettierPlugin.handleReformatCommand (/Users/unknown/Library/Application Support/JetBrains/Toolbox/apps/WebStorm/ch-0/212.5080.54/WebStorm.app/Contents/plugins/prettierJS/prettierLanguageService/prettier-plugin.js:36:16)
Process finished with exit code -1

Expected behavior:

Prettier should not throw SyntaxError when trying to parse a Template Literal Type.

closed time in a month

bes

issue commentprettier/prettier

SyntaxError when using Template Literal Type

Prettier version was correct but WebStorm didn't pick up the change until restart.

bes

comment created time in a month

issue openedprettier/prettier

SyntaxError when using Template Literal Type

Prettier 2.4.1 Playground link

# Options (if any):
{
  "trailingComma": "all",
  "tabWidth": 4,
  "semi": true,
  "singleQuote": false,
  "jsxBracketSameLine": false,
  "arrowParens": "always",
  "printWidth": 120
}

Input:

type TypeAbc = "a" | "b" | "c";
type TypeAbcEnabled = `${TypeAbc}Enabled`;

Output:

SyntaxError: Type expected. (2:23)
  1 | type TypeAbc = "a" | "b" | "c";
> 2 | type TypeAbcEnabled = `${TypeAbc}Enabled`;
    |                       ^
  3 | 
  4 | 
  5 | 
    at t (/Users/bes/repos/spiideo/web-monolith/node_modules/prettier/parser-typescript.js:1:287)
    at Object.parse (/Users/bes/repos/spiideo/web-monolith/node_modules/prettier/parser-typescript.js:14:2633274)
    at Object.parse (/Users/bes/repos/spiideo/web-monolith/node_modules/prettier/index.js:11370:19)
    at coreFormat (/Users/bes/repos/spiideo/web-monolith/node_modules/prettier/index.js:14784:25)
    at format (/Users/bes/repos/spiideo/web-monolith/node_modules/prettier/index.js:15019:75)
    at formatWithCursor (/Users/bes/repos/spiideo/web-monolith/node_modules/prettier/index.js:15035:12)
    at /Users/bes/repos/spiideo/web-monolith/node_modules/prettier/index.js:51620:12
    at Object.format (/Users/bes/repos/spiideo/web-monolith/node_modules/prettier/index.js:51640:12)
    at performFormat (/Users/bes/Library/Application Support/JetBrains/Toolbox/apps/WebStorm/ch-0/212.5080.54/WebStorm.app/Contents/plugins/prettierJS/prettierLanguageService/prettier-plugin.js:66:29)
    at PrettierPlugin.handleReformatCommand (/Users/bes/Library/Application Support/JetBrains/Toolbox/apps/WebStorm/ch-0/212.5080.54/WebStorm.app/Contents/plugins/prettierJS/prettierLanguageService/prettier-plugin.js:36:16)
Process finished with exit code -1

Expected behavior:

Prettier should not throw SyntaxError when trying to parse a Template Literal Type.

created time in a month

startede-tony/best-of-ml-rust

started time in 2 months

issue commenttrunnion/cargo-acap

README instructions are outdated?

I would love to have a peek at those fabled Rust bindings to the ACAP libraries you mentioned ;)

bes

comment created time in 2 months

issue commenttrunnion/cargo-acap

README instructions are outdated?

Great! No dice using the workspace configuration (same error, missing Cargo.lock), but modifying Cargo.toml in cargo-acap like this worked:

vapix = { path = "../vapix", version = "0.1.1-alpha.0", features = ["goblin"] }
bes

comment created time in 2 months

issue commenttrunnion/cargo-acap

README instructions are outdated?

I wonder if warning: no Cargo.lock file published might be a hint?

bes

comment created time in 2 months

issue commenttrunnion/cargo-acap

README instructions are outdated?

Unfortunately I still get that build failure when using cargo install --locked --path ./cargo-acap

Given this directory structure:

axis% exa -T -L 1
.
├── cargo-acap
├── Cargo.toml
├── target
└── vapix

This Cargo.toml in axis:

[workspace]

members = [
    "cargo-acap",
    "vapix",
]

[patch.crates-io]
vapix = { path = "./vapix" }

And these commits from cargo-acap

axis/cargo-acap% git show --summary

commit 76edea1ef13017ddf202deee14ef3bcd98d0dc7d (HEAD -> master, origin/master, origin/HEAD)
Author: Will Glynn <will@willglynn.com>
Date:   Thu Nov 19 09:58:26 2020 -0600

    1.48.0: search for compiler/rustc_target/src/spec too

and vapix:

axis/vapix% git show --summary

commit eac61ce0bbf80e6c4ab3b9ad55960aab46fc39b1 (HEAD -> master, origin/master, origin/HEAD)
Author: Will Glynn <will@willglynn.com>
Date:   Fri Sep 3 23:45:47 2021 -0500

    Add ARTPEC-2

Running this command fails:

axis% cargo install --locked --path ./cargo-acap
warning: no Cargo.lock file published in cargo-acap v0.1.0 (/Users/bes/repos/github/axis/cargo-acap)
  Installing cargo-acap v0.1.0 (/Users/bes/repos/github/axis/cargo-acap)
    Updating crates.io index
    Updating git repository `https://github.com/willglynn/goblin.git`
warning: field is never read: `device`
  --> vapix/src/v3/recordings.rs:16:5
   |
16 |     device: &'a Client<T>,
   |     ^^^^^^^^^^^^^^^^^^^^^
   |
   = note: `#[warn(dead_code)]` on by default

warning: field is never read: `supports_continuous_recording`
  --> vapix/src/v3/recordings.rs:17:5
   |
17 |     supports_continuous_recording: bool,
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

warning: field is never read: `supports_playback_over_rtsp`
  --> vapix/src/v3/recordings.rs:18:5
   |
18 |     supports_playback_over_rtsp: bool,
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

warning: field is never read: `supports_exporting`
  --> vapix/src/v3/recordings.rs:19:5
   |
19 |     supports_exporting: bool,
   |     ^^^^^^^^^^^^^^^^^^^^^^^^

warning: associated function is never used: `new`
  --> vapix/src/v3/recordings.rs:23:25
   |
23 |     pub(crate) async fn new(device: &'a Client<T>) -> Result<Option<Recordings<'a, T>>> {
   |                         ^^^

warning: 5 warnings emitted

   Compiling cargo v0.47.0
error[E0283]: type annotations needed
   --> /Users/bes/.cargo/registry/src/github.com-1ecc6299db9ec823/cargo-0.47.0/src/cargo/util/config/de.rs:491:63
    |
491 |                 seed.deserialize(Tuple2Deserializer(1i32, env.as_ref()))
    |                                                           ----^^^^^^--
    |                                                           |   |
    |                                                           |   cannot infer type for type parameter `T` declared on the trait `AsRef`
    |                                                           this method call resolves to `&T`
    |
    = note: cannot satisfy `std::string::String: AsRef<_>`
help: use the fully qualified path for the potential candidates
    |
491 |                 seed.deserialize(Tuple2Deserializer(1i32, <std::string::String as AsRef<OsStr>>::as_ref(env)))
    |                                                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
491 |                 seed.deserialize(Tuple2Deserializer(1i32, <std::string::String as AsRef<std::path::Path>>::as_ref(env)))
    |                                                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
491 |                 seed.deserialize(Tuple2Deserializer(1i32, <std::string::String as AsRef<[u8]>>::as_ref(env)))
    |                                                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
491 |                 seed.deserialize(Tuple2Deserializer(1i32, <std::string::String as AsRef<str>>::as_ref(env)))
    |                                                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

error: aborting due to previous error

For more information about this error, try `rustc --explain E0283`.
error: failed to compile `cargo-acap v0.1.0 (/Users/bes/repos/github/axis/cargo-acap)`, intermediate artifacts can be found at `/Users/bes/repos/github/axis/target`

Caused by:
  could not compile `cargo`

To learn more, run the command again with --verbose.
bes

comment created time in 2 months

issue commenttrunnion/cargo-acap

README instructions are outdated?

So if I were to build an ACAP application using cargo-acap, but I also had a bunch of legacy code in C, then I would have to call into the C code using FFI, instead of my initial plan which was to call Rust from C over FFI?

bes

comment created time in 2 months

issue commenttrunnion/cargo-acap

README instructions are outdated?

Thanks for the explanation! I would be really happy to have a look at your Rust bindings 👍

You write "Axis SDK2", how does that relate to "ACAP 3" as mentioned here https://hub.docker.com/r/axisecp/acap-toolchain ?

bes

comment created time in 2 months

issue openedtrunnion/cargo-acap

README instructions are outdated?

Hi,

I was looking forward to testing this project to see if I could get Rust running as an ACAP app.

I had some troubles getting this up and running, mainly that cargo install cargo-acap doesn't work since there is no cargo-acap on crates.io.

I tried building cargo-acap from source but after cloning cargo-acap and vapix, updating Cargo.toml with vapix = { path = "../vapix", version = "0.1.1-alpha.0", features = ["goblin"] } and running cargo install --path cargo-acap I got a build error:

cargo install --path .
  Installing cargo-acap v0.1.0 (/Users/bes/repos/github/cargo-acap)
    Updating crates.io index
    Updating git repository `https://github.com/willglynn/goblin.git`
   Compiling cargo v0.47.0
error[E0283]: type annotations needed
   --> /Users/bes/.cargo/registry/src/github.com-1ecc6299db9ec823/cargo-0.47.0/src/cargo/util/config/de.rs:491:63
    |
491 |                 seed.deserialize(Tuple2Deserializer(1i32, env.as_ref()))
    |                                                           ----^^^^^^--
    |                                                           |   |
    |                                                           |   cannot infer type for type parameter `T` declared on the trait `AsRef`
    |                                                           this method call resolves to `&T`
    |
    = note: cannot satisfy `std::string::String: AsRef<_>`
help: use the fully qualified path for the potential candidates
    |
491 |                 seed.deserialize(Tuple2Deserializer(1i32, <std::string::String as AsRef<OsStr>>::as_ref(env)))
    |                                                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
491 |                 seed.deserialize(Tuple2Deserializer(1i32, <std::string::String as AsRef<std::path::Path>>::as_ref(env)))
    |                                                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
491 |                 seed.deserialize(Tuple2Deserializer(1i32, <std::string::String as AsRef<[u8]>>::as_ref(env)))
    |                                                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
491 |                 seed.deserialize(Tuple2Deserializer(1i32, <std::string::String as AsRef<str>>::as_ref(env)))
    |                                                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

error: aborting due to previous error

For more information about this error, try `rustc --explain E0283`.
error: failed to compile `cargo-acap v0.1.0 (/Users/bes/repos/github/cargo-acap)`, intermediate artifacts can be found at `/Users/bes/repos/github/cargo-acap/target`

Caused by:
  could not compile `cargo`

To learn more, run the command again with --verbose.

Which commits of cargo-acap and vapix should I use for building?

Furthermore I could not find any version of cargo-acap-build on docker hub? Maybe the files are on another registry, or do I have build the image (and multiple versions of rust) manually using the Dockerfile in cargo-acap-build. I am kind of surprised that there isn't an easier way of doing this than building Rust from scratch?

Thanks.

created time in 2 months

startedtrunnion/cargo-acap

started time in 2 months

startedtrunnion/vapix

started time in 2 months

startedpublic-apis/public-apis

started time in 2 months

startedbaldurk/renderdoc

started time in 2 months

issue commentgfx-rs/wgpu

Need more efficient way to use app client generated video frame's pixel buffer fill wgpu texture

Thanks for the update @kvark, I would be happy with an OpenGL-only solution for now, but it seems I am out of luck. Would be happy to help with testing or other simliar things if needed. I really like this project 👍

jinleili

comment created time in 2 months

startedmitsuhiko/insta

started time in 2 months

issue commentgfx-rs/wgpu

Need more efficient way to use app client generated video frame's pixel buffer fill wgpu texture

Sorry for bumping this, but I am looking to start experimenting on converting our video pipeline (ios/web/android/desktop/headless) which has implementation copied and slightly different for each platform into wgpu.

I am trying to get a feel for how far into the future this support would be, if there has been any movement?

As stated each platform is different, and I guess it has overlap with https://github.com/gfx-rs/wgpu/issues/274 and maybe other issues as well.

Sorry for bumping an old issue :(

jinleili

comment created time in 2 months

startedemilk/egui

started time in 2 months

issue closedbes/KeystoreBrute

.jks files

Does this code work with .jks files? Is there any difference between .jks and .keystore? Thanks in advance!

closed time in 3 months

ricardonogues

issue commentbes/KeystoreBrute

.jks files

Wow I totally missed this question. I haven't worked with this repository in a long time so the honest answer is: I don't know. Sorry for taking so long to answer...

ricardonogues

comment created time in 3 months

startedphiln/glide

started time in 3 months