profile
viewpoint
Benjamin Schmid bentolor @exxcellent Ulm, Germany http://twitter.com/bentolor Head of Division & Technology Advisor @exxcellent

bentolor/docker-nextcloud-collabora-postgresql-letsencrypt 4

Docker-compose based NextCloud installation with LetsEncrypt SSL, PostgreSQL backend, Collabora online office, supervisord cron

bentolor/gradle-maven-multimodule-kotlindsl 3

An example Gradle 5 Kotlin DSL Java library project which consists of multiple modules to be published/released as Maven modules

bentolor/docker-dind-awscli 2

A Docker image for Docker-in-Docker (dind) with AWS CLI v2 awscli tool included

bentolor/docker-bamboo-agent 1

An updated Docker-based Bamboo Agent aimed and building Java & Web-based projects

bentolor/gitcity 1

A vsiual VR 3D exploration of your Git history

bentolor/anbox-modules 0

Anbox kernel modules

bentolor/angular-strap 0

AngularJS 1.2+ native directives for Twitter Bootstrap 3.

bentolor/asciidoctor-reveal.js 0

:crystal_ball: A reveal.js converter for Asciidoctor and Asciidoctor.js. Write your slides in AsciiDoc!

bentolor/asciidoctor-stylesheet-factory 0

:art: A factory for producing stylesheets to theme AsciiDoc HTML5 output. Assembled using Compass, Sass and Foundation.

bentolor/atom-kotlin-language 0

Adds syntax highlighting to Kotlin files in Atom

startedcheckly/headless-recorder

started time in 3 days

push eventbentolor/jsr303-playground

dependabot[bot]

commit sha 4b1994c5cddc05b599499c57e166a0866fc9dd92

