profile
viewpoint

feuerrot/aseag-python 11

Das sollte mal zu einer vernünftigen API-Implementation werden, ist derzeit aber einfach nur ein Client

feuerrot/dp2retina 5

PCB to connect an iPad 3/4 display to a common displayport

feuerrot/dorfdoor 3

ssh, eine Tür und etwas derp

feuerrot/chaoscontrol 1

c-foo, um irgendwann™ mal das Chaosdorf per CAN steuern zu können.

feuerrot/czds-dl 1

Downloads zone files from https://czds.icann.org

feuerrot/geier 1

Sammlung aller(?) Geier

babiel/puppet-postfix 0

Puppet Module for managing Postfix (non-authoritative fork)

crackwitz/ut61c-ir-dongle 0

UNI-T UT61C IR dongle

push eventfeuerrot/mpzbc

Markus Witt

commit sha 927d8f098ac5a4f7e3a5e62092058d81b876e8a7

fix: normalize env parsing log

view details

push time in 14 days

push eventfeuerrot/mpzbc

Markus Witt

commit sha cd2c6c883cc3fd05c436803a7a4bd3f388f126a6

fix: use mpdVolumeDelta to calculate new volume

view details

push time in 14 days

push eventfeuerrot/mpzbc

Markus Witt

commit sha 3048ecd4e588265d840a1b4df2e1df53467a0713

feat: add setting for volume step size

view details

push time in 14 days

push eventfeuerrot/mpzbc

Markus Witt

commit sha 48efd809a2b88255daf9ab2e3cdfb94e0f504ff5

ci: do docker stuff

view details

push time in 15 days

release feuerrot/mpzbc

v0.1.0

released time in 15 days

created tagfeuerrot/mpzbc

tagv0.1.0

created time in 15 days

delete tag feuerrot/mpzbc

delete tag : v0.2.0

delete time in 15 days

delete tag feuerrot/mpzbc

delete tag : v0.1.7

delete time in 15 days

delete tag feuerrot/mpzbc

delete tag : v0.1.6

delete time in 15 days

push eventfeuerrot/mpzbc

Markus Witt

commit sha cae5174cfd562822dce7da1c14082cbc2e45146c

build: add Dockerfile & automatic releases

view details

Markus Witt

commit sha 5cca97bb67045aefad39d55498e3ca279c76a877

fix: print errors during mqtt message handling

view details

push time in 15 days

delete tag feuerrot/mpzbc

delete tag : v0.1.6

delete time in 15 days

delete tag feuerrot/mpzbc

delete tag : v0.1.7

delete time in 15 days

delete tag feuerrot/mpzbc

delete tag : v0.1.0

delete time in 15 days

delete tag feuerrot/mpzbc

delete tag : v0.1.1

delete time in 15 days

delete tag feuerrot/mpzbc

delete tag : v0.1.2

delete time in 15 days

delete tag feuerrot/mpzbc

delete tag : v0.1.3

delete time in 15 days

delete tag feuerrot/mpzbc

delete tag : v0.1.4

delete time in 15 days

delete tag feuerrot/mpzbc

delete tag : v0.1.5

delete time in 15 days

delete tag feuerrot/mpzbc

delete tag : v0.1.8

delete time in 15 days

delete tag feuerrot/mpzbc

delete tag : v0.1.9

delete time in 15 days

delete tag feuerrot/mpzbc

delete tag : v0.1.10

delete time in 15 days

delete tag feuerrot/mpzbc

delete tag : v0.1.11

delete time in 15 days

push eventfeuerrot/mpzbc

Markus Witt

commit sha 5a2dcb14b082030aac2b88cabcb8bb8b1de914d7

fix(ci): use two jobs for tag&release

view details

push time in 15 days

push eventfeuerrot/mpzbc

Markus Witt

commit sha 50538391a9876e8ad6b8738459c451794a820222

fix(ci): do a new checkout after go-semrel

view details

push time in 15 days

push eventfeuerrot/mpzbc

Markus Witt

commit sha 4a3c0eb45ad66ef25ba021fc796495d0c27ca538

fix(ci): skip the prerelease

view details

push time in 15 days

push eventfeuerrot/mpzbc

Markus Witt

commit sha 6c3b177d414d650c042d223858b097826337909c

fix(ci): yet another try for automatic semantic releases

view details

push time in 15 days

push eventfeuerrot/mpzbc

Markus Witt

commit sha 13d92758f518f2c4ce6275beeb22ed433d7de045

fix: print errors during mqtt message handling

