tcas

My guess is this is all due to CloudWatch logs putlogevents failures.

By default a docker container configured with awslogs runs in "blocking" mode. As logs get logged, docker will buffer them and push to CloudWatch logs frequently. In case the log stream is faster than what the buffer can absorb, stdout/stderr get blocked and then the container will freeze on the logging write call. If putlogevents is failing, buffers are probably filling up and freezing containers. I assume most of AWS uses it's own logging system, which could cause these large, intermittent failures.

If you're okay dropping logs, add something like this to the container logging definition:

  "max-buffer-size": "25m"
  "mode": "non-blocking"

Just wait until they find your personal cell phone number and try to force you into scheduling a "time that works" on the calendar.

For certified piston aircraft, generally yes. The engines are pretty much made by a few manufacturers based on ancient designs, and while you may get some "newer" benefits in some models, such as fuel injection (instead of carborators), or digital engine control (FADEC), they're pretty much ancient technology compared to modern engines. Most still have manual mixture control for example and very limited monitoring.

The only example in that class (sub $750k) I can think off the top of my head with a better engine is DA40 NG, which uses a modified Mercedes diesel engine.

I had the same experience when I was a TA a long time ago. Reviewing the code to a homework set I noticed that two students mixed up the naming of two variables (I think min/max were switched).

I ran a whitespace sensitive diff and noticed the only difference between the two files was the author name in the header.

The professor sent a sternly worded letter to the class about not cheating, and nothing else came from it AFAIK.

As someone who's dealt with these protocols as well I agree.

I find the print quality of PDFs perfect on Zebra's as long as you keep the following in mind:

  - Make sure the DPI of the document is correct (e.g. 203dpi)
  - Make sure the document does not need to be scaled (and scaling to fit is disabled) (for 4x6 that means 812 x 1218 pixels max)
  - Make sure the document is black and white (no grayscale)

ZPL is a beast.

Some PDFs embed a single image in them, in which case you can do the following;

  pdfimages -all <input_file>.pdf <out_prefix>
  convert <generated_png>.png -filter point -density 203 -units PixelsPerInch out.png

And then print the generated png.

I have 2x LG Ultrafine 5Ks as well.

I found the USB-C connector wears down over time and causes display and power issues. I've reflowed the connector itself, and am looking at doing a complete connector swap soon. The mechanicals of an active USB-C cable puts stress on the joints and causes them to crack and create unreliable connections. I wish there was a way to lock the connector in and use something else as strain relief.

Unfortunately I've that you can't rely on the chargers being available at most hotels. In my experience they're frequently either ICE-ed (the charging spot is taken by a non-EV car), or there's already another car charging.

I got hit by the same year long gradual bill increase. I didn't notice at first, as the number seemed right, but then at 6 months or so I looked into why the price seemed so much higher than what I remember and got really upset.

When I looked into it, it seemed as though they restructured their plans multiple times during the ~4 years I was paying them, and I got placed into the most expensive option which was originally the same price as what I started with. I was also locked into a year long commitment at some point, and they wouldn't budge on letting me downgrade to the lower plan mid year (I didn't have a use for any of the advanced features).

The support chat told me the same thing about the changes being announced via marketing emails, and said they could not credit, cancel or downgrade my plan. The support agent also couldn't care less when I said it would cause me to cancel my plan at renewal.

The whole experience left me with a really bad impression, I went from a huge advocate to telling everyone to avoid them.

Not really, I mostly cared about AES which was around 25x faster. Here's what a NanoPi M4 does:

  Cryptsetup
  #     Algorithm |       Key |      Encryption |      Decryption
          aes-cbc        128b       465.5 MiB/s       654.0 MiB/s
  
  OpenSSL Speed for ChaCha
  type             16 bytes     64 bytes    256 bytes   1024 bytes   8192 bytes  16384 bytes
  chacha20-poly1305    85242.48k   144024.55k   265936.64k   309418.33k   317977.94k   317658.45k

vs Pi4

  Cryptsetup
  #     Algorithm |       Key |      Encryption |      Decryption
          aes-cbc        128b        18.9 MiB/s        31.9 MiB/s
  
  OpenSSL Speed for ChaCha
  type             16 bytes     64 bytes    256 bytes   1024 bytes   8192 bytes  16384 bytes
  chacha20-poly1305    24833.53k    55555.22k    90574.34k    99022.17k   102659.41k   100592.30k

I'm still surprised that they did not include a crypto accelerator on the Pi4. It seems like a very low cost peripheral, with a high performance impact for many use cases (drive encryption, network encryption, etc...). I ran some benchmarks between a Pi4 and a Nanopi M4 and it wasn't even close.

It's 1 lane, but a 16x connector to allow plugging in any device. PCIe devices can be downgraded into a lower number of lanes. Many motherboard 16x connectors aren't even a full 16x.

From my reading of the interim rules, it's based on your 2019 Schedule C Line 31 (Total Profit and Loss), capped at 100k.

For forgiveness it's: ($100,000 / 52 weeks) * 8 weeks = $15,384. The rules and new clarifications seem to change every week, I'd consult a CPA before assuming anything.