Projects & Stories

Gitlab runner clean-up caches

photo_small If you are using the gitlab runner on your system you probably already saw the pile of cache containers he leaves after running pipelines. Thats nessecary cause .. well its a cache and could be reused. But I think after a certain amount of time its ok to clean-up the mess. If you search for it you probably end up with the gitlab-runner-docker-cleanup repository. It will clean-up cache containers after a certain threshold is reached. Since the git []

ODB2, DealerTool and Linux

photo_small Sometimes I am wondering myself why people pay a lot of money for closed-source software when they can use open-source for free. This time I simply wanted to read my ECU for errors and some sensor information. If you quickly search for "Triumph" and "ECU" you will end up with expensive Window Programms. But if you dig a little bit deeper. You will know that reading your ECU is pretty much standardized, whether it is a car or y []

Sidekiq 3 Memory Killer

photo_small My Sidekiq 3 installation seams to be very hungry in respect of memory. If you dig through the Net you'll find a lot of similar reports. For e.g. the unicorn web worker a memory-killer script exists which should prevent running into Madland. So I thought I take an example and do a similar thing for the sidekiq workers. If you give them time and send a graceful kill signal there shouldn't be any data-loss either. #!/bin/bash # check if script is []

SystemStackError: stack level too deep

photo_small I just had some trouble running a intense ruby task. The result was following error: SystemStackError: stack level too deep /home/diaspora/diaspora/app/models/aspect_membership.rb:13:in `block in <class:AspectMembership>' /home/diaspora/diaspora/app/models/user/connecting.rb:46:in `remove_contact' /home/diaspora/diaspora/app/models/user/connecting.rb:62:in `disconnect' /home/diaspora/diaspora/app/models/aspect_membership.rb:14:in `block in []

Prevent Spotify from "freezing" on Linux

photo_small I am a big fan of the Awesome-Windows-Manager for Linux but since a couple of weeks the Spotify-Client is freezing the X-Server for couple of seconds after a track change happened. I've already been thinking about that this has something to do with the track notification from spotify. After some research I discovered the option ui.track_notifications_enabled. After disabling the track notification, Spotify worked quite well again! It can be used []