Manuel Fittko

*bump* also seeing the after hook failure in our main repo. Would be cool if we could get this out.

For us the problem could be identified as iterating through a non thread-safe array in the _manifest.json.erb_ file that is part of our asset pipeline, so maybe that helps some...

I also have this issue, this extension is also not compatible with other extensions that change the battery indicator like this one https://extensions.gnome.org/extension/817/battery-status/. Please fix!

@julio641742 Super easy to fix: https://github.com/julio641742/extend-panel-menu/blob/4fa4e4fb6b87c81e38dfd83c1d9efe41cfb2dd08/indicators/power.js#L84 => `this._percentageLabel.clutter_text.set_markup('' + Math.round(this._power._proxy.Percentage) + " %");` @roizcorp You can fix it yourself, just change the respective line here: _~/.local/share/gnome-shell/extensions/extend-panel-menu@julio641742/indicators/power.js_

I am on a linux notebook and I'm getting this very often recently with the google calendar or trello tabs, which also sometimes already cleared my input, which is super...

Is this whole project even maintained any more? I have the slight feeling that this docker compose integration approach is, while being super attractive at first, just another dead end...

+1

I second this, tests are also becoming much slower and with the retry option enabled on CI, we're only interested in videos of failing retries

getting the same errors, when installing the qt packages as suggested [here](https://github.com/thoughtbot/capybara-webkit/wiki/Installing-Qt-and-compiling-capybara-webkit#debian--ubuntu) on debian stretch :(

I now switched to using local caching with EFS as backing cache filesystem. Hope that this will be fixed for ECR soon though! I saw that there was some progress...