view details

push time in 15 days

push eventfeuerrot/mpzbc

Markus Witt

commit sha dd2f500430d11decaac67dffb4d284add7d09a8e

ci: enable go-semrel prerelease

view details

push time in 15 days

push eventfeuerrot/mpzbc

Markus Witt

commit sha ef2f463fab73848ae83a022f619bfd6896d48390

fix(ci): test another variant

view details

push time in 16 days

push eventfeuerrot/mpzbc

Markus Witt

commit sha 2518e2d992af9da346349e4cdcd3a5628a16762e

fix(ci): fix yaml syntax

view details

push time in 16 days

push eventfeuerrot/mpzbc

Markus Witt

commit sha a0a421f4d75e4356c92f762efb69ab26410f14cc

fix(ci): run release on create

view details

push time in 16 days

push eventfeuerrot/mpzbc

Markus Witt

commit sha b07373a8c3eb31d9ec330995d2f0b0248679f28d

fix(ci): yet another try to fix the ci config

view details

push time in 16 days

push eventfeuerrot/mpzbc

Markus Witt

commit sha 40379e84f7661dae7592c5aff5b62b0266e3c690

fix(ci): run gosemrel & goreleaser together

view details

push time in 16 days

push eventfeuerrot/mpzbc

Markus Witt

commit sha 9d6259a5e66bf7f9e481c0427cd210e6b50daa42

ci: try using goreleaser only

view details

push time in 16 days

push eventfeuerrot/mpzbc

Markus Witt

commit sha 74449f93551f37e272cdb45d4e85e15200fac498

fix: add correct gitignore

view details

push time in 16 days

push eventfeuerrot/mpzbc

Markus Witt

commit sha 85126a70ed03f16c889e516d2c0d740c44fec030

ci: add goreleaser config

view details

push time in 16 days

push eventfeuerrot/mpzbc

Markus Witt

commit sha 3ddd6b7ea1d36d0e3014d76c16e70c76d8a3f0b6

build: add Dockerfile

view details

Markus Witt

commit sha b338a6ba3ac16d93e5cc31f3a6154db971042b19

ci: add automatic releases

view details

push time in 16 days

push eventfeuerrot/mpzbc

Markus Witt

commit sha c35cb36314e73384250b6c3c614a5b9e048d61c1

fix: improve logging

view details

push time in 16 days

create barnchfeuerrot/mpzbc

branch : master

created branch time in 16 days

created repositoryfeuerrot/mpzbc

created time in 16 days

startedearthly/earthly

started time in a month

startedearthly/earthly

started time in a month

MemberEvent

push eventfeuerrot/gomumblesoundboard

Fionera

commit sha a74d443fe899dc53a0013fe68f2ac8e649b61bdc

Fix duplicate groups

view details

Fionera

commit sha 10210839f98fd0634a17a64bbf3a367a49d0875c

Formatting

view details

Fionera

commit sha d3a04993f23f9a92b8fbe8d8c877c76532337d6c

fix more stuff

view details

Fionera

commit sha 08d79944f284b601d8c4f239fea4a088eb071fe2

Merge branch 'master' into master

view details

Markus Witt

commit sha d582d000d33542b848c27ad6bf7098b75aff9165

Merge pull request #2 from fionera/master

view details

push time in 2 months

PR merged feuerrot/gomumblesoundboard

Fix duplicate groups
+250 -216

0 comment

3 changed files

fionera

pr closed time in 2 months

push eventfeuerrot/gomumblesoundboard

Markus Witt

commit sha 4f3be430a4ceaeb7ded6ca5e191297b05b51e291

fix: group by folders

view details

push time in 2 months

push eventfeuerrot/gomumblesoundboard

Fionera

commit sha 4949873c5962c3d2cb8f2cf70eb79f644fe2c14b

Add folders

view details

Markus Witt

commit sha 76f68955ea67f1192c5c5c78d36c21f205cd04f1

Merge pull request #1 from fionera/master Add folders

view details

push time in 2 months

PR merged feuerrot/gomumblesoundboard

Add folders
+46 -33

0 comment

4 changed files

fionera

pr closed time in 2 months

issue commentminio/minio

missing cleanup of tmp data on IncompleteBody error

@vadmeste You can try. I did on my machine and was also not able to trigger the bug again - as soon as the client process is terminated or runs into the timeout, the corresponding connection from nginx to minio is closed which triggers a cleanup.

Would it be useful to capture data using mc admin obd the next time we run into this error or is there any other way, to dump the current internal state of a minio process?

