I used to work at Epic as a software developer. The experience with MyChart isn’t particularly surprising. I generally think that Epic is pretty genuinely well-intentioned, as companies go, but they’re not particularly incentivized to put more than the bare minimum of effort in this process, since the number of patients who want to opt out is very low, and it’s in Epic’s interest for patients to be signed up (not, I think, for nefarious reasons like selling data; Care Everywhere data is covered by HIPAA and misuse would be a serious legal liability for Epic. But having more patients lets them tout their exchange numbers, etc).

Some of this can also probably be said about the hospital itself. They probably slapped together a process needed to meet legal requirements, but don’t put much effort into it beyond that. It wouldn’t surprise me if they simply didn’t have the resources to spare for it.

Sounds good! And the emergency is that there are too many data centers on the grid.

If one of these bumped into me I feel like I’d want to tip it over in response.

Another option is to disable the warning locally […] But this is compiler-specific and noisy. It also does not explain the real issue to anyone reading the code.

I don’t understand this logic. Surely disabling the warning is directly explaining the actual issue, that the code emits a false positive warning for specific compilers and conditions? That the false_but_compiler_does_not_know_it_ thing is apparently the better way to convey what’s going on seems kind of ridiculous.

They’re really playing up the ominous tone.

“We know this because your IP address — xxx.xxx.xxx.xxx — was the first thing your device sent us. We know the rest of it. We chose not to display it. Most pages would not have made that choice. We did not ask for your location. Your address arrived before you did.”

Uh, yeah. That’s how IP addresses work.

Most of the time the front doesn’t fall off at all! Unless a wave hits it.

That’s got it, thanks!

Ok, I can import the file now, but some entries are getting messed up. This line, for example, shows up in the diary with the amount “NaNg · 722903 kcal”. And as much as I would like to eat Ginger Peanut Chicken until numbers fail to describe my gluttony, I just can’t afford that many calories.

Day,Group,Food Name,Amount,Energy (kcal),Alcohol (g),Caffeine (mg),Oxalate (mg),Phytate (mg),Water (g),B1 (Thiamine) (mg),B2 (Riboflavin) (mg),B3 (Niacin) (mg),B5 (Pantothenic Acid) (mg),B6 (Pyridoxine) (mg),B12 (Cobalamin) (µg),Folate (µg),Vitamin A (µg),Vitamin C (mg),Vitamin D (IU),Vitamin E (mg),Vitamin K (µg),Calcium (mg),Copper (mg),Iron (mg),Magnesium (mg),Manganese (mg),Phosphorus (mg),Potassium (mg),Selenium (µg),Sodium (mg),Zinc (mg),Net Carbs (g),Carbs (g),Fiber (g),Insoluble Fiber (g),Soluble Fiber (g),Starch (g),Sugars (g),Added Sugars (g),Fat (g),Cholesterol (mg),Monounsaturated (g),Polyunsaturated (g),Saturated (g),Trans-Fats (g),Omega-3 (g),ALA (g),DHA (g),EPA (g),Omega-6 (g),AA (g),LA (g),Cystine (g),Histidine (g),Isoleucine (g),Leucine (g),Lysine (g),Methionine (g),Phenylalanine (g),Protein (g),Threonine (g),Tryptophan (g),Tyrosine (g),Valine (g),Category 2026-04-20,"Lunch","Ginger Peanut Chicken","750.00 g",963.87,0.00,0.00,202.97,411.64,438.18,0.54,0.84,24.82,1.63,1.88,1.54,142.39,1074.55,62.64,2.52,4.13,39.04,547.85,0.77,12.70,252.20,1.97,913.92,2259.83,76.25,1861.40,6.73,38.20,55.08,16.50,12.52,1.88,9.13,17.86,7.79,45.73,236.74,16.68,10.61,7.96,0.08,3.19,3.15,0.02,0.01,6.92,0.05,6.82,0.88,1.93,3.15,5.60,5.57,1.68,2.96,85.62,3.14,0.78,2.56,3.38,"Meals, Entrees, and Sidedishes"

Also, there’s a bit of layout weirdness when reimporting days:

I gave this a shot, but when I press the “preview” button I just get a little popup that says “Invalid CSRF token”.

If you’re going to work on CSV import anyway soon, then I’ll just wait. Thanks!

I have exports of my nutrition and weight info from other apps as csv files, and I’d like to import that data if I can. It looks like Nutritrace can export to csv but not import that. There is the option to import from a json backup though. If I can massage my data into that json format, does it seem reasonable to use that as a way to import my historical data?

If the answer isn’t “omg don’t do that”, then I have a couple of questions about the json:

• Does each item in the diary array require a matching foodList/meals/recipes entry? Or could I just generate items in the diary array?
• How much do I need to worry about IDs? The “import JSON” option says that it merges with existing data; how would it handle ID conflicts (which I assume could happen normally when exporting and importing anyway)?
• Are there any gotchas you can think of that I should watch out for?

All I had to do was run the pull command again.

I’m seeing “Could not reach server — retry” on the diary page and when going to enter foods. The diagnostics log has

[14:25:38.821] [ERROR] [diary] loadEntry error: _fetch@http://my.server:3000/assets/index-Dl7TTIk7.js:175:24686

[14:25:41.686] [WARN] [settings] direct push failed for startPage: Server responded 401
[14:25:41.689] [WARN] [settings] direct push failed for weightUnit: Server responded 401
[14:25:41.695] [WARN] [settings] direct push failed for heightUnit: Server responded 401
[14:25:41.699] [WARN] [settings] direct push failed for statsGoalLine: Server responded 401
[14:25:41.701] [WARN] [settings] direct push failed for lengthUnit: Server responded 401
[14:25:41.702] [WARN] [settings] direct push failed for distUnit: Server responded 401
[14:25:41.704] [WARN] [settings] direct push failed for statsYZero: Server responded 401
[14:25:41.705] [WARN] [settings] direct push failed for tempUnit: Server responded 401
[14:25:41.705] [WARN] [settings] direct push failed for usdaEnabled: Server responded 401
[14:25:41.706] [WARN] [settings] direct push failed for statsAvgLine: Server responded 401
[14:25:41.708] [WARN] [settings] direct push failed for offSearchCountry: Server responded 401
[14:25:41.708] [WARN] [settings] direct push failed for offUploadCountry: Server responded 401
[14:25:41.709] [WARN] [settings] direct push failed for offSearchLanguage: Server responded 401
[14:25:41.710] [WARN] [settings] direct push failed for statsTrendLine: Server responded 401
[14:25:41.710] [WARN] [settings] direct push failed for statsChartType: Server responded 401

Looks good, so I’ve got it up and running now. Thanks!

Is the docker image public? I’m getting an “unauthorized” error when attempting to pull it. I’m not getting that error for other ghcr.io images. But I’m not docker expert, so I may be doing something wrong.

Ooh, I’ll definitely give this a try.