profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/mre/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.
Matthias mre @trivago Düsseldorf, Germany https://endler.dev Curious person. Maker. Rustacean

analysis-tools-dev/static-analysis 8919

A curated list of static analysis (SAST) tools for all programming languages, config files, build tools, and more.

analysis-tools-dev/dynamic-analysis 396

A curated list of dynamic analysis tools for all programming languages, binaries, and more.

hello-rust/show 286

🍿 Show notes, code, and future topic ideas for "Hello Rust!", a YouTube channel about the Rust programming language.

Hoverbear/digitalocean 32

A prototype API for Digital Ocean.

andygrunwald/things-with-buzzers-jeopardy 17

A Jeopardy! game frontend for things with buzzers with support for three buzzers 🚀

mre/beacon 8

A dedicated endpoint for real user monitoring. Works with boomerang, statsc and others.

andygrunwald/perseus 4

Local git mirror for your PHP (composer) project dependencies that works together with Satis.

mre/awesome-static-analysis-ci 4

Continuous integration for the awesome static analysis project

mre/async-talk 2

Slides and additional material for my talk about asynchronous programming

mre/accs 1

Parse menu of the ACCS cantine Düsseldorf.

issue commentlycheeverse/lychee

Link Checker Report

Huh? I'm confused where the empty output comes from... 😨

github-actions[bot]

comment created time in 9 hours

pull request commentlycheeverse/lychee

Don't panic on unknown status codes

Thanks for the feedback. The only thing that irritates me is that the ⚠️ emoji is not colored in the output. I tried to fix that, but so far no luck.

mre

comment created time in 3 days

PR closed mre/the-coding-interview

Configure Renovate

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.


Detected Package Files

  • problems/the-rabbit-question/RabbitQuestion/RabbitQuestion/RabbitQuestion.csproj (nuget)

What to Expect

It looks like your repository dependencies are already up-to-date and no Pull Requests will be necessary right away.


❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section. If you need any further assistance then you can also request help here.


This PR has been generated by Renovate Bot.

+3 -0

1 comment

1 changed file

ottx96

pr closed time in 3 days

pull request commentmre/the-coding-interview

Configure Renovate

Even though you probably have good intentions, let me tell you that this marketing strategy can backfire. Open Source maintainers are very sensitive to corporate pull requests that try to market a product like that. At best it gets ignored, at worst in can harm your brand.

ottx96

comment created time in 3 days

issue commentlycheeverse/lychee

Error with base dir `<empty>`

You have a good point there. I changed my mind. Unless anyone else brings up a good argument against it, let's go with option 1.

ran-huang

comment created time in 3 days

pull request commentlycheeverse/lychee

Make inputs required (show help if not provided)

Yeah we could overwrite the description, but then we'd run risk of forgetting to keep it up-to-date in the future. And incorrect information is worse than no information, so I'd like fix that upstream if possible. Since it's not a blocker, I went ahead and merged this. Thanks for the input @fauust, @MichaIng, and @lebensterben.

mre

comment created time in 3 days

push eventlycheeverse/lychee

Matthias

commit sha 712bdfa8cbd55bdfa103e16ad3cf063e493af18a

