1,839 karma · joined June 12, 2012
I'll agree and admit that implication is not explicit specification, but I think it's a reasonable example to follow.
When a Content-Length is given in a message where a message-body is allowed, its field value MUST exactly
match the number of OCTETs in the message-body.
According to this, the Content-Length MUST match the data. Can you share an example of the opposite being stated?[1] https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4....
Definitely not what I was expecting...
CloudFlare:
$ ping -c 240 -i 0.25 1.1.1.1
...
--- 1.1.1.1 ping statistics ---
240 packets transmitted, 240 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 16.271/17.286/25.105/1.236 ms
Google Public DNS: $ ping -c 240 -i 0.25 8.8.8.8
...
--- 8.8.8.8 ping statistics ---
240 packets transmitted, 240 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 5.092/10.083/35.949/2.426 ms
OpenDNS: $ ping -c 240 -i 0.25 208.67.222.222
...
--- 208.67.222.222 ping statistics ---
240 packets transmitted, 240 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 8.596/9.847/25.898/1.788 ms
Level 3: $ ping -c 240 -i 0.25 4.2.2.2
...
--- 4.2.2.2 ping statistics ---
240 packets transmitted, 240 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 8.479/9.563/18.971/1.336 ms
Comcast's Resolver: $ ping -c 240 -i 0.25 75.75.75.75
...
--- 75.75.75.75 ping statistics ---
240 packets transmitted, 240 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 8.410/9.717/19.428/1.487 ms
It even looks like OpenDNS and Level 3 are better than Google Public DNS in terms of latency.Well, I'm estimating a percentage in my head and then considering the amount of karma that percentage may have. I'd say 20%, maybe? Of which I personally know a few who have some sizeable karma.
I assume the system calls to interact with the GPU, or to do any sort of I/O, are going to incur the performance overhead. So rendering frames, reading/writing from the network, and loading assets from the disk could all cause issues.
And this is just for gaming. Anyone using a cloud provider that's running on Intel needs to worry about similar things.
What a nightmare...
I'm due to refresh my gaming PC, and I was going to go with Intel again as they've not been a problem. However, if Intel chips are going to incur the same 5% - 50% performance hit on Windows, I might end up investing in AMD hardware instead.
I think the risk here is the assumption that the only devices where you may care about GeoLocation are ones that have this capability. There are cases where using the less precise GeoIP option is not only legitimate, but it's the only option you have. What about IoT or embedded systems where you may not have the capacity to determine the location?
You can't treat the data obtained from GeoIP databases as being absolutely precise. However, for most cases the data will be precise for most people's needs.
I'd be interested in hearing how you handle devices that don't have the APIs you mention.
If it's critical, PagerDuty pings my phone. It starts with the push notification, and escalates to a phone call shortly thereafter.
If it's a low urgency alert, PagerDuty sends me an email. I'll get to it eventually.
All of these trigger Slack webhooks, but those aren't for me to manage the incident or to be alerted. They are there only for visibility purposes.
So yeah, it's a bit inconsistent.
Think CloudFlare CDN or the Google Cloud Load Balancer.
Edit Mistyped RTT as TTL.
Reading the docs, though, it does seem like it's one legendary AWS outage away from being a huge problem:
>Torus’s infrastructure has been designed from the ground up for resilience without any single point of failure. All of our services are autoscaled and run in multiple availability zones in the us-east-1 region.
Seems to be a partial outage.
Mind sharing what information you have which makes you think they were hacked? :)
If so, the hack we've applied for StatefulSets is to delete the StatefulSet with `--cascade=false`. This keeps the Pods of the StatefulSet online, but removes the StatefulSet itself. We can then deploy the StatefulSet with the new configuration vlaues, and manually delete the Pods one-by-one to have the changes be applied.
Graceful: Nope. Needs Improvement: For sure Gets the job done: Yep!
The downside is that it's an experience that admittedly only works if you're using a trackpad, or a mouse with good side-scrolling support. So people with laptops / trackpad mice are probably okay.
>It's not hard to draw the planets.
>It's the empty space that's the problem.
Almost free because you shouldn't forget to tip the driver you're stealing the pizza from!
It was actually the straw that broke the camel's back for me as an Arch user. This was around the time Arch Linux was going through lots of breaking changes.
> I don’t particularly care about the argument between plain text versus binary logs. However, if your reasoning for not wanting to use binary logs is because they are opaque and can be corrupted then you should take a close look at your log rotation or archival process. If you are archiving logs by first compressing them using something like gzip, you no longer have plain text log files.
I found quite a few people disliked binary log files due to concerns around their portability. Specifically when they depend on a platform-specific utility to read them. If they are compressed using a standard algorithm, it alleviates concerns about portability.