Bump junit from 4.8.2 to 4.13.1 Bumps [junit](https://github.com/junit-team/junit4) from 4.8.2 to 4.13.1. - [Release notes](https://github.com/junit-team/junit4/releases) - [Changelog](https://github.com/junit-team/junit4/blob/main/doc/ReleaseNotes4.13.1.md) - [Commits](https://github.com/junit-team/junit4/compare/r4.8.2...r4.13.1) Signed-off-by: dependabot[bot] <support@github.com>

view details

Benjamin Schmid

commit sha 9806ee6994ed1396d155a281b89ffdc9325a656c

Merge pull request #1 from bentolor/dependabot/maven/junit-junit-4.13.1 Bump junit from 4.8.2 to 4.13.1

view details

push time in 3 days

PR merged bentolor/jsr303-playground

Bump junit from 4.8.2 to 4.13.1 dependencies

Bumps junit from 4.8.2 to 4.13.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/junit-team/junit4/releases">junit's releases</a>.</em></p> <blockquote> <h2>JUnit 4.13.1</h2> <p>Please refer to the <a href="https://github.com/junit-team/junit/blob/HEAD/doc/ReleaseNotes4.13.1.md">release notes</a> for details.</p> <h2>JUnit 4.13</h2> <p>Please refer to the <a href="https://github.com/junit-team/junit/blob/HEAD/doc/ReleaseNotes4.13.md">release notes</a> for details.</p> <h2>JUnit 4.13 RC 2</h2> <p>Please refer to the <a href="https://github.com/junit-team/junit4/wiki/4.13-Release-Notes">release notes</a> for details.</p> <h2>JUnit 4.13 RC 1</h2> <p>Please refer to the <a href="https://github.com/junit-team/junit4/wiki/4.13-Release-Notes">release notes</a> for details.</p> <h2>JUnit 4.13 Beta 3</h2> <p>Please refer to the <a href="https://github.com/junit-team/junit4/wiki/4.13-Release-Notes">release notes</a> for details.</p> <h2>JUnit 4.13 Beta 2</h2> <p>Please refer to the <a href="https://github.com/junit-team/junit4/wiki/4.13-Release-Notes">release notes</a> for details.</p> <h2>JUnit 4.13 Beta 1</h2> <p>Please refer to the <a href="https://github.com/junit-team/junit4/wiki/4.13-Release-Notes">release notes</a> for details.</p> <h2>JUnit 4.12</h2> <p>Please refer to the <a href="https://github.com/junit-team/junit/blob/HEAD/doc/ReleaseNotes4.12.md">release notes</a> for details.</p> <h2>JUnit 4.12 Beta 3</h2> <p>Please refer to the <a href="https://github.com/junit-team/junit/blob/HEAD/doc/ReleaseNotes4.12.md">release notes</a> for details.</p> <h2>JUnit 4.12 Beta 2</h2> <p>No release notes provided.</p> <h2>JUnit 4.12 Beta 1</h2> <p>No release notes provided.</p> <h2>JUnit 4.11</h2> <p>No release notes provided.</p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/junit-team/junit4/blob/main/doc/ReleaseNotes4.13.1.md">junit's changelog</a>.</em></p> <blockquote> <h2>Summary of changes in version 4.13.1</h2> <h1>Rules</h1> <h3>Security fix: <code>TemporaryFolder</code> now limits access to temporary folders on Java 1.7 or later</h3> <p>A local information disclosure vulnerability in <code>TemporaryFolder</code> has been fixed. See the published <a href="https://github.com/junit-team/junit4/security/advisories/GHSA-269g-pwp5-87pp">security advisory</a> for details.</p> <h1>Test Runners</h1> <h3>[Pull request <a href="https://github-redirect.dependabot.com/junit-team/junit4/issues/1669">#1669</a>:](<a href="https://github-redirect.dependabot.com/junit-team/junit/pull/1669">junit-team/junit#1669</a>) Make <code>FrameworkField</code> constructor public</h3> <p>Prior to this change, custom runners could make <code>FrameworkMethod</code> instances, but not <code>FrameworkField</code> instances. This small change allows for both now, because <code>FrameworkField</code>'s constructor has been promoted from package-private to public.</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/junit-team/junit4/commit/1b683f4ec07bcfa40149f086d32240f805487e66"><code>1b683f4</code></a> [maven-release-plugin] prepare release r4.13.1</li> <li><a href="https://github.com/junit-team/junit4/commit/ce6ce3aadc070db2902698fe0d3dc6729cd631f2"><code>ce6ce3a</code></a> Draft 4.13.1 release notes</li> <li><a href="https://github.com/junit-team/junit4/commit/c29dd8239d6b353e699397eb090a1fd27411fa24"><code>c29dd82</code></a> Change version to 4.13.1-SNAPSHOT</li> <li><a href="https://github.com/junit-team/junit4/commit/1d174861f0b64f97ab0722bb324a760bfb02f567"><code>1d17486</code></a> Add a link to assertThrows in exception testing</li> <li><a href="https://github.com/junit-team/junit4/commit/543905df72ff10364b94dda27552efebf3dd04e9"><code>543905d</code></a> Use separate line for annotation in Javadoc</li> <li><a href="https://github.com/junit-team/junit4/commit/510e906b391e7e46a346e1c852416dc7be934944"><code>510e906</code></a> Add sub headlines to class Javadoc</li> <li><a href="https://github.com/junit-team/junit4/commit/610155b8c22138329f0723eec22521627dbc52ae"><code>610155b</code></a> Merge pull request from GHSA-269g-pwp5-87pp</li> <li><a href="https://github.com/junit-team/junit4/commit/b6cfd1e3d736cc2106242a8be799615b472c7fec"><code>b6cfd1e</code></a> Explicitly wrap float parameter for consistency (<a href="https://github-redirect.dependabot.com/junit-team/junit4/issues/1671">#1671</a>)</li> <li><a href="https://github.com/junit-team/junit4/commit/a5d205c7956dbed302b3bb5ecde5ba4299f0b646"><code>a5d205c</code></a> Fix GitHub link in FAQ (<a href="https://github-redirect.dependabot.com/junit-team/junit4/issues/1672">#1672</a>)</li> <li><a href="https://github.com/junit-team/junit4/commit/3a5c6b4d08f408c8ca6a8e0bae71a9bc5a8f97e8"><code>3a5c6b4</code></a> Deprecated since jdk9 replacing constructor instance of Double and Float (<a href="https://github-redirect.dependabot.com/junit-team/junit4/issues/1660">#1660</a>)</li> <li>Additional commits viewable in <a href="https://github.com/junit-team/junit4/compare/r4.8.2...r4.13.1">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)
  • @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

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+1 -1

0 comment

1 changed file

dependabot[bot]

pr closed time in 3 days

startedtmorin/ff-cpdn

started time in 3 days

startedhadolint/hadolint

started time in 4 days

startedhadolint/hadolint

started time in 4 days

push eventbentolor/docker-nextcloud-collabora-postgresql-letsencrypt

Benjamin Schmid

commit sha 528b38ce10d29883ea16ec34d622672762068ce1

fix(supervisord): allow supervisor to run as root in container New supervisord fail to start unless explicitly allowed to run as root. It's a good point but for now we'll stick to the current approach and trust on container isolation.

view details

push time in 5 days

push eventexxcellent/programming-challenge

Benjamin Schmid

commit sha a1a6d1808f47a8cf223d7674e0929bceef313254

build(*): update dependencies

view details

Benjamin Schmid

commit sha 46eb8fcbf18f913e1422d9863660a0b1af17abb9

Merge branch 'challenge-scaffold' into challenge-weatherdata

view details

push time in 7 days

push eventexxcellent/programming-challenge

Benjamin Schmid

commit sha a1a6d1808f47a8cf223d7674e0929bceef313254

build(*): update dependencies

view details

Benjamin Schmid

commit sha d61d212373994064e64aa98a6509cfd5e57b0cc0

Merge branch 'challenge-scaffold' into challenge-nestedlist

view details

push time in 7 days

push eventexxcellent/programming-challenge

Benjamin Schmid

commit sha a1a6d1808f47a8cf223d7674e0929bceef313254

build(*): update dependencies

view details

push time in 7 days

push eventexxcellent/programming-challenge

Benjamin Schmid

commit sha ed821ce24a51019ecc29c4304ff2d27590bdc8aa

build(*): update dependencies

view details

push time in 7 days

issue commentterraform-providers/terraform-provider-aws

data.aws_ecs_task_definition: Failed getting task definition

FYI for everybody else stumbling over the issue: @skorfmann illustrated in this MR https://github.com/terraform-providers/terraform-provider-aws/pull/10247 a better workaround using aws_ecs_task_definition.self.revision and explains why the discussed depends_on approach is not what you want!

This is working around the issue of not having a task definition when the resources are initially rolled out. The documetation example of directly referecing "task_family" doesn't work and exits with an error when initially applying it. See also this issue #1274

The reason is, that data sources don't handle missing data gracefully. Unfortunately, that's not gonna be addressed, as stated here: hashicorp/terraform#16380 (comment). One of the suggested workarounds is, to add an explict depends_on. However, this causes a potential change in the terraform plan output, even though it's not actually going to change. Furthermore, it's discourage by the Terraform documentation itself.

This thread mentions a few other workarounds, but none of them seem to be suitable hashicorp/terraform#16380

aws_ecs_task_definition.self.revision can only be referenced, once the resource is created (in contrast to family, which is already present in code). Apparently, this allows Terraform to correctly resolve the dependencies and makes the data source behave as expected.

sychevsky

comment created time in 11 days

startedatc1441/ATC_MiThermometer

started time in 12 days

push eventbentolor/docker-nextcloud-collabora-postgresql-letsencrypt

Benjamin Schmid

commit sha 22779ad161a980443e46cbfc314b998dea1036f9

fix(Startup failure): pin to PostgreSQL 12 New PostgreSQL 13 requires manual upgrade. Stick to 12 as officially its already newer than the currently supported version by Nextcloud

view details

push time in 17 days

pull request commentbentolor/java9-in-action

Update README.asciidoc

Thanks, @gagan9551 : I understood that you propose to better advertise the provides examples. Rephrased your proposal a little with 105d6ed493a36b05f196ffdacb2f93467674916b. Thanks!

gagan9551

comment created time in 18 days

push eventbentolor/java9-in-action

Benjamin Schmid

commit sha 105d6ed493a36b05f196ffdacb2f93467674916b

doc(README): better advertise the examples

view details

push time in 18 days

issue commentbentolor/idea-cli-inspector

Does it run with other IDEs

Thanks for the feedback!

Just to clarify the various warnings:

WARNING: An illegal reflective access operation has occurred

This is a plain groovy issue with an interop issue with the JVM. Ecpect it as "normal" until Groovy itself solves it.

2020-09-23 14:09:25,493 [  21969]  ERROR - spection.InspectionsResultUtil - Descriptions are missed for tools: PreviewMustBeTopLevelFunction, PreviewNeedsComposableAnnotation, PreviewDimensionRespectsLimit, PreviewAnnotationInFunctionWithParameters
java.lang.Throwable: Descriptions are missed for tools: PreviewMustBeTopLevelFunction, PreviewNeedsComposableAnnotation, PreviewDimensionRespectsLimit, PreviewAnnotationInFunctionWithParameters

These are typicals issue with inspections: They tend to work in the UI-mode but some fail sporadically in headless mode. They might reveal bugs in the inspection code and you can report them to Jetbrains.

You should have a look on those, because they might inhibit the successful run of other inspections. If in doubt, comment them out.

disconnect3d

comment created time in a month

pull request commentasciidoctor/asciidoclet

Support for Java 11

So much work has already gone in this and based on the comments the outcome should be feasible.

How about just merging this in a 2.0-alpha release & branch or something release so people can actually use it and then trying to get the other things pinpointed/done?

AFAIK mostly upgrade of asciidoctor4j should also go in a 2.0 release, right?

Am I missing further work to be done?

chrisvest

comment created time in a month

push eventbentolor/idea-cli-inspector

Benjamin Schmid

commit sha 7f07ae0dac4a562e78cda5dac4497d1bdc117bea

fix(Container): add git to avoid startup error

view details

push time in a month

pull request commentbentolor/idea-cli-inspector

Bump idea version

Thanks @LionZXY for the bump.

The new version is already built and up on Docker Hub.

I just added another minor fix (adding git which seems to be no longer present in the base layer).

LionZXY

comment created time in a month

created tagbentolor/idea-cli-inspector

tagidea-2020.2.1

A little command-line tool to integrate the awesome IntelliJ IDEA code inspections in your continuous integration (CI) process using Jenkins, Bamboo, et. al.

created time in a month

push eventbentolor/idea-cli-inspector

lionzxy

commit sha 7915bbe2929f2e095a0753683ae018477dcfd31e

Bump idea version

view details

Benjamin Schmid

commit sha dbc4db19cd1bd8d403201285d965cec2cc174fce

Merge pull request #23 from LionZXY/master Bump idea version

view details

push time in a month

pull request commentbbernhard/signal-cli-rest-api

build(Dockerfile): reduce image size from 2G GB to ~0.4GB

Thanks for your quick feedback! All fine – just stumbled over it in my GH history and wanted to give a quick bump.

I appreciate your precaution to not break people's setup!

bentolor

comment created time in 2 months

pull request commentbbernhard/signal-cli-rest-api

build(Dockerfile): reduce image size from 2G GB to ~0.4GB

@bbernhard how went the testrun phase?

bentolor

comment created time in 2 months

push eventbentolor/enforce-angular-commitmessages

Benjamin Schmid

commit sha 1257b02380f2c6e6252b7d705158e69e584cd1ec

doc(README): join readmes for lazy Github

view details

push time in 2 months

push eventbentolor/enforce-angular-commitmessages

Benjamin Schmid

commit sha 3b32789910b03b3a9d9abb08aab7d041f94186de

doc(README): add note on Githubs fault

view details

push time in 2 months

push eventbentolor/enforce-angular-commitmessages

Benjamin Schmid

commit sha b6c84c34507af4f89d98976dd53da15a7b32f392

feat(hooks): provide code & descriptions

view details

push time in 2 months

create barnchbentolor/enforce-angular-commitmessages

branch : master

created branch time in 2 months

created repositorybentolor/enforce-angular-commitmessages

Git Hooks to enforce Angular-style Git commit messages on client-side as welll as server-side

created time in 2 months

push eventbentolor/microframeworks-showcase

Benjamin Schmid

commit sha c84bad96d75c76cb3c66d63938dfcf219334c557

build(gradle): upgrade to JDK11

view details

push time in 2 months

push eventbentolor/microframeworks-showcase

Benjamin Schmid

commit sha 7f0e342605670277ded5b0905eaee519bacd46ec

build(gradle): upgrade to JDK11

view details

bentolor

commit sha 0db016d4fce6258549ca798118bc0ee169832763

build(*): add test dependencies

view details

bentolor

commit sha e835fc1a333b9f71cda8e6e361dbb761df76df7e

feat(jodd): upgrade to madvoc5

view details

push time in 2 months

push eventbentolor/microframeworks-showcase

Benjamin Schmid

commit sha 7f0e342605670277ded5b0905eaee519bacd46ec

build(gradle): upgrade to JDK11

view details

push time in 2 months

create barnchbentolor/microframeworks-showcase

branch : feat/upgrade-madvoc

created branch time in 2 months

push eventbentolor/microframeworks-showcase

bentolor

commit sha 0ad9dbb6cca025075cc7e48dac1d20fd62f44d25

chore(.gitignore): ignore vscode dirs & files

view details

bentolor

commit sha 8d66c08698ac23a04691f077e8dc0c22434e1e65

build(gradle): get build running with Gradle 6

view details

bentolor

commit sha efa58ff4b78eef8aa3034a4d72e14d36b5549422

fix(spring5): remove competing log implementation

view details

bentolor

commit sha 36bfb1ff637bab158752ca94fb92efb4781c5cad

build(*): upgrade dependencies

view details

bentolor

commit sha b41f19d3a4c5c53186f2a0d150ac2bc1fc1df341

build(*): upgrade more dependencies & progress toward Gradle 7 compatibility

view details

push time in 2 months

push eventbentolor/lightningtalk-fido2-webauthn

Benjamin Schmid

commit sha 43644888f3cdbf36994b550f1183d801722c64c6

doc(presentation): increase autoslide to 7.5s

view details

push time in 2 months

push eventbentolor/lightningtalk-fido2-webauthn

bentolor

commit sha a86bac32c228888badcebed147009fb90039981e

doc(presentation): enable viewes hint and autoslide

view details

push time in 2 months

pull request commentbbernhard/signal-cli-rest-api

build(Dockerfile): reduce image size from 2G GB to ~0.4GB

Awesome @bbernhard & glad we found a working approach for all environments: Looking forward to your feedback.

bentolor

comment created time in 2 months

pull request commentbbernhard/signal-cli-rest-api

build(Dockerfile): reduce image size from 2G GB to ~0.4GB

@bbernhard No – for sure we do not want to deviate here between architectures.

I was not aware that the openjdk project itself only releases arm64 builds, so I switched now to the adoptopenjdk release: They provide builds for nearly all available Java plattforms. The JRE base image is 78MB and very small. See the 11-jre-hotspot Tag

FYI: It seems that you are using manual ways to build the images. The Docker/Github integration is quite easy and allows you singingly to enable autobuilds i.e. on tag. You can i..e. see the results of that integration here.

bentolor

comment created time in 2 months

push eventbentolor/signal-cli-rest-api

Benjamin Schmid

commit sha c00480696d1e997f79f8b02da8be3c0a47d02883

build(Docker): switch to adoptopenjdk to support armv7

view details

push time in 2 months

push eventbentolor/signal-cli-rest-api

Benjamin Schmid

commit sha a6e8cce641640708a5d373480f3c0a35f3a88305

build(Docker image): switch to JRE and Debian buster variant This should avoid potential issues in ARM environemnts with musl/alpine linux.

view details

push time in 2 months

pull request commentbbernhard/signal-cli-rest-api

build(Dockerfile): reduce image size from 2G GB to ~0.4GB

I do not have a ARM environment to test it. But I know that the musl environment sometimes causes issues.

In that case you could simply replace the 11-slim with 11-jre-slim-buster : I realized that I missed the 11-jre-slim and 11-jre-slim-buster variants which only include JRE and are even much more smaller (65MB). The buster variant works on debian so it should make no difference then regarding the musl/glibc variant.

But its obvious that I was only able to quickly test in my environment so i cannot oversee if this change would cause side effects on other platforms.

bentolor

comment created time in 2 months

PR opened bbernhard/signal-cli-rest-api

build(Dockerfile): reduce image size from 2G GB to ~0.4GB

This uses mulit-stage build to separate the build phase from the distribution image and signigicantly reduces images size.

You can find more information on Docker multistage builds here: https://docs.docker.com/develop/develop-images/multistage-build/

+11 -6

0 comment

1 changed file

pr created time in 2 months

create barnchbentolor/signal-cli-rest-api

branch : build/reduce-image-size

created branch time in 2 months

issue commentbbernhard/signal-cli-rest-api

Growing container size due to missing cleanup for /tmp/*.{jpg,mp4} files

Awesome! Thanks for you lightning fast fix!

bentolor

comment created time in 2 months

issue openedbbernhard/signal-cli-rest-api

Growing container size due to missing cleanup for /tmp/*.{jpg,mp4} files

A sudo docker container ls -s reveals the following:

58f27f04c663        bbernhard/signal-cli-rest-api            "signal-cli-rest-api"    7 days ago          Up 7 days           0.0.0.0:9922->8080/tcp                           signal-api                                   118MB (virtual 2.04GB)

On inspecting with container diff reports the following situation:

$ sudo docker container diff signal-api
C /tmp
A /tmp/10096571-0b51-41ac-84cc-44bd77a6fc4e.mp4
A /tmp/193791b7-a84c-4458-823d-6120b33c6b56.jpg
…
A /tmp/c37bebc6-c6a8-40b6-92c4-c770a97bdfeb.jpg
A /tmp/dfbea440-7709-4600-9065-7ce02fe76ba7.jpg
C /tmp/hsperfdata_root
D /tmp/hsperfdata_root/57
A /tmp/2c1f1207-e9ca-47c7-b1c3-3a7dc064b792.jpg
…

A container restart does not clean them up.

After inspecting the code it seems there is also some sort of cleanup logic. Not sure where the fallthrough is lying: func cleanupTmpFiles(paths []string) {

For me it seems that nearly no cleanup happened at all, because the file list more or less matches all media files I yet sent via the API?!

created time in 2 months

created tagbentolor/docker-dind-awscli

tagv2.0.38

A Docker image for Docker-in-Docker (dind) with AWS CLI v2 awscli tool included

created time in 2 months

push eventbentolor/docker-dind-awscli

Benjamin Schmid

commit sha efd34bee6ef67cbc1aa6016c8f5699601d45911f

doc(README): add more hints that this adresses v2 of awscli

view details

push time in 2 months

push eventbentolor/docker-dind-awscli

Benjamin Schmid

commit sha df6cad8dceac3d579d970bd239f041867cb87899

build(aws cli): print installed version in docker build

view details

push time in 2 months

startedbbernhard/signal-cli-rest-api

started time in 2 months

startedAsamK/signal-cli

started time in 2 months

push eventbentolor/java14-presentation

Benjamin Schmid

commit sha 49ab3a855f313c45c4696de8684e536b5ffa1664

chore(index.html): remove

view details

Benjamin Schmid

commit sha 92a0728d7b2e89a1f74375f5c505cf568d927006

build(index.html): add symlink to support github pages

view details

push time in 3 months

push eventbentolor/java14-presentation

Benjamin Schmid

commit sha 8f90a4c624a3441450c7281016b593f77c51c69a

doc(presentation): autoprogress

view details

push time in 3 months

issue closedarendst/Tasmota

Sleep timer / Inching / Auto turn-off functionality on button press (watering plants)

<!-- Thanks for suggesting an idea for this project. READ THIS FIRST:

Please take a few minutes to complete the requested information below. Our ability to provide assistance is greatly hampered without it. The details requested potentially affect which options to pursue. The small amount of time you spend completing the template will also help the volunteers providing the assistance to you to reduce the time required to help you.

DO NOT DELETE ANY TEXT from this template! Otherwise the issue will be auto-closed. -->

Have you looked for this feature in other issues and in the docs?
Yes

Is your feature request related to a problem? Please describe.
I migrated my Sonoff S20 lately to Tasmota and miss an important functionality: My problem is, that I use the S20 plug to water plants outdoor: With the EWELink firmware there was an "inching" functionality available which allowed me to define a custom time span after which the plug reliably would turn off automatically.

My Wifi connection outdoor is only sporadic available if at all. On demand-programming a new cycle via web interface turned out to be rather cumbersome (UI UX) or not possible (broken Wifi Link).

Therefore restoring my former functionality of just pressing the button to start on demand a new watering cycle which gets automatically turned off i.e. after 10 minutes would be a big win. Yet I drained my water barrels empty more than once…

Describe the solution you'd like
I want to be able to configure a custom time period after which the plug should turned off itself reliably.

This means i.e. after a turning on the plug by a short button press (default behavior) it will automatically turn off after my custom configured time (i.e. 10 mins). This auto-turn-off period could also apply to schedule-triggered turn-ons.

Describe alternatives you've considered
1. Manually programming a new time table entry: Doesn't work due to crappy Wifi connection. 2. Manually turning of: I forget it EVERY time! 3. Looking at the button config options: Didn't see any way to copy my desired behavior

Additional context
Nothing.

(Please, remember to close the issue when the problem has been addressed)

closed time in 3 months

bentolor

issue commentarendst/Tasmota

Sleep timer / Inching / Auto turn-off functionality on button press (watering plants)

Thanks @schrej-zz : Found a cookbook recipe similar to my use case: https://tasmota.github.io/docs/Rules/#time-delayed-auto-off-switch

Using this I found out I must enter

Rule1  ON Power1#state=1 DO RuleTimer1 4 ENDON ON Rules#Timer=1 DO Power1 Off ENDON
Rule1 1
bentolor

comment created time in 3 months

issue commentarendst/Tasmota

Sleep timer / Inching / Auto turn-off functionality on button press (watering plants)

Hi @schrej-zz : Thanks for your quick reply. Hmmm… how did I miss that?

Nevertheless: Easy does not match at least for me: I'm a little lost on how to get things working. I would access the web console an there paste something like the following ????:

Rule1  ON Power#state=1 DO RuleTimer1 4 ENDON ON Rules#Timer=1 DO Power 0 ENDON

But this is not working. Also tried Power1 instead of Power.

bentolor

comment created time in 3 months

issue openedarendst/Tasmota

Sleep timer / Inching / Auto turn-off functionality on button press (watering plants)

<!-- Thanks for suggesting an idea for this project. READ THIS FIRST:

Please take a few minutes to complete the requested information below. Our ability to provide assistance is greatly hampered without it. The details requested potentially affect which options to pursue. The small amount of time you spend completing the template will also help the volunteers providing the assistance to you to reduce the time required to help you.

DO NOT DELETE ANY TEXT from this template! Otherwise the issue will be auto-closed. -->

Have you looked for this feature in other issues and in the docs?
Yes

Is your feature request related to a problem? Please describe.
I migrated my Sonoff S20 lately to Tasmota and miss an important functionality: My problem is, that I use the S20 plug to water plants outdoor: With the EWELink firmware there was an "inching" functionality available which allowed me to define a custom time span after which the plug reliably would turn off automatically.

My Wifi connection outdoor is only sporadic available if at all. On demand-programming a new cycle via web interface turned out to be rather cumbersome (UI UX) or not possible (broken Wifi Link).

Therefore restoring my former functionality of just pressing the button to start on demand a new watering cycle which gets automatically turned off i.e. after 10 minutes would be a big win. Yet I drained my water barrels empty more than once…

Describe the solution you'd like
I want to be able to configure a custom time period after which the plug should turned off itself reliably.

This means i.e. after a turning on the plug by a short button press (default behavior) it will automatically turn off after my custom configured time (i.e. 10 mins). This auto-turn-off period could also apply to schedule-triggered turn-ons.

Describe alternatives you've considered
1. Manually programming a new time table entry: Doesn't work due to crappy Wifi connection. 2. Manually turning of: I forget it EVERY time! 3. Looking at the button config options: Didn't see any way to copy my desired behavior

Additional context
Nothing.

(Please, remember to close the issue when the problem has been addressed)

created time in 3 months

push eventbentolor/lightningtalk-fido2-webauthn

Benjamin Schmid

commit sha b9f515c445519525afa111a5da448d6614501d6b

build(Github pages): add index.html link

view details

push time in 3 months

push eventbentolor/lightningtalk-fido2-webauthn

Benjamin Schmid

commit sha 98e8d3c0e4bd8ef0869f8c675a324e1d7b984155

doc(FIDO2 Talk): revealjs based HTML presentation

view details

push time in 3 months

create barnchbentolor/lightningtalk-fido2-webauthn

branch : master

created branch time in 3 months

created repositorybentolor/lightningtalk-fido2-webauthn

FIDO2 & WebAuthn: Passwordless logins and secure 2FA (HTML5 Presentation)

created time in 3 months

issue commentJetBrains/inspection-plugin

[Discussion] Similarities & share ideas & concepts with idea-cli-inspector

@dzwicker Thanks. Upvoted: At least it seems you were able to provide a starting pointer and some assumption. For me it's more or less: "In some constellations it mostly fails, in other it mostly works for unknown reasons".

bentolor

comment created time in 3 months

startedmprograms/QMC5883LCompass

started time in 3 months

more