Simon Dahlbacka

[Enter steps to reproduce below:] 1. ... 2. ... **Atom Version**: 1.7.3 **System**: Mac OS X 10.11.4 **Thrown From**: [git-projects](https://github.com/prrrnd/atom-git-projects) package, v1.17.0 ### Stack Trace Uncaught Error: channel closed ```...

no-deeply-nested-dependent-keys-with-each: false positive

1

A dependent key like `[email protected],[email protected]` is reported as an error even though it should be fine.

namespace mismatch

6

# Bug report Given the following WSDL [AFO.wsdl.zip](https://github.com/savonrb/savon/files/5401149/AFO.wsdl.zip) and the following test code: ``` require 'bundler/inline' gemfile do source 'https://rubygems.org' gem 'savon' end pp client = Savon.client(wsdl: 'AFO.wsdl', log: true,...

kubernetes_manifest: inconsistent result after apply, [] vs null

2

### Terraform Version, Provider Version and Kubernetes Version ``` terraform -v Terraform v1.1.9 on darwin_amd64 + provider registry.terraform.io/anasinnyk/onepassword v1.2.1 + provider registry.terraform.io/hashicorp/helm v2.5.1 + provider registry.terraform.io/hashicorp/kubernetes v2.11.0 cert-manager 1.8.0 installed...

This is not the correct controller for this cluster.

2

I might be doing something stupid, but: ``` required_providers { ... kafka = { source = "Mongey/kafka" version = "0.4.3" } } ``` ``` provider "kafka" { bootstrap_servers = split(",",...

Suboptimal pod order

1

If I deploy the e.g. the kafka chart into rancher I end up with this:  In addition to this being confusing since the the prometheus exporter is not the...

Use _dbs_info instead of fetching the db info one-by-one

1

## Overview Slight efficiency improvement, use `_dbs_info` instead of fetching the info about the databases one by one. Note, I'm by no means a react expert, so please let me...

phobos on ruby 3.1

6

I'm seeing the following error: ``` /Users/me/.rvm/rubies/ruby-3.1.0/lib/ruby/3.1.0/psych.rb:323:in `safe_load': wrong number of arguments (given 4, expected 1) (ArgumentError) from /Users/sdahlbacka/.rvm/gems/ruby-3.1.0/gems/phobos-2.1.0/lib/phobos.rb:117:in `read_configuration' from /Users/sdahlbacka/.rvm/gems/ruby-3.1.0/gems/phobos-2.1.0/lib/phobos.rb:111:in `fetch_configuration' from /Users/sdahlbacka/.rvm/gems/ruby-3.1.0/gems/phobos-2.1.0/lib/phobos.rb:57:in `configure' from /Users/sdahlbacka/.rvm/gems/ruby-3.1.0/gems/phobos-2.1.0/lib/phobos/cli/start.rb:20:in `execute' from...

I might be missing something but do I really need to specify both `-topic` and `-group` in order to get reasonable results? I.e. ``` kt group -topic prod_m3_13_4.service_assignment.updates -group prod_fieldops_13_4_work_order_tx...

changes to projected volumes not detected properly

3

```yaml volumes: - configMap: defaultMode: 420 name: kafka-jmx-configmap optional: false name: jmx-config - name: tls-conf projected: defaultMode: 420 sources: - secret: name: kafka-secret optional: false - secret: items: - key:...