This should force the coverage job to return with a success error code.
Codacy changed support for legacy projects. This change should not cause
builds to fail and should not influence ability to merge pull requests. Until
further work with coverage with codacy, this change emits a warning of "NO
COVERAGE" while allowing the build to pass, rather than failing the build.
This patches uses a newer versin of minimed-connect-to-nightscout
that is designed to work under the same version of node as
Nightscout. It should result in Nightscout gaining a capability
to use Medtronic Careportal accounts for cloud to cloud
synchronization.
Many proxies (NGINX included) will generate a list of IPs in v4 and
v6 formats. The forwarded-for library is a well-maintained library for
express that sanitizes, checks, and validates trusted proxy IPs. This helps
eliminate XSS or other attempts to inject invalid material through the
x-forwarded-for header.
Co-authored-by: Sulka Haro <sulka@sulka.net>
This change allows each route to express policies for interpreting and parsing
the request body. Before this change uploads to entries or treatments api
would error if they were larger than 100Kb due to the preference being set for
the whole server. This change removes the global preference in favor of
allowing each route to choose it's own request size limit.
We also refactor usage of body-parser to be more consistent throughout the code
base. Most routes can use jsonParser, rawPraser, and urlencodedParser provided
by the common wares component. Anything doing something else should be called
out as such. For example, treatments, activity, and entries allow uploads up
to 50Mb. Other v1 endpoints are using the common configuration set to 1Mb.
Use npm update --save share2nightscout-bridge to update package-lock.json and
package.json. This should assist in updates intended to help unify Dexcom Account management.
This change moves the ci.test.env file into the tests/ subdirectory in an
effort to reduce the number of files in the project root. The package.json
metadata is updated to enable continuous integration tools to continue to work
as expected.
This change attempts to tidy the project root by moving webpack configuration
into it's own subdirectory. The metadata has been updated to match this information.
In addition, the configuration file itself is simplified for future maintainers
in some ways. Now the configuration to a projectRoot which is calculated
exactly once, instead of introspecting from __dirname each time.
This change moves the azure deployment script from the root of the project into
the bin subdirectory with a name that makes its purpose more clear.
.deployment file has been updated to execute the new path.
setup.sh appears to be a developer utility to assist in bootstrapping a debian
based system. It is intended to help install the dependencies needed to run
node, and not used in any automated deploy pipeline.
Instructions have been updated to suite this change which simply moves the
developer tool out of the project repo and into the bin subdirectory.
This script is used to help prep release branches and tags. Since it's not
crucial to the business of remote monitoring and only useful as a maintenance
tool, we're moving it away from the project root.
This change seeks to continue tidying up the repo.
* The database_configuration.json file is not used and has not been used since
the project was published on github. We remove the ability to look at files
inside the source tree for database credentials.
* Move example-profiles.md to the relevant documentation for plugins area and
update the link to match.
* prepare hotfix for MMConnect/EU - 2020-06-28
Prepare to handle issue #5719. This patch adjusts dependencies to
target a community edition fork of minimed-connect-to-nightscout. The
new dependency targets information provided to begin addressing
changes to Medtronic Carelink services starting late June 2020.
* bump pointing at right tag
* hotfix attempt 2 - carelink 2020 sso updates
* hotfix 3 - attempt 3 at carelink 2020 sso updates
* attempt 4 at hotfix for nightscout
Based on more reliable version of minimed-connect-to-nightscout....
This is testing the hotfix. When it works, we will bump this one more
time with the newly released version.
Co-authored-by: Sulka Haro <sulka@sulka.net>
Based on more reliable version of minimed-connect-to-nightscout....
This is testing the hotfix. When it works, we will bump this one more
time with the newly released version.
Prepare to handle issue #5719. This patch adjusts dependencies to
target a community edition fork of minimed-connect-to-nightscout. The
new dependency targets information provided to begin addressing
changes to Medtronic Carelink services starting late June 2020.
Prepare to handle issue #5719. This patch adjusts dependencies to
target a community edition fork of minimed-connect-to-nightscout. The
new dependency targets information provided to begin addressing
changes to Medtronic Carelink services starting late June 2020.
In a default configuration, there is no treatment data. The code to redirect
the UI to the profile editor is buried deep within the chart rendering code for
basals. This plugin is only supposed to go into action when enabled via
ENABLE=basal. This commit fixes first-use experience for the default
configuration intended to draw real-time CGM traces and no basal information is
expected. Since no basal information is expected unless plugin is enabled via
ENABLE=basal, this allows skipping instead of redirecting to the profile editor.
Provide readENVTruthy, and mapTruthy, to explicitly handle
the cases where on/off or similar should result in a
Boolean value. Here, they should be mapped correctly,
eliminating a problem @miloskozak experienced when setting
AUTH_DEFAULT_ROLES=bad, there is an exception becaue the
value is a literal `true` instead of the string `"bad"`.
Intended to be a no-op, preserving the intended effects
from previous commit
dbe29bd4be from
@jasoncalabrese.
Using all(...) in this manner allows middleware from router A to
not affect router B.
As a result, sendJSONStatus and ability to optionally end in
.json disappeared, which this patch also restores.
CC: @jasoncalabrese
With this change, I can successfully restrict reads to entries
vs status vs other things without the middleware leakage we
observed earlier.
CC @jasoncalabrese, this is debatable, I think this is what you were referring
to, I'd prefer to use the sha1sum (which is fewer bytes) and use that as the id
to lookup/store in mongo instead of this, but not sure.
Ben WestandGitHub
