actualizacion #7489
Closed
actualizacion #7489
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
merge request
This helps create an area for developing towards the next version.
Allow users to choose whether or not to reveal the provenance of the data to consumers. This is intended to help protect data rights to portability and access. If consumers start abusing or discriminating against Nightscout users due to the source of the data, this allows users to conceal this information.
Disregard brand of device when considering glucose values. By de facto usage, the meaning of LOW and HIGH within Nightscout means that glucose is beyond limits. LOW means 40 or lower. HIGH means 400 or higher. Both tend to invite questioning therapy options, including inspecting if the device is working correctly, as well as potential treatment options.
The results to render may come from an in-memory cache, or from the database. If they came from the in-memory cache, it's possible that obscurring the device field could actually change the values in memory. When obscurring, the device field, this patch copies all of the values in order to ensure that the in-memory copies are unaffected. With this patch, cached objects should not be affected.
With this change, any code referencing the sandbox or /api/v2/properties for plugin will also benefit from having the device information obscured.
…/cgm-remote-monitor into wip/bewest/obscure-provenance
obscure private device provenance
…rdless of units (#7273)
Temporarily use git references to share2nightscout-bridge and minimed-connect-to-nightscout in order to help test similar changes in those packages.
The tests pass cleanly.
Change deduping interval
Run tests also against nodejs 16.x
Omnipod reservoir fixes
Fix expiration time on remote notifications for Loop
Support automatic bolus volumes in the enacted field for loop status.
Results could be null and can crash the website
…emote-monitor into wip/bewest/upgrade-node
This reverts commit ead83e0. Minor differences are causing the tests to fail consistently.
Wip/bewest/upgrade node
npm ls fsevent didn't list any output. I'm running on linux, and regenerating this file after removing it seems to remove the fsevent package from the file. It's likely that fsevent may be used in development mode as part of one of the build utilities, but it shouldn't block anyone from deploying. #7475
The build still fails for node 12.x. Skip optional dependencies. https://stackoverflow.com/a/48953213
Fix incorrect appending for loop enacted status. LGTM.
Remove npm list from engine as it is intended to be advisory.
…ote-monitor into wip/bewest/issue-7475
This makes the testing framework and the advertised node versions match, one for one.
|
Closing extra pull request. These are easily created by mistake sometimes. See the dev branch for current progress. #7237 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
.