Paweł Janowski

Hi, I have the same problem [https://obrazki.elektroda.pl/2770627400_1579946929.jpg](https://obrazki.elektroda.pl/2770627400_1579946929.jpg). Im trying read Amiga disk on PC 3,5 Floppy Drive. Im trying RPM too - but the same error.

[https://obrazki.elektroda.pl/2319567800_1615122708.png](https://obrazki.elektroda.pl/2319567800_1615122708.png) Another floppy drive works with my FluxEngine! [https://www.youtube.com/watch?v=BbFkaMgtkto&ab_channel=8-Bitz](https://www.youtube.com/watch?v=BbFkaMgtkto&ab_channel=8-Bitz)

I have similar error : ` public ActionResult WhoAmI() { Dictionary result = new Dictionary(); result.Add("OS Platform", Environment.OSVersion.Platform.ToString()); using (var cn = new LdapConnection()) { // connect cn.Connect(); // bind...

hello, which commit will add this to master ? Regards Pawel

/sig Network

yes, it dosnt problem with kustomize but problem z podSelector matching on NetworkPolicy Kustomize only generate additional selectors to objects as NetworksPolicy / Service ``` podSelector: matchLabels: application-component: "00000" -...

example (based on first description of this issue) @ kustomization.yaml (...) ``` commonLabels: environment : dev application-component: "00000" ``` (...) the Kustomize generate additional labels to Kinds as Deployment, NetworkPolicy,...

@thockin Hi, the failing is the podSelector casting the value of "00000" in NetworkPolicy. The same value "00000" are corrected interpeting by Service. On Service the podSelector matchLabels works fine....

@aojea yes, I know how works the NP. When i put the new label (commonLabels via Kustomize) the NP dosnt works properly with the new podSelector matchLabels - i think...

Ok, i Check it on another CNI. The my CNI is the NCP (VMWare) ... but the on NetworkPolicy: when i edit the NC by hand ``` kubeclt -n {ns}...