Some are even worse than this. When I was in Portugal, the machine said "Press (1) for GBP. Press (2) for EUR.", then on the next screen, after you select "(2) for EUR", it says "Rate will Apply. Please confirm. (1) Accept conversion (2) Reject Conversion". If you select "Accept conversion", it overrides your currency decision and you pay in GBP with their markup fee...
I saw the same in an ATM in Greece. The first screen wanted me to let them convert the currency (at a 20% markup), I declined, and the second screen said "are you sure? You might be charged a lot" and had "accept" and "decline" where the small print said "do you want us to convert anyway?".
The text is crossed out using Unicode combining characters of a strikethrough. This allows it to display without any specific formatting support, but it does require that the font support those characters. The font you're using doesn't support the characters, so it displays boxes, instead.
I tried to work out the problem myself first (using only the text) and accidentally used the diameter as the radius just like ChatGPT! Granted I haven't really tackled any maths problems for many years though.
If you mean one instance in each pod, then each should be labelled differently and you can filter down to one instance.
If you mean running multiple instances in each pod (and container?), then the standard kubectl log output will also have them all joined together. For both of those, you would need to add another unique identifier to each line, or run each instance in a separate container so you can submit the logs with the pod name and container name combined being the unique identifier.
Have you had a look at AsiaRF[1]? If you are building an access point you are probably looking for more specific cards. You do miss out on things like hardware offloading if you go down that route afaik though but it may not matter due to the extra processing power you tend to get.
I don't know much about it but things like DBDC/MIMO are probably wanted. Other people may be able to comment more about this though.
I just went down the route of using a Banana Pi R3 with OpenWRT in the end though[2]. The R4 does exist now with Wifi 7 though[3].
It's robust. I hamstrung the model solution by forcing pistonAcceleration to be 0, and forcing hingeAcceleration to be 0 during the first second, but it still "caught" and balanced the ball.
It's a complete con...
reply