Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Correction Bolus tooltip incorrectly scales BG #5500

Closed
dybs opened this issue Feb 1, 2020 · 3 comments
Closed

Correction Bolus tooltip incorrectly scales BG #5500

dybs opened this issue Feb 1, 2020 · 3 comments

Comments

@dybs
Copy link

dybs commented Feb 1, 2020

Describe the bug
The Correction Bolus tooltip scales a manually-entered BG value by a factor of 18.

To Reproduce
Steps to reproduce the behavior:

  1. Set profile units to mg/dl
  2. Set client settings Units to mg/dL
  3. In Care Portal, create a Correction Bolus treatment and enter a BG value in mg/dL (e.g. 100).
  4. Hover the mouse over the treatment in the graph.
  5. The tooltip shows the BG value multiplied by 18 (e.g. 1800).
  6. NOTE: The Treatement Report shows the entered value, and the treatement dot does appear at the correct position on the graph.

Expected behavior
The treatment tooltip should show the same BG value that was entered.

Screenshots
Profile unit settings - mg/dl:
image

Client unit settings - mg/dL:
image

Tooltip:
image

Treatement report:
image

Your setup information

  • Nightscout 13.0.1
  • CGM is Dexcom G5, data uploaded from xDrip+ on Android.
  • Have tested on Firefox and Chrome on Windows 10, as well as Firefox on Android.

Additional context
I think the issue is lib/client/renderer.js, appendTreatments.treatmentTooltip() function around line 635 when checking the client units vs the profile units. I thought there might be a case-sensitivity issue (my settings are mg/dL, but the profile showed mg/dl), but doing a lowercase-only comparison did not fix it on my fork.

@jakobsandberg
Copy link
Contributor

This issue was reported back in December (#5384) and a fix was already merged in via #5381. However, that fix has not been released yet (it's currently on the dev branch).

It should go out in the next release.

@dybs
Copy link
Author

dybs commented Feb 1, 2020

Ah, thanks, I didn't think to check dev

@pbudzon
Copy link

pbudzon commented May 25, 2020

Can confirm this appeared for me today on latest master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants