Update before moving data to mLab #2

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.

master

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.

rm package-lock.json && npm install

Allow Remote Carb Entries in Past or Future

…already merged his branch to dev add NodeJS 16.x support. drop NodeJS 12.x support.It reached End-of-Life status on 30 April 2022 allow NodeJS 18.x support to run for CI upgrade webpack and webpack-cli update browserlist and browser documentation, config is now at .browserslistrc update README.md for browsers and Node versions fix typos in comments in lib/client/hashauth.js and webpack/webpack.config from #7440

…k.json with node v10.24.1

…verage pacakge (see issue #7515 ).

…ll...

…odules, so the content is retained across cached builds in various PAAS environments

* Change | to && in package.json

…ript

* Build docker image for arm64 architecture * Add `platforms` input * Merge `master` and `dev` jobs together into one * Run job on master or dev branch

Release 14.2.6

… into PieterGit-dev20220815

The '^' prefix makes this meaingless, there's no reason to refuse to run less than 16.16.0 if it's still some 16.x.

…0815 Wip/bewest/pieter git dev20220815

New build artefact cache location

Avoid HTML injection called out by CODEQL.

See if this makes codeql happy.

Wip/bewest/code ql analysis

codeql text/html injection in food.js

Fix empty import config

Remove unused OTP field from Remote Override form.

…oke as a result

Co-authored-by: Ben West <[email protected]>

* New translations en.json (Hungarian) * New translations en.json (Turkish) * New translations en.json (Hungarian) * New translations en.json (Turkish) * New translations en.json (Turkish) * New translations en.json (Arabic) * New translations en.json (Turkish) * New translations en.json (Slovak) * New translations en.json (Turkish) * New translations en.json (Turkish) * New translations en.json (Turkish) * New translations en.json (Turkish) * New translations en.json (Turkish) * New translations en.json (Turkish) * New translations en.json (Turkish) * New translations en.json (Turkish) * New translations en.json (Turkish) * New translations en.json (Hungarian) * New translations en.json (Turkish) * New translations en.json (Turkish) * New translations en.json (Estonian) * New translations en.json (Estonian) * New translations en.json (Estonian) * New translations en.json (Norwegian Bokmal) * New translations en.json (Portuguese, Brazilian) * New translations en.json (Italian) * New translations en.json (Italian) * New translations en.json (Portuguese, Brazilian) * New translations en.json (Portuguese, Brazilian) * New translations en.json (Portuguese, Brazilian) * New translations en.json (Portuguese, Brazilian) * New translations en.json (Ukrainian) * New translations en.json (Ukrainian) * New translations en.json (Ukrainian) * New translations en.json (Ukrainian) * New translations en.json (German) * New translations en.json (Spanish) * New translations en.json (Turkish) * New translations en.json (Turkish) * New translations en.json (Turkish) * New translations en.json (Estonian) * New translations en.json (Estonian)

Bumps [jsonwebtoken](https://github.com/auth0/node-jsonwebtoken) from 8.5.1 to 9.0.0. - [Release notes](https://github.com/auth0/node-jsonwebtoken/releases) - [Changelog](https://github.com/auth0/node-jsonwebtoken/blob/master/CHANGELOG.md) - [Commits](auth0/node-jsonwebtoken@v8.5.1...v9.0.0) --- updated-dependencies: - dependency-name: jsonwebtoken dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* This commit updates the uuid and socket.io packages to latest versions and enables compression over websocket * Drop the compression threshold down to 512 bytes * Enable http compression down to 512 bytes and request long poll transport only, as per current release * Add the socket.io-client back in * Use polling with the NS client * Update express to latest in 4.x line, fix tests

* check if d1 is not nil before call getTime Co-authored-by: Sulka Haro <[email protected]>

* Use 'forwarded' always Getting the remote IP from the socket doesn't work behind a reverse proxy. 'Forwarded' is there to fix there, but wasn't used here. * Consistently use getRemoteIP() throughout Stay in line with other modules that do this * Use getRemoteIP consistently One more missing case; in this file it isn't helpful, but it is consistent with other files. Co-authored-by: Sulka Haro <[email protected]>

* Experimental branch that replaces momentjs with dayjs in the client * Revert unintentional change * feat * Turns out dayjs is a no-go, but this has some good restructuring so submitting that

…ast two years

…cloud providers

* Fixes a bug introduced in #7273 * Oops somehow managed to commit a wrong file version * Cleaner code based on feedback from Ben

* Allow DELETE via PATCH/UPDATE operation too * rollback wrong commit Co-authored-by: Milos Kozak <[email protected]>

Co-authored-by: Sulka Haro <[email protected]>

) * Delete v3 api identifiers when cloning a record * Refactored to use lodash omit * Move cleaning logic to correct function, add _id to list of cleaned properties * Add back a line that was accidentally deleted * profileeditor: add created_at, srvModified too on save to simulate API v3 Co-authored-by: Milos Kozak <[email protected]>

* rollback compatibility issues for tests Revert "Bump jsonwebtoken from 8.5.1 to 9.0.0 (#7787)" This rolls back changes to node_modules via package-lock.json as a result of new dependencies. More work is needed before involving these changes. Without this rollback, the tests do consistently complete within the allowed time in a reproducible way. * Test Github Actions with jsdom 11.11.0 * Upgrade github actions as requested by the actions runner * Lock generated using 6.14.18 * Upgrade actions/checkout@v2 to v3 * restore jsonwebtoken upgrade Co-authored-by: Ben West <[email protected]>

* Change runtime cache to support item timestamp be defined in either mills or date field. * Fix typo * Return mills in v1 api when returning data from cache * Also parse created_at in the cache * Fix copy paste error

Midnight for the profile should always be at the start of the day (midnight) for the chart.

This more closely mirrors logic in loopalyzer, as well as the intent from the surrounding code in reportclient.js.

This fixes the label on the days in the daytoday charts. Passing a moment object that is already zoned prevents toLocaleDateString from reinterpreting the zone information when the date is already relative to the profile. This also ensures that the datefilter is adjusted to the profile's zone rather than truncating the time to the end or beginning of the day. This should prevent incorrectly wrapping arounnd the dateline.

To illustrate the difference, I used chrome "sensors" feature to change my timezone to one that spans the dateline. > moment.tz('2023-01-19', 'America/Los_Angeles').endOf('day').format( ) '2023-01-19T23:59:59-08:00' > moment.tz(moment('2023-01-19'), 'America/Los_Angeles').endOf('day').format( ) '2023-01-18T23:59:59-08:00' The old code uses a string replacement, which is equivalent to the first test. This causes the dates on the reports to be off by one, as well as risks the data wrapping around the dateline so it can't be seen. For example, replacing "23:59:59" with "00:00:00" in the first example doesn't correctly wrap around the dateline. The patch introduces a way to parse the dates requested in the browser's time zone, and then translates them to the profile's timezone. The difference is shown in the second example above. With this change, the correct date label should be rendered, and the data should start at midnight without wrapping around the dateline.

Ensure that the test fixtures will return; the previous changes correctly forward the time to end of day across zones and datelines. One side effect is that the date formatted for the end of the day uses all the microseconds for the day as well. This changes the query from the form of 23:59:59.000Z to 23:59:59.999Z. This also ensures that anything that happens during that one second will be included rather than excluded.

…nd reports (#7833) * * Change profile editor so it works when client uploads profiles where string case doesn't match editor expectations * Re-enable culling down time zone data sent to client * Add a workaround to fix Loop uploading non-ISO compliant time zone identifier

* New translations en.json (German) * New translations en.json (Russian)

…gm-remote-monitor into wip/bewest/daytoday-redo-03

This reverts commit f51fac9.

This reverts commit a4f9271.

This change correctly aligns the name of the day in the current zone with the start of the data for the equivalent day in the profile's zone. This makes it so that viewing a day to day report in any timezone works going both east and west directions.

* Update Mongo URL parser to 1.0.2 to fix issues Scott H found * Reset the lockfile * Update lock to include new component

* minimum attempt to protect /api/v2/ endpoints These endpoints should be protected as reported in #7546. * remove spurious line Co-authored-by: Sulka Haro <[email protected]>

…gm-remote-monitor into wip/bewest/daytoday-redo-03

Wip/bewest/daytoday redo 03

…7884) Parameters defined in x-logging extension field with options: max-size: '10m' max-file: '5'

Co-authored-by: Sulka Haro <[email protected]>

…by AAPSClientV3. (#7873) Co-authored-by: Sulka Haro <[email protected]>

* Fix an issue reported by Milos, when a JWT is loaded with a subject that has no permissions * Add unit test to cover this case

* Alarm sockets for api v3 * Migrate to alarm websockets * Fix unit tests --------- Co-authored-by: Sulka Haro <[email protected]>

* APIv3: removing authorization by accessToken from codebase and adjusting tests * APIv3: updating docs --------- Co-authored-by: Petr Ondrůšek <[email protected]> Co-authored-by: Sulka Haro <[email protected]>

There is a bug generating the window for time ranges across different timezones, which results in different queries wrapping around day boundaries. This provides the fixture with three variants of the queries, in some ways better documenting the bug, and allowing the tests to pass.

cheat for tests across different time zones

…rrect order * Fix a bug in CGM entry insertion, where entries that were inserted without a dateString but with a numeric date were always using the current time

Fixes #7910 LGTM, tests work, merging.

) * Allow DELETE via PATCH/UPDATE operation too * rollback wrong commit * Ensure indexes for Roles and Subjects collections as part of boot --------- Co-authored-by: Milos Kozak <[email protected]>

* New translations en.json (French) * New translations en.json (Bulgarian) * New translations en.json (Bulgarian)

This allows consumers, such as nightscout-connect to receive a new sbx without creating a new one.

Wip/bewest/document data rights

…ded event to process local data updates even if the call is debounced

…/cgm-remote-monitor into wip/bewest/nightscout-connect

* Removes old openaps-storage feature

https://github.com/nodejs/release#release-schedule

…quest for use in watchfaces and other display-only applications * Cleans V2 API implementation * Removes unnecessary server init calls in API calls that were unnecessary * Expose latest SBX state through the CTX object

* Preprocess temp basals and profile to create a temp basal dataset * Cleaner profile output * Support hours GET parameter (up to 48 hours)

Further minize returned data

With this patch, the new version of nightscout-connect will support all the features of share2nightscout-bridge, minimed-connect-to-nightscout, and more.

…/nightscout-connect

Introduce nightscout-connect in the README. Issue warnings in the logs when the older plugins are used.

support for nightscout-connect + easystate summary API v2

…/cgm-remote-monitor into wip/bewest/nightscout-connect

Wip/bewest/nightscout connect

Set interruption level

New Crowdin updates

…grade Upgrade APN Library & Support Time-Sensitive Notifications

This provides better support for several vendors, notably Medtronic and Glooko.

This patch allows the operator to control whether or not the API Secret authentication dialog will display by default or not. Historically Nightscout allows a configuration to be readable and to send alarm information to all displays. A change in in dev in February to support authentication and api v3 introduced a new configuration where websocket communication is authenticated, and the API Secret modal will display if it authenticates in error. The side-effect is that all new instances, even readable instances with glucose data, can't be seen or monitored without putting in the API Secreet or explicitly dismissing it. This patch returns to the default behavior while allowing to select the new one using authenticationPromptOnLoad in the settings communicated from server to client. If people strongly prefer, we can reverse to the new behavior over time. To select the old behavior with no API Secret needed for readabable data, do nothing. To select the new behavior where the API Secret prompts occur on load, set `AUTHENTICATION_PROMPT_ON_LOAD=1`.

…eads Wip/bewest/api secret free reads

Please see nightscout/nightscout-connect#18 for the proposed code change.

APIv3 sync only on srvModified

README.md: use shareous1 for Nightscout connect using Dexcom share

Point readme to correct location of swagger.yaml

Given node 18 and 20, allow running on any LTS version of node. We can block out bad versions if needed.

Use npm install under node 14 generates different lock file.

This patch adjusts the user feedback while the server is initializing to communicate that Nightscout startup sequence should take closer to 15 second than 5 seconds.

…ates

Record output of npm instlal using oldest supported version.

Record changes from upgrading nightscout-connect to at least the latest release, 0.0.12.

Mongo driver update & less frequent database polls

New Crowdin updates

dev - candidate for release 15.0.0

…ates" This reverts commit 2757fe5, reversing changes made to 4a461e5.

Revert "Merge pull request #8026 from nightscout/less_frequent_db_upd…

Releasing 15.0.1, hotfix to revert series of changes affecting mongodb that were not quite ready.

The allowEIO3, when set to true allows v2 clients to connect while the default is false. This patch should allow versions of AndroidAPS older than 3.2 to connect to NS15 and above. Thanks to Dave Carlson for researching and experimenting with this option! https://socket.io/docs/v4/migrating-from-2-x-to-3-0/#how-to-upgrade-an-existing-production-deployment https://socket.io/docs/v4/server-options/#alloweio3

@thecubic

This patch removes my own patch to enable allowEIO3 in favor of @thecubic's patch. They both do the same thing, but @thecubic's is tested.

socket.io: enable legacy v2 connections

This patch is intended to allow customizing the behavior for whether or not to prompt for authorization before subscribing or acknolweding alarms. There was a bug in previous attempts where the profileeditor would be double initialized, causing the profileeditor to remove some buttons from the GUI. This patch adds checking for a permission specifically related to acknolwedging alarms, as well as avoids double-initializing the editor, which causes the issue with the GUI.

This patch eliminates debugging logging in favor of commentary to capture how, where, and why alarmSocket feature is causing different pages to demand the authentication prompt in a variety of circumstances.

Create an opportunity to respond with something other than a global ack when someone that is not authorized sends an acknolwedgement to an alarm. Eliminate double-initializing when subscribing to alarms. The `callback` variable is not local to the function, anyway.

When someone is looking at Nightscout and needs the alarm silenced, it is very desirable to always silence the local UI. This patch documents some of the working code around handling the alarm notification process, as well as provides commentary on handling unauthorized scenarios. There are some open questions such as how to update the permission set after authorization.

alarmSocket: customizing authorization requirements

Dev branch for next release, 15.0.2

Commits on Dec 11, 2021

Add Arabic as an option to translations

sulkaharo committed Dec 11, 2021

Configuration menu

View commit details

Copy full SHA for c09616c

Browse repository at this point

Copy the full SHA

c09616c View commit details

Browse the repository at this point in the history

Commits on Jan 7, 2022

Change deduping interval

MilosKozak authored Jan 7, 2022

Configuration menu

View commit details

Copy full SHA for 4625050

Browse repository at this point

Copy the full SHA

4625050 View commit details

Browse the repository at this point in the history

Commits on Mar 21, 2022

Remove debug print

ps2 committed Mar 21, 2022

Configuration menu

View commit details

Copy full SHA for 6f02d51

Browse repository at this point

Copy the full SHA

6f02d51 View commit details

Browse the repository at this point in the history

Commits on Dec 31, 2022

Update codeql-analysis.yml

sulkaharo authored Dec 31, 2022

Configuration menu

View commit details

Copy full SHA for 05bbc55

Browse repository at this point

Copy the full SHA

05bbc55 View commit details

Browse the repository at this point in the history

Commits on Apr 7, 2023

experimental support for nightscout-connect

bewest committed Apr 7, 2023

Configuration menu

View commit details

Copy full SHA for 25672ea

Browse repository at this point

Copy the full SHA

25672ea View commit details

Browse the repository at this point in the history

Commits on May 9, 2023

temporary nightscout-connect by url

bewest committed May 9, 2023

Configuration menu

View commit details

Copy full SHA for 728b7be

Browse repository at this point

Copy the full SHA

728b7be View commit details

Browse the repository at this point in the history

Commits on Jun 13, 2023

use latest version of nightscout-connect

bewest committed Jun 13, 2023

Configuration menu

View commit details

Copy full SHA for e7e04fc

Browse repository at this point

Copy the full SHA

e7e04fc View commit details

Browse the repository at this point in the history

Commits on Jun 28, 2023

Fix null values in the summary API

sulkaharo committed Jun 28, 2023

Configuration menu

View commit details

Copy full SHA for e99a166

Browse repository at this point

Copy the full SHA

e99a166 View commit details

Browse the repository at this point in the history

Commits on Aug 21, 2023

New translations en.json (Greek)

sulkaharo committed Aug 21, 2023

Configuration menu

View commit details

Copy full SHA for b4ab7ce

Browse repository at this point

Copy the full SHA

b4ab7ce View commit details

Browse the repository at this point in the history

Commits on Aug 25, 2023

npm install nightscout-connect@^0.0.11

bewest committed Aug 25, 2023

Configuration menu

View commit details

Copy full SHA for 79df562

Browse repository at this point

Copy the full SHA

79df562 View commit details

Browse the repository at this point in the history

Update before moving data to mLab #2

Are you sure you want to change the base?

Update before moving data to mLab #2

Commits on Dec 10, 2021

Commits on Dec 11, 2021

Commits on Dec 14, 2021

Commits on Dec 15, 2021

Commits on Jan 5, 2022

Commits on Jan 7, 2022

Commits on Jan 28, 2022

Commits on Feb 16, 2022

Commits on Feb 20, 2022

Commits on Mar 2, 2022

Commits on Mar 15, 2022

Commits on Mar 18, 2022

Commits on Mar 19, 2022

Commits on Mar 21, 2022

Commits on Mar 28, 2022

Commits on Apr 19, 2022

Commits on Apr 20, 2022

Commits on Apr 21, 2022

Commits on Apr 30, 2022

Commits on Jun 27, 2022

Commits on Jun 29, 2022

Commits on Jun 30, 2022

Commits on Jul 18, 2022

Commits on Aug 8, 2022

Commits on Aug 14, 2022

Commits on Aug 15, 2022

Commits on Aug 16, 2022

Commits on Aug 28, 2022

Commits on Aug 29, 2022

Commits on Aug 30, 2022

Commits on Sep 13, 2022

Commits on Sep 30, 2022

Commits on Oct 1, 2022

Commits on Oct 29, 2022

Commits on Nov 1, 2022

Commits on Nov 16, 2022

Commits on Dec 30, 2022

Commits on Dec 31, 2022

Commits on Jan 1, 2023

Commits on Jan 5, 2023

Commits on Jan 6, 2023

Commits on Jan 9, 2023

Commits on Jan 12, 2023

Commits on Jan 13, 2023

Commits on Jan 15, 2023

Commits on Jan 17, 2023

Commits on Jan 23, 2023

Commits on Jan 24, 2023

Commits on Jan 26, 2023

Commits on Jan 27, 2023

Commits on Jan 28, 2023

Commits on Feb 9, 2023

Commits on Feb 13, 2023

Commits on Feb 18, 2023

Commits on Feb 21, 2023

Commits on Feb 25, 2023

Commits on Feb 26, 2023

Commits on Mar 29, 2023

Commits on Apr 7, 2023

Commits on Apr 8, 2023

Commits on May 2, 2023

Commits on May 9, 2023

Commits on May 29, 2023

Commits on May 31, 2023

Commits on Jun 1, 2023

Commits on Jun 2, 2023

Commits on Jun 4, 2023

Commits on Jun 6, 2023

Commits on Jun 7, 2023

Commits on Jun 9, 2023

Commits on Jun 10, 2023

Commits on Jun 13, 2023

Commits on Jun 14, 2023

Commits on Jun 17, 2023

Commits on Jun 19, 2023

Commits on Jun 21, 2023

Commits on Jun 28, 2023