feuerrot

comment created time in 2 months

issue commentminio/minio

missing cleanup of tmp data on IncompleteBody error

The problem happened twice and during both times we had proxy-send-timeout and proxy-read-timeout in our nginx ingress controller configuration. After the last occurence the timeout configuration was removed and since then there was no further one.

I was also not able to reproduce the bug using a local nginx with configured timeouts.

feuerrot

comment created time in 2 months

issue commentminio/minio

missing cleanup of tmp data on IncompleteBody error

@vadmeste The disks are logical volumes on the host, using ext4 as their fs:

/dev/mapper/vg1-k8s1 on /mnt/disks/1 type ext4 (rw,relatime,data=ordered)
feuerrot

comment created time in 2 months

issue commentminio/minio

missing cleanup of tmp data on IncompleteBody error

@vadmeste the directories were deleted, because they used all of the remaining free disk space.

/mnt/disks/1
   13,9 GiB [##########] /.minio.sys
    5,0 GiB [###       ] /[bucket name]
  458,0 MiB [          ] /[another bucket]
!  16,0 KiB [          ] /lost+found

I don't have additional information and I'm also not quite sure, if this is a problem in minio or our setup. Currently I'm still not able to reproduce the bug using concurrent uploads and sending only parts of the body for some of them - as soon as the client closes it's connection (using ^C with the python client, which results in the /has incomplete body-error) the temporary files of this connection get removed.

feuerrot

comment created time in 2 months

fork feuerrot/SPL

SOLIPSISTIC PUBLIC LICENSE

fork in 2 months

push eventfeuerrot/gomumblesoundboard

Markus Witt

commit sha f4f20e4dd2986a5acc57cc19cffa6c0cb21934ff

feat: add restart endpoint

view details

push time in 2 months

push eventfeuerrot/p14753

Markus Witt

commit sha ec5b5b859b40c30979e26dc96ca5d3ceabec0b4f

docs: add README.md

view details

push time in 2 months

create barnchfeuerrot/p14753

branch : master

created branch time in 2 months

created repositoryfeuerrot/p14753

created time in 2 months

issue openedminio/minio

missing cleanup of tmp data on IncompleteBody error

Expected Behavior

If there is an error during PutObject the temporary files/directories below `.minio.sys/tmp which were created for the request should be cleaned up.

Error:

API: PutObject(bucket=[bucket name], object=[object])
Time: 16:15:55 UTC 08/17/2020
DeploymentID: ebaef8a7-6ccc-4ab2-9314-9aaeea8bec7a
RequestID: 162C1A562572B633
RemoteHost: [remote host]
Host: hostname
UserAgent: Go-http-client/1.1
Error: /has incomplete body
       6: github.com/minio/minio@/cmd/erasure-object.go:697:cmd.erasureObjects.putObject()
       5: github.com/minio/minio@/cmd/erasure-object.go:566:cmd.erasureObjects.PutObject()
       4: github.com/minio/minio@/cmd/erasure-sets.go:674:cmd.(*erasureSets).PutObject()
       3: github.com/minio/minio@/cmd/erasure-zones.go:552:cmd.(*erasureZones).PutObject()
       2: github.com/minio/minio@/cmd/object-handlers.go:1552:cmd.objectAPIHandlers.PutObjectHandler()
       1: net/http/server.go:2036:http.HandlerFunc.ServeHTTP()

Current Behavior

Due to a currently unknown reason this error happens sometimes on our system and it leaves temporary directories:

[root@hostname ~]# ls -la /mnt/disks/1/.minio.sys/tmp/
[…]
drwxr-xr-x  3 root root 4096 17. Aug 18:15 a1e14c4b-b3fb-4af4-b3c0-df28edab0aa3
drwxr-xr-x  3 root root 4096 17. Aug 18:11 ad22102f-076c-4551-9517-27fad4ece4bf

(timestamps in CEST, so the a1e14c4b-directory belongs to the error above. I don't have the content anymore as someone already did a cleanup)

Possible Solution

I'd suspect that this is a bug somewhere in easureObjects.putObject() - there is a defer which should clean up the temporary files, but maybe it doesn't catch the tempEasureObj?

Steps to Reproduce (for bugs)

I'm currently not able to reproduce the bug

Regression

Unknown

Your Environment

  • Version used (minio --version): RELEASE.2020-08-16T18-39-38Z
  • Server setup and configuration: we use the minio/minio docker container running on kubernetes using nginx as our ingress controller

created time in 2 months

more