Catch up on stories from the past week (and beyond) at the Slashdot story archive


Forgot your password?
Check out the new SourceForge HTML5 internet speed test! No Flash necessary and runs on all devices. ×

Comment Re:Yeah, sure (Score 5, Informative) 104

I know Dana Lewis, so I can probably tell you (the AC, not the reply) more about this system than the article does. There are safeguards around "use all its insulin at once" in the pump controller itself, that the OpenAPS system *cannot* override. The OpenAPS system effectively automates the "pushing the button" actions on the pump that are normally done manually by the patient who is reading his/her glucose meter and doing some fairly complicated math in his/her head to figure out the proper dose. It's an API client, nothing more.

The pump itself has safeguards against overdosing, either via manual control or APS control. And if there's a failure of the OpenAPS system, it simply reverts to manual control, which patients have been doing for years.

Comment Single line of code? (Score 4, Insightful) 618

I *highly* doubt it was a single line of code. To toggle the car's "EPA Cheat" mode, maybe, but by all accounts, the system used a variety of inputs to detect artificial driving conditions (including, apparently, barometer data), as well as needing code to define what engine parameters to change once the mode was entered.

Comment Re:IPv6 would make the problem worse (Score 1) 248

While in practice most admins configure /64s as subnets, there's nothing preventing netblocks that are smaller than /64. I have /127 point-to-point subnets on my network, and /96s going to server racks. You need a /64 in order to do RA, however, but you can use DHCPv6 instead on smaller subnets.

Comment More likely case (Score 1) 125

What's more likely - I've run into exactly this scenario before, in fact - is that the configuration generation system regenerates configs on a regular schedule, and at one point encountered a failure or spurious bug that caused it to push an invalid config. On the next run - right as the SREs started poking around - the generator ran again, the bug wasn't encountered, and it generated and pushed a correct config, clearing the error and allowing apps to recover.

Comment Re:Silly priorities (Score 3, Informative) 274

Disclaimer: Another Twitter engineer here. What my apparently former colleague said, plus X.

Also: Don't be afraid to add caching layers when you see your web server or DBs start to run hot. Putting a memcached instance in place in "front of" your database layer is much easier than sharding the database layers to relieve load - eventually you'll have to do both, but you'll definitely want the memcache layer first. Same with web caches/proxies - putting varnish or squid in front will take some pressure off before you need to implement load balancers.

Slashdot Top Deals

I've looked at the listing, and it's right! -- Joel Halpern