Make inputs required (show help if not provided) (#329)

view details

push time in 3 days

delete branch lycheeverse/lychee

delete branch : required-inputs

delete time in 3 days

PR merged lycheeverse/lychee

Make inputs required (show help if not provided)

Fixes #327 @fauust fyi

+5 -6

7 comments

2 changed files

mre

pr closed time in 3 days

issue closedlycheeverse/lychee

Why `lychee` does not defaults to `--help` ?

Hi! lychee defaults to trying to parse a README.md file and this is quite strange IMO.

Maybe defaulting to --help would be more appropriate?

I am not sure about the reason of this behavior (there is maybe a very good one) and sorry if this was already discussed.

closed time in 3 days

fauust

pull request commentlycheeverse/lychee

Recursion Support (closes #55, #78)

Will put this on hold once again as we started implementing a stream-based approach in #330, which might supersede this branch soon. Sorry to everyone waiting on recursion support to land, but I'd like to get this right instead of merging a buggy solution prematurely.

mre

comment created time in 3 days

PR closed lycheeverse/lychee

Send extracted links from extractor pool via channel question

I tried to make it look decent, maybe a different style while waiting for the first link would be sensible?

I recorded an example here: https://user-images.githubusercontent.com/5281645/112684773-cf958d00-8e73-11eb-832b-3e116dba3545.mp4

And all those nitpick commits are just small things I noticed, I can drop them if you don't want them

+44 -28

8 comments

3 changed files

TimoFreiberg

pr closed time in 3 days

pull request commentlycheeverse/lychee

Send extracted links from extractor pool via channel

@TimoFreiberg let's focus on #330 and move the discussion over there. I'll close this to keep the issue tracker clean. We can draw some inspiration from here in the future, though.

TimoFreiberg

comment created time in 3 days

PR opened lycheeverse/lychee

Don't try to publish Docker image on fork

Discussion: https://github.com/lycheeverse/lychee/issues/321#issuecomment-919161530 @fauust is that how you imagined it or is there a better way?

+1 -0

0 comment

1 changed file

pr created time in 3 days

create barnchlycheeverse/lychee

branch : block-docker-publish-on-forks

created branch time in 3 days

pull request commentlycheeverse/lychee

Add a description on DockerHub registry

Cool. Rolled back the change. Thanks anyway for looking into this. Let's try again at a later point in time. 😃

fauust

comment created time in 3 days

push eventlycheeverse/lychee

Matthias

commit sha dd667a656ccc1b29c446fae2ae0f09b422879433

Undo Docker documentation from CI It's currently not supported to update docs with a Dockerhub token. See https://github.com/lycheeverse/lychee/pull/325.

view details

push time in 3 days

pull request commentlycheeverse/lychee

Make inputs required (show help if not provided)

I agree with your conclusion. The current implementation in clap is not technically incorrect however, so they might decline a change. The -- isn't strictly required in all cases and the help message looks a little cleaner. Maybe that's what they were aiming for. On the other hand if a user doesn't know about the -- trick, they might get stuck in such a situation anyway. Then again even if the -- was mentioned, they probably wouldn't know what that would be used for if they never came across that convention before. ¯\_(ツ)_/¯ I for one consider it good form to add the [--] in this case. Just don't want to add last = true and make the -- mandatory, because it's cumbersome for simple use-cases.

> lychee README.md
error: Found argument 'README.md' which wasn't expected, or isn't valid in this context

USAGE:
    lychee [FLAGS] [OPTIONS] [--] <inputs>...

This would be lychee -- README.md with last=true, which is inconvenient.

But probably we should just ask them about their opinion I don't consider this a blocker, though. @MichaIng?

mre

comment created time in 3 days

push eventlycheeverse/lychee

dependabot[bot]

commit sha d83d36788ffb09a96356a5745b1cfc2c49b828e9

Bump serde_json from 1.0.67 to 1.0.68 (#331) Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.67 to 1.0.68. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.67...v1.0.68) --- updated-dependencies: - dependency-name: serde_json dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

view details

push time in 3 days

delete branch lycheeverse/lychee

delete branch : dependabot/cargo/serde_json-1.0.68

delete time in 3 days

PR merged lycheeverse/lychee

Bump serde_json from 1.0.67 to 1.0.68 dependencies

Bumps serde_json from 1.0.67 to 1.0.68. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/serde-rs/json/releases">serde_json's releases</a>.</em></p> <blockquote> <h2>v1.0.68</h2> <ul> <li>Preserve negative sign of <code>-0</code> when deserializing to f32 or f64 (<a href="https://github-redirect.dependabot.com/serde-rs/json/issues/799">#799</a>, <a href="https://github-redirect.dependabot.com/serde-rs/json/issues/801">#801</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/serde-rs/json/commit/9420d3a0a4ebf17ef1deeecee07851f58ff6148f"><code>9420d3a</code></a> Release 1.0.68</li> <li><a href="https://github.com/serde-rs/json/commit/d86e353575b27c52611787cf499bcc55a2409e44"><code>d86e353</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/serde-rs/json/issues/801">#801</a> from dtolnay/negative0</li> <li><a href="https://github.com/serde-rs/json/commit/51a4db1631d2746f28fe3b6f2eafda3aff03af4b"><code>51a4db1</code></a> Parse -0 as float -0.0 instead of integer 0</li> <li><a href="https://github.com/serde-rs/json/commit/f5219be867e11c81f463c769e01caa2d79702926"><code>f5219be</code></a> Add test parsing <code>-0</code></li> <li><a href="https://github.com/serde-rs/json/commit/b419f2e0650ab959a3db0b0ca471269e81abf27f"><code>b419f2e</code></a> Test negative zero parsing to f32</li> <li><a href="https://github.com/serde-rs/json/commit/ef823af7d5d6c67b06988c50d9a2dfcba9c9e247"><code>ef823af</code></a> Suppress unused field in test_borrow_in_map_key</li> <li><a href="https://github.com/serde-rs/json/commit/f4fc150c45d915426f05739a6b77859983c4f412"><code>f4fc150</code></a> Fix dead code warning in issue 795 regression test</li> <li><a href="https://github.com/serde-rs/json/commit/133bb61574c5d1aa2f60dbf967ebc05e0363b0b1"><code>133bb61</code></a> Ignore derivable_impls clippy false positive</li> <li>See full diff in <a href="https://github.com/serde-rs/json/compare/v1.0.67...v1.0.68">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

</details>

+3 -3

0 comment

2 changed files

dependabot[bot]

pr closed time in 3 days

issue commentlycheeverse/lychee

Error with base dir `<empty>`

I see three options moving forward:

  1. We silently ignore internal links with absolute paths.
  2. We print a warning but check the rest
  3. We assume the input directory as the base for absolute links if no base is set.

In the long run I lean towards option 3. It would be what I expect if I run lychee public/ for example where public is the build directory of a static site generator. It gets tricky when we look at multiple inputs. Then we'd have to track the input source for each link to determine the base. We could add a source field to the Input, which would allow us to backtrack the source of each link for that use-case.

This requires quite some refactoring, so in the meantime we could go with option 1 to not break any existing user workflows.

ran-huang

comment created time in 3 days

push eventlycheeverse/lychee

Matthias

commit sha b20b689f7306fb0095c7d0b3955b92376bb7cf1b

Fix docs

view details

push time in 3 days

pull request commentlycheeverse/lychee

Add a description on DockerHub registry

Would also love to set an icon/logo/avatar, but that's only possible with a pro account it seems. 😕 That little lychee would look amazing IMHO. 😆

fauust

comment created time in 3 days

pull request commentlycheeverse/lychee

Add a description on DockerHub registry

Great idea. I've updated the docs now and added a tagline.

image

fauust

comment created time in 3 days

PR closed mre/prettyprint

Update derive_builder requirement from 0.9.0 to 0.10.2 dependencies

Updates the requirements on derive_builder to permit the latest version. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/colin-kiegel/rust-derive-builder/releases">derive_builder's releases</a>.</em></p> <blockquote> <h2>v0.10.2</h2> <ul> <li>Don't include <code>derive_builder_core</code> in <code>derive_builder</code> so that <code>no_std</code> builds <a href="https://github-redirect.dependabot.com/colin-kiegel/rust-derive-builder/issues/206">#206</a></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/colin-kiegel/rust-derive-builder/commit/0b104fa91fb4d97dc245fca0a79ba064a84accca"><code>0b104fa</code></a> Bump version to 0.10.2</li> <li><a href="https://github.com/colin-kiegel/rust-derive-builder/commit/b0180683670554ea93b865b7b05ae9b548fde2a0"><code>b018068</code></a> Remove derive_builder_no_std_tests</li> <li><a href="https://github.com/colin-kiegel/rust-derive-builder/commit/77d847e146371fcd8f99fb9fe04c98e674d575d3"><code>77d847e</code></a> Move UninitializedFieldError to derive_builder</li> <li><a href="https://github.com/colin-kiegel/rust-derive-builder/commit/4c7034f0bbf8e78c051843af112684f025306bc5"><code>4c7034f</code></a> Bump version to 0.10.1</li> <li><a href="https://github.com/colin-kiegel/rust-derive-builder/commit/0b5c1ac2f852b25bee0b43991abedc59f6359ddb"><code>0b5c1ac</code></a> docs: remove the obsolete instruction (<a href="https://github-redirect.dependabot.com/colin-kiegel/rust-derive-builder/issues/202">#202</a>)</li> <li><a href="https://github.com/colin-kiegel/rust-derive-builder/commit/57179c65f9bdbc5ea4b6c46a50475d2bc127cbc0"><code>57179c6</code></a> Make it work in no_std environment (<a href="https://github-redirect.dependabot.com/colin-kiegel/rust-derive-builder/issues/204">#204</a>)</li> <li><a href="https://github.com/colin-kiegel/rust-derive-builder/commit/7bea88f9899434b10b89d866d52b05408d2cd6cf"><code>7bea88f</code></a> Fix a test (<a href="https://github-redirect.dependabot.com/colin-kiegel/rust-derive-builder/issues/205">#205</a>)</li> <li><a href="https://github.com/colin-kiegel/rust-derive-builder/commit/9d2ee6ffb7864401e5299b6104721db7a742223b"><code>9d2ee6f</code></a> Bump version to 0.10.0</li> <li><a href="https://github.com/colin-kiegel/rust-derive-builder/commit/6f6c0fe53f7f88afd5951058a967a741f76027df"><code>6f6c0fe</code></a> Update README with 0.10.0 material</li> <li><a href="https://github.com/colin-kiegel/rust-derive-builder/commit/7cde4861025278c3af73236263e67c27ac6e20d9"><code>7cde486</code></a> Add setter(each = "...") option to extend collection-like fields (<a href="https://github-redirect.dependabot.com/colin-kiegel/rust-derive-builder/issues/199">#199</a>)</li> <li>Additional commits viewable in <a href="https://github.com/colin-kiegel/rust-derive-builder/compare/v0.9.0...v0.10.2">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

If all status checks pass Dependabot will automatically merge this pull request.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Automerge options (never/patch/minor, and dev/runtime dependencies)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

</details>

+1 -1

2 comments

1 changed file

dependabot-preview[bot]

pr closed time in 3 days

push eventmre/prettyprint

dependabot[bot]

commit sha 01903fa732cde9489868ff6b563a9087cbddb3c7

Update directories requirement from 3.0.0 to 4.0.0 Updates the requirements on [directories](https://github.com/soc/directories-rs) to permit the latest version. - [Release notes](https://github.com/soc/directories-rs/releases) - [Commits](https://github.com/soc/directories-rs/commits) --- updated-dependencies: - dependency-name: directories dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>

view details

Matthias

commit sha 5be1bea4b5ac183846453d3494f32edd0a5576ef

Merge pull request #36 from mre/dependabot/cargo/directories-4.0.0 Update directories requirement from 3.0.0 to 4.0.0

view details

push time in 3 days

delete branch mre/prettyprint

delete branch : dependabot/cargo/directories-4.0.0

delete time in 3 days

PR merged mre/prettyprint

Update directories requirement from 3.0.0 to 4.0.0 dependencies

Updates the requirements on directories to permit the latest version. <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/soc/directories-rs/commits">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

</details>

+1 -1

0 comment

1 changed file

dependabot[bot]

pr closed time in 3 days

pull request commentlycheeverse/lychee

Make inputs required (show help if not provided)

Then I wonder why -- was not added automatically without braces (mandatory)

last = true does not imply required = true. The dashes are only mandatory if the last positional argument is indeed required. If it isn't, the dashes can be left off because if you omit the last positional argument then the other arguments will still work without the dashes and don't need any separation from the optional positional argument. Long explanation, but that's what's going on in my opinion.

mre

comment created time in 3 days