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:
I just want to thank you for providing this info. This was exactly the cause of some of our issues and this config setting restored functionality to a major part of our app.
Happy it helped. If you have a very high throughput app (or something that logs gigantic payloads), the "logging pauses" may slow down your app in non-obvious ways. Diagnosing it the very first time took forever (I think I straced the process in the docker container and saw it was hanging on `write(1)`)
USB has a built in protocol level reset that should achieve the same thing. The only change is 5V power is not cut. It's basically the same as doing an OS reboot from the peripheral's perspective.
If the USB device still doesn't respond then it means that they have some buggy firmware that requires a hard reboot to work.
You need to cut the power for certain USB devices to actually reset their in-device memory though (like an iLok dongle). Just "disconnecting and reconnecting" via software without a power cycle won't do anything for those. And that's not a bug, in dongles that's literally an anti-piracy feature.
I've tried that, my RealSense camera and several other USB devices I've used require physically unplugging and plugging after every reboot or it refuses to work.
I've got experience with this... `reboot` won't work, as it doesn't cut power, but if you can do `rtcwake -m off -s 30`, the power to the USB ports gets cut in between the computer being off and booting back up again.
(I even replace `reboot` with a script warning of this gotcha :) )
Caveat: this is with a typical x86 motherboard. Not all SBCs have RTCs needed to use rtcwake (e.g. RPi doesn't I think?)
Some devices (mostly security devices) trigger things based on the physical connection state, cycle count, etc. and it's useful to have a means to test these.
I've never seen a device so far that has a physical switch to make sure it's really been unplugged, but I'd imagine someone could find a use case.
That doesn't solve the problem that I still need to do it though. I've got this problem right now with my Blue microphone: it hates being rebooted without being power-cycled for some reason.
Just wait until they find your wife's phone number. (OK, this wasn't datadog, but some similarly aggressive headhunting agency went from calling me to calling my wife - who is in no way affiliated with my company - to ask her if she could tell me about how they could help me in hiring, yadda yadda.)
I had something similar happen with a Facebook recruiter. I didn't reply to her first two emails so she started emailing my mom to try to get in touch with me. My mom called me because she thought it was a phishing email. I had never had that happen before.
I have started invoicing companies for wasting my time and also threatening them with CAN-SPAM complaints for failing to include an opt-out, an actual mailing address, etc.
Then, when my invoice isn’t paid, I threaten collections on them personally and the company. Usually that solves it. Then I’m “such a dick” but highly effective in recovering my time.
Back in the days when this kind of thing happened on the telephone, the SERIOUSLY passive aggressive trick was to talk to them, and then hang up on yourself. Repeatedly.
"Hi this is Arnie from CHewemup'n'Spitemout Staffing, is this Bob?"
"Hey Arnie, what perfect timing! I just started looking for a new opportunity, and I'm really excited to— CLICK."
Ring ring.
"This is Arnie, we seem to have been cut off."
"Oh Arnie, right, thought you hung up on me."
"No, not me, must be a bad connection. You were saying?"
"Yes, I was saying this is a great time to talk about opportunities. I just finished a major Java Enterprise JavaBeans project, and I'm— CLICK."
Lather, rinse, repeat, as the meme used to go before we called them memes.
oh man, that's great-- you could probably get through a LOTT more CLICKs before they get the point. what a great use of human psychology-- they assume you have good intentions because you called them... it's a bit devious, but i'm gonna have to add that one to the toolbox hahaha.
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;
Car and Driver did a test using an older Model 3 with a resistive heater (the newer models use a much more efficient heat pump), and found that it used around 2.2% an hour to keep the cabin warm.
In your example with 15% left, you'll use ~9% battery while in traffic for 4 hours keeping the heat and car on, leaving 6% to get to the next charger. At ~300wh/mile you'll arrive with ~4-5% left. There's also buffer under 0%, but it's not guaranteed.
4-5% is not a comfortable number to be at, but I think it's acceptable in a worst case scenario like this. That being said I would definitely turn down the heat, and drive slower for the next few miles (and check for alternate chargers) to minimize power usage.
I really wonder how a heat pump can achieve so much efficiency gain. Heat of electric resistance is about 99% energy efficient: almost all energy is converted into heat, nothing else.
A resistive heater directly converts electricity to heat, whereas a heat pump instead moves heat, from the outside to inside of your car. The heat your car gains is reflected by the heat the outside loses. In that way, they can be 300-400% “efficient”, because we do not care about the outside air around the car getting a little bit colder.
It just goes back to the battery to complete the circuit. Heat is created by resistance and if the energy going through the heater isn’t being resisted enough, there is no heat, just wasted energy. Most of these heaters regulate temperature by turning off/on/off and it’s the coming up to full resistance that is when the energy is “wasted” and doing it at human temperatures is a lot of off/on cycles. Also, it’s worth pointing out that not 100% of the energy is converted to heat, or you’d have a gigaton bomb instead of a heater.
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.
I have an LG Ultrafine 5K and suffer from random display disconnections. I was wondering if I was just unlucky, but this kind of explains everything now. Is there any guide that you know of for doing the reflowing? It's at the point now where I need to spend up to an hour carefully tweaking the connector into the right position to provide a signal so I don't mind hacking away at it with the risk of it breaking.
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.
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: