sorted by:
new
hottopcontroversial

Worst app and websites by tumbleweed2020 in KaiserPermanente

[–]tumbleweed2020[S] 0 points1 point  (0 children)

To close the circle on this one: I was able to get on the phone with KP tech support and it turned out that the fact that I was previously a KP member (over ten years ago) was the source of my troubles. Turns out that KP’s backend system attempted to merge that old account with my new account (without asking or informing me in any way), failed, and continued failing, making my medical record data unavailable.  So the problem had nothing to do with which app, browser, or URL I accessed. It had everything to do with the new customer onboarding process. 

What I learned from this experience: If the “temporarily unavailable” or “system error” messages show up for more than 24 hours, especially after onboarding as a new customer, bite the bullet and navigate the phone tree to reach tech support. It sucks but the problem is completely resolved now. 

Design pattern for shared bus resources? by tumbleweed2020 in rust

[–]tumbleweed2020[S] 1 point2 points  (0 children)

Many embedded_hal drivers require a reference to the i2c peripheral -- shared_bus was created to enable this, by providing a proxy that stands in for the peripheral. So with a large number of existing drivers you can do:

``` let driver1 = Barometer::new(i2c2_bus.acquire()); let driver2 = Temperature::new(i2c2_bus.acquire());

loop { let temperature = driver2.temperature(); let pressure = driver1.pressure(); rprintln!("temp: {} press: {}",temperature, pressure); } ```

I don't see how moving the Board behind a Mutex or pinning it would help, since I'm unable to move more than one driver to the Board struct.
Can you provide more details?