Javier Gómez Rodríguez

will the azure-cli supports this sometime?

We have a containerized api json service and, as we pass all the config throught environment. We set globally Content-type with the env var and when we try to update...

Ok with that. My point was about that controlling run-time environment options in tests, maybe just cleaning env hash by default, will allow to pass the tests in a reliable...

Same here (Ubuntu 14.04, chef 11.16.4) ``` ================================================================================ Error executing action `enable` on resource 'service[php-fpm]' ================================================================================ ArgumentError ------------- invalid byte sequence in US-ASCII Resource Declaration: --------------------- # In /mnt/cookbooks/supermarket/php-fpm/recipes/install.rb 51:...

Solved, locales wasn't configured in my system. Including "locale::default" recipe in my run list, and seting LANG and LC_ALL in my base recipe fix the issue. ``` include_recipe "locale::default" #...

@stisot are you using [locale cookbook](https://supermarket.chef.io/cookbooks/locale) too? I'm doing it in my [base recipe](https://github.com/RIYIC/riyic/blob/master/recipes/default.rb) and works ok https://github.com/RIYIC/riyic/blob/master/recipes/_configure_locale.rb

We have been able to solve this problem, using the token of a GitHub App (instead of GITHUB_TOKEN). In this way, the check run is associated with a specific new...

Regarding this, we finally took another path, [recently indicated in the GitHub documentation](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks#handling-skipped-but-required-checks), by using a fallback workflow that fulfills the required status check, in case the real job has...

Sorry for intruding, I'm a @tonirvega workmate. We don't see this behavior with 0.22.3, and we've been using it on AKS for the past few months until we refactored for...

> Just to add a note that we're also experiencing this, and from what I can see it does seem that when the informer disconnects and reconnects again, we're receiving...