search

burnedikt / diasend-nightscout-bridge

Synchronize your diasend data to nightscout.
MIT License
18 stars 18 forks source link

Heroku build fails after merging with nightscout with OS expected darwin Vs actual linux #17

Closed muthijammy closed 1 year ago

muthijammy commented 2 years ago

Not a techie just merged ur changes to my nightscout branch. Got below OS incompatability. Can u help how ot can be fix it?

-----> Building on the Heroku-22 stack-----> Using buildpack: heroku/nodejs-----> Node.js app detected -----> Creating runtime environment NPM_CONFIG_LOGLEVEL=error NODE_VERBOSE=false NODE_ENV=production NODE_MODULES_CACHE=true -----> Installing binaries engines.node (package.json): ^16.x || ^14.x || ^12.x engines.npm (package.json): unspecified (use default) Resolving node version ^16.x || ^14.x || ^12.x... Downloading and installing node 16.18.1... Using default npm version: 8.19.2 -----> Restoring cache - npm cache -----> Installing dependencies Installing node modules npm ERR! code EBADPLATFORM npm ERR! notsup Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin"} (current: {"os":"linux","arch":"x64"}) npm ERR! notsup Valid OS: darwin npm ERR! notsup Valid Arch: undefined npm ERR! notsup Actual OS: linux npm ERR! notsup Actual Arch: x64 npm ERR! A complete log of this run can be found in: npm ERR! /tmp/npmcache.cZ2Co/_logs/2022-11-29T00_38_53_379Z-debug-0.log-----> Build failed We're sorry this build is failing! You can troubleshoot common issues here: https://devcenter.heroku.com/articles/troubleshooting-node-deploys If you're stuck, please submit a ticket so we can help: https://help.heroku.com/ Love, Heroku ! Push rejected, failed to compile Node.js app. ! Push failed

burnedikt commented 2 years ago

Sorry to hear that. From the logs I understand that heroku fails to install a dependency (fsevents) as it's only supported on darwin, i.e. macOS and not on a linux host (as is the case for heroku). Interestingly enough, that dependency is not from my nightscout branch (but already included with vanilla nightscout). Only difference I can see is that the vanilla nightscout repository still uses npm lockfile version 1, whereas my fork now uses version 2. Maybe npm handles the optional dependencies there differently. But even then, it still odds me out that heroku would handle this differently than railway.

The weird part is that I don't get those issues and I'm also running nightscout on a linux host (no longer on heroku since the free tier was removed but now on railway.app. But technically, there shouldn't be much difference).

I'll check if I can reproduce this build error somehow (on node 16.18.1 as used by heroku).

burnedikt commented 1 year ago

Sorry for not being able to look at this earlier. I was able to reproduce the issue (only on heroku, though).

-----> Building on the Heroku-22 stack
-----> Determining which buildpack to use for this app
-----> Node.js app detected

-----> Creating runtime environment

       NPM_CONFIG_LOGLEVEL=error
       NODE_VERBOSE=false
       NODE_ENV=production
       NODE_MODULES_CACHE=true

-----> Installing binaries
       engines.node (package.json):  ^16.x || ^14.x || ^12.x
       engines.npm (package.json):   unspecified (use default)

       Resolving node version ^16.x || ^14.x || ^12.x...
       Downloading and installing node 16.18.1...
       Using default npm version: 8.19.2

-----> Installing dependencies
       Installing node modules
       npm ERR! code EBADPLATFORM
       npm ERR! notsup Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin"} (current: {"os":"linux","arch":"x64"})
       npm ERR! notsup Valid OS:    darwin
       npm ERR! notsup Valid Arch:  undefined
       npm ERR! notsup Actual OS:   linux
       npm ERR! notsup Actual Arch: x64

       npm ERR! A complete log of this run can be found in:
       npm ERR!     /tmp/npmcache.W79c6/_logs/2022-12-02T23_19_18_637Z-debug-0.log
-----> Build failed

       We're sorry this build is failing! You can troubleshoot common issues here:
       https://devcenter.heroku.com/articles/troubleshooting-node-deploys

       If you're stuck, please submit a ticket so we can help:
       https://help.heroku.com/

       Love,
       Heroku

 !     Push rejected, failed to compile Node.js app.
 !     Push failed

I've pushed a fix which downgrades the npm lockfile version again, marking optional dependencies as optional again instead of extraneous. This seems to have done the trick, with the most recent commit, the build works on heroku again. Can you confirm?

muthijammy commented 1 year ago

Hi @burnedikt Thanks for even looking into this. Sorry for responding late on this. I have moved to google cloud now. So, cant test on heroku & waiting for guidance on how I can do this. I dont want to trouble railway if I can. Reason I needed diasend is camaps. Note, after merge, one of CI tests did fail on github. Hope not an issue. Will keep u posted.

Screenshot_20221206-090445_Chrome Screenshot_20221206-090410_Chrome

burnedikt commented 1 year ago

I've also encountered the failing github actions but they're "just" out-of-memory exceptions, i.e. the system is working as intended, it's just consuming more resources during testing than what the default allows for. This is addressed by https://github.com/burnedikt/cgm-remote-monitor/commit/40210e252205e3279a2664c5a1b21598559d0381.

Unsure why it doesn't happen with the original nightscout, though.

It's worth noting for anyone reading this that the (build) issues described in this thread are actually not related to this project (diasend-nightscout-bridge) but to the fork of nightscout embedding the diasend-nightscout-bridge within nightscout.

muthijammy commented 1 year ago

Thanks for the fix. It worked and I was able to deploy ur code merged into my ns on google site and site is up. I added diasend to ENABLE and added diasend username/password heroku variables & rebooted. Though diasend works, ns doesnt contain. I trying to access logs but can u confirm below?

  1. Any chance below instruction can be detailed? I downloaded source code of plugin

"you can simply install the bridge as an npm package within your nightscout installation"

muthijammy commented 1 year ago

I managed to download tar.gz, upload to vm, tar extract and run npm install. I got lot of below errors. Any idea whats next?

user@instance-1:~ /diasend-nightscout-bridge-0.7.8$ ls @custom-types LICENSE Looper.ts tests adapter.ts config.ts diasend-api.http diasend.ts index.ts jest.config.ts nightscout.ts package.json readme.md run.ts tsconfig.json yarn.lock user@instance-1:~ /diasend-nightscout-bridge-0.7.8$ npm install

diasend-nightscout-bridge@0.1.2 prepare /home/user/diasend-nightscout-bridge-0.7.8 npm run build

diasend-nightscout-bridge@0.1.2 build /home/user/diasend-nightscout-bridge-0.7.8 tsc

npm notice created a lockfile as package-lock.json. You should commit this file. npm WARN notsup Unsupported engine for axios-cookiejar-support@2.0.5: wanted: {"node":">=12.19.0 <13.0.0 || >=14.5.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: axios-cookiejar-support@2.0.5 npm WARN notsup Unsupported engine for http-cookie-agent@1.0.6: wanted: {"node":">=12.19.0 <13.0.0 || >=14.5.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: http-cookie-agent@1.0.6 npm WARN notsup Unsupported engine for @typescript-eslint/eslint-plugin@5.46.1: wanted: {"node":"^12.22.0 || ^14.17.0 || >=16.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: @typescript-eslint/eslint-plugin@5.46.1 npm WARN notsup Unsupported engine for @typescript-eslint/parser@5.46.1: wanted: {"node":"^12.22.0 || ^14.17.0 || >=16.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: @typescript-eslint/parser@5.46.1 npm WARN notsup Unsupported engine for eslint@8.29.0: wanted: {"node":"^12.22.0 || ^14.17.0 || >=16.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: eslint@8.29.0 npm WARN notsup Unsupported engine for eslint-plugin-unused-imports@2.0.0: wanted: {"node":"^12.22.0 || ^14.17.0 || >=16.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: eslint-plugin-unused-imports@2.0.0 npm WARN notsup Unsupported engine for jest@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: jest@28.1.3 npm WARN notsup Unsupported engine for ts-jest@28.0.8: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: ts-jest@28.0.8 npm WARN notsup Unsupported engine for expect@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: expect@28.1.3 npm WARN notsup Unsupported engine for pretty-format@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: pretty-format@28.1.3 npm WARN notsup Unsupported engine for @jest/expect-utils@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: @jest/expect-utils@28.1.3 npm WARN notsup Unsupported engine for jest-get-type@28.0.2: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: jest-get-type@28.0.2 npm WARN notsup Unsupported engine for jest-matcher-utils@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: jest-matcher-utils@28.1.3 npm WARN notsup Unsupported engine for jest-message-util@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: jest-message-util@28.1.3 npm WARN notsup Unsupported engine for jest-util@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: jest-util@28.1.3 npm WARN notsup Unsupported engine for jest-diff@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: jest-diff@28.1.3 npm WARN notsup Unsupported engine for diff-sequences@28.1.1: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: diff-sequences@28.1.1 npm WARN notsup Unsupported engine for @jest/schemas@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: @jest/schemas@28.1.3 npm WARN notsup Unsupported engine for @jest/types@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: @jest/types@28.1.3 npm WARN notsup Unsupported engine for @typescript-eslint/scope-manager@5.46.1: wanted: {"node":"^12.22.0 || ^14.17.0 || >=16.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: @typescript-eslint/scope-manager@5.46.1 npm WARN notsup Unsupported engine for @typescript-eslint/type-utils@5.46.1: wanted: {"node":"^12.22.0 || ^14.17.0 || >=16.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: @typescript-eslint/type-utils@5.46.1 npm WARN notsup Unsupported engine for @typescript-eslint/utils@5.46.1: wanted: {"node":"^12.22.0 || ^14.17.0 || >=16.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: @typescript-eslint/utils@5.46.1 npm WARN notsup Unsupported engine for @typescript-eslint/types@5.46.1: wanted: {"node":"^12.22.0 || ^14.17.0 || >=16.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: @typescript-eslint/types@5.46.1 npm WARN notsup Unsupported engine for @typescript-eslint/visitor-keys@5.46.1: wanted: {"node":"^12.22.0 || ^14.17.0 || >=16.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: @typescript-eslint/visitor-keys@5.46.1 npm WARN notsup Unsupported engine for eslint-visitor-keys@3.3.0: wanted: {"node":"^12.22.0 || ^14.17.0 || >=16.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: eslint-visitor-keys@3.3.0 npm WARN notsup Unsupported engine for @typescript-eslint/typescript-estree@5.46.1: wanted: {"node":"^12.22.0 || ^14.17.0 || >=16.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: @typescript-eslint/typescript-estree@5.46.1 npm WARN notsup Unsupported engine for @eslint/eslintrc@1.3.3: wanted: {"node":"^12.22.0 || ^14.17.0 || >=16.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: @eslint/eslintrc@1.3.3 npm WARN notsup Unsupported engine for @humanwhocodes/module-importer@1.0.1: wanted: {"node":">=12.22"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: @humanwhocodes/module-importer@1.0.1 npm WARN notsup Unsupported engine for eslint-scope@7.1.1: wanted: {"node":"^12.22.0 || ^14.17.0 || >=16.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: eslint-scope@7.1.1 npm WARN notsup Unsupported engine for espree@9.4.1: wanted: {"node":"^12.22.0 || ^14.17.0 || >=16.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: espree@9.4.1 npm WARN notsup Unsupported engine for @jest/core@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: @jest/core@28.1.3 npm WARN notsup Unsupported engine for jest-cli@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: jest-cli@28.1.3 npm WARN notsup Unsupported engine for @jest/console@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: @jest/console@28.1.3 npm WARN notsup Unsupported engine for @jest/reporters@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: @jest/reporters@28.1.3 npm WARN notsup Unsupported engine for @jest/test-result@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: @jest/test-result@28.1.3 npm WARN notsup Unsupported engine for @jest/transform@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: @jest/transform@28.1.3 npm WARN notsup Unsupported engine for jest-changed-files@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: jest-changed-files@28.1.3 npm WARN notsup Unsupported engine for jest-config@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: jest-config@28.1.3 npm WARN notsup Unsupported engine for jest-haste-map@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: jest-haste-map@28.1.3 npm WARN notsup Unsupported engine for jest-regex-util@28.0.2: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: jest-regex-util@28.0.2 npm WARN notsup Unsupported engine for jest-resolve@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: jest-resolve@28.1.3 npm WARN notsup Unsupported engine for jest-resolve-dependencies@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: jest-resolve-dependencies@28.1.3 npm WARN notsup Unsupported engine for jest-runner@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: jest-runner@28.1.3 npm WARN notsup Unsupported engine for jest-runtime@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: jest-runtime@28.1.3 npm WARN notsup Unsupported engine for jest-snapshot@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: jest-snapshot@28.1.3 npm WARN notsup Unsupported engine for jest-validate@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: jest-validate@28.1.3 npm WARN notsup Unsupported engine for jest-watcher@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: jest-watcher@28.1.3 npm WARN notsup Unsupported engine for jest-worker@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: jest-worker@28.1.3 npm WARN notsup Unsupported engine for write-file-atomic@4.0.2: wanted: {"node":"^12.13.0 || ^14.15.0 || >=16.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: write-file-atomic@4.0.2 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^2.3.2 (node_modules/jest-haste-map/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) npm WARN notsup Unsupported engine for @jest/test-sequencer@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: @jest/test-sequencer@28.1.3 npm WARN notsup Unsupported engine for babel-jest@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: babel-jest@28.1.3 npm WARN notsup Unsupported engine for jest-circus@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: jest-circus@28.1.3 npm WARN notsup Unsupported engine for jest-environment-node@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: jest-environment-node@28.1.3 npm WARN notsup Unsupported engine for babel-preset-jest@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: babel-preset-jest@28.1.3 npm WARN notsup Unsupported engine for babel-plugin-jest-hoist@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: babel-plugin-jest-hoist@28.1.3 npm WARN notsup Unsupported engine for @jest/environment@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: @jest/environment@28.1.3 npm WARN notsup Unsupported engine for @jest/expect@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: @jest/expect@28.1.3 npm WARN notsup Unsupported engine for jest-each@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: jest-each@28.1.3 npm WARN notsup Unsupported engine for @jest/fake-timers@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: @jest/fake-timers@28.1.3 npm WARN notsup Unsupported engine for jest-mock@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: jest-mock@28.1.3 npm WARN notsup Unsupported engine for @jest/globals@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: @jest/globals@28.1.3 npm WARN notsup Unsupported engine for @jest/source-map@28.1.2: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: @jest/source-map@28.1.2 npm WARN notsup Unsupported engine for emittery@0.10.2: wanted: {"node":">=12"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: emittery@0.10.2 npm WARN notsup Unsupported engine for jest-docblock@28.1.1: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: jest-docblock@28.1.1 npm WARN notsup Unsupported engine for jest-leak-detector@28.1.3: wanted: {"node":"^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: jest-leak-detector@28.1.3 npm WARN notsup Unsupported engine for yargs@17.6.2: wanted: {"node":">=12"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: yargs@17.6.2 npm WARN notsup Unsupported engine for cliui@8.0.1: wanted: {"node":">=12"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: cliui@8.0.1 npm WARN notsup Unsupported engine for yargs-parser@21.1.1: wanted: {"node":">=12"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: yargs-parser@21.1.1 npm WARN notsup Unsupported engine for @cspotcode/source-map-support@0.8.1: wanted: {"node":">=12"} (current: {"node":"10.19.0","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: @cspotcode/source-map-support@0.8.1 npm WARN diasend-nightscout-bridge@0.1.2 No repository field.

added 429 packages from 368 contributors and audited 431 packages in 19.703s

72 packages are looking for funding run npm fund for details

found 0 vulnerabilities

user@instance-1:~/diasend-nightscout-bridge-0.7.8$ npm fund diasend-nightscout-bridge@0.1.2 ├─┬ https://opencollective.com/typescript-eslint │ └── @typescript-eslint/eslint-plugin@5.46.1, @typescript-eslint/parser@5.46.1, @typescript-eslint/scope-manager@5.46.1, @typescript-eslint/type-utils@5.46.1, @typescript-eslint/utils@5.46.1, @typescript-eslint/types@5.46.1, @typescript-eslint/visitor-keys@5.46.1, @typescript-eslint/typescript-estree@5.46.1 ├─┬ https://github.com/cheeriojs/cheerio?sponsor=1 │ └── cheerio@1.0.0-rc.12 ├─┬ https://opencollective.com/eslint │ └── eslint@8.29.0, @eslint/eslintrc@1.3.3, espree@9.4.1 ├─┬ https://github.com/prettier/prettier?sponsor=1 │ └── prettier@2.8.1 ├─┬ https://github.com/chalk/chalk?sponsor=1 │ └── chalk@4.1.2 ├─┬ https://github.com/chalk/ansi-styles?sponsor=1 │ └── ansi-styles@4.3.0, ansi-styles@5.2.0 ├─┬ https://github.com/sponsors/jonschlinkert │ └── picomatch@2.3.1 ├─┬ https://github.com/sponsors/mysticatea │ └── regexpp@3.2.0, eslint-utils@3.0.0 ├─┬ https://github.com/sponsors/sindresorhus │ └── globby@11.1.0, escape-string-regexp@4.0.0, find-up@5.0.0, globals@13.19.0, import-fresh@3.3.0, strip-json-comments@3.1.1, locate-path@6.0.0, p-locate@5.0.0, p-limit@3.1.0, yocto-queue@0.1.0, type-fest@0.20.2, import-local@3.1.0, ansi-escapes@4.3.2, terminal-link@2.1.1, make-dir@3.1.0, p-limit@2.3.0, type-fest@0.21.3, get-stream@6.0.1, is-stream@2.0.1, onetime@5.1.2, parse-json@5.2.0, camelcase@6.3.0 ├─┬ https://github.com/sponsors/feross │ └── run-parallel@1.2.0, queue-microtask@1.2.3 ├─┬ https://www.patreon.com/feross │ └── run-parallel@1.2.0, queue-microtask@1.2.3 ├─┬ https://feross.org/support │ └── run-parallel@1.2.0, queue-microtask@1.2.3 ├─┬ https://github.com/sponsors/RubenVerborgh │ └── follow-redirects@1.15.2 ├─┬ https://github.com/sponsors/fb55 │ └── cheerio-select@2.1.0, htmlparser2@8.0.1, css-select@5.1.0, css-what@6.1.0, domelementtype@2.3.0 ├─┬ https://github.com/cheeriojs/dom-serializer?sponsor=1 │ └── dom-serializer@2.0.0 ├─┬ https://github.com/fb55/domhandler?sponsor=1 │ └── domhandler@5.0.3 ├─┬ https://github.com/fb55/domutils?sponsor=1 │ └── domutils@3.0.1 ├─┬ https://github.com/fb55/htmlparser2?sponsor=1 │ └── htmlparser2@8.0.1 ├─┬ https://github.com/inikulin/parse5?sponsor=1 │ └── parse5@7.1.2, parse5-htmlparser2-tree-adapter@7.0.0 ├─┬ https://github.com/fb55/nth-check?sponsor=1 │ └── nth-check@2.1.1 ├─┬ https://github.com/fb55/entities?sponsor=1 │ └── entities@4.4.0 ├─┬ https://github.com/sponsors/nzakas │ └── @humanwhocodes/module-importer@1.0.1 ├─┬ https://github.com/sponsors/epoberezkin │ └── ajv@6.12.6 ├─┬ https://opencollective.com/js-sdsl │ └── js-sdsl@4.2.0 ├─┬ https://github.com/sponsors/isaacs │ └── rimraf@3.0.2, glob@7.2.3 ├─┬ https://opencollective.com/babel │ └── @babel/core@7.20.5 ├─┬ https://opencollective.com/browserslist │ └── browserslist@4.21.4, caniuse-lite@1.0.30001439, update-browserslist-db@1.0.10 ├─┬ https://tidelift.com/funding/github/npm/browserslist │ └── browserslist@4.21.4, update-browserslist-db@1.0.10 ├─┬ https://tidelift.com/funding/github/npm/caniuse-lite │ └── caniuse-lite@1.0.30001439 ├─┬ https://github.com/chalk/supports-color?sponsor=1 │ └── supports-color@8.1.1 ├─┬ https://github.com/sindresorhus/execa?sponsor=1 │ └── execa@5.1.1 ├─┬ https://github.com/sponsors/ljharb │ └── resolve@1.22.1, is-core-module@2.11.0, supports-preserve-symlinks-flag@1.0.0 ├─┬ https://github.com/sindresorhus/emittery?sponsor=1 │ └── emittery@0.10.2 └─┬ https://github.com/chalk/wrap-ansi?sponsor=1 └── wrap-ansi@7.0.0

muthijammy commented 1 year ago

Good news Navid Fo suggested I should I do certain steps (phase1 and 2 in Google cloud utility) and now ns is up. However, diasend data still doesn't succeed uploading to ns but saw below log. Not sure if it transient issue or even related to diasend. I have reconfirmed diasend username/password set as heroku variable is all good. data loaded: reloading sandbox data and updating plugins tick 2022-12-13T19:45:43.421Z Resolving secret/token to permissions failed Load Complete: treatments:6, profiles:1, sitechangeTreatments:1, insulinchangeTreatments:1, sensorTreatments:2, profi

I have 3 doubts now on possible reason?

  1. When I login to diasend.com, it doesn't allow me to login unless I select Australia as country as well. It shows https://international.diasend.com/patient/account/apps#" in url. do we need variable to set this?

  1. what is the format of setting NIGHTSCOUT_URL? Do we need it when we use diasend-nightscout-bridge as plugin by npm install + merge upload code? NIGHTSCOUT_URL | http://.....my.to/

  2. I live in AU & Use mmol/L but ns is mg/dL. Do i need to set time zone and bg unit heroku variables?

Original issue is sorted and hence can be closed. But grt if u can answer

burnedikt commented 1 year ago

Good news Navid Fo suggested I should I do certain steps (phase1 and 2 in Google cloud utility) and now ns is up. However, diasend data still doesn't succeed uploading to ns but saw below log. Not sure if it transient issue or even related to diasend. I have reconfirmed diasend username/password set as heroku variable is all good. data loaded: reloading sandbox data and updating plugins tick 2022-12-13T19:45:43.421Z Resolving secret/token to permissions failed Load Complete: treatments:6, profiles:1, sitechangeTreatments:1, insulinchangeTreatments:1, sensorTreatments:2, profi

I have 3 doubts now on possible reason?

  1. When I login to diasend.com, it doesn't allow me to login unless I select Australia as country as well. It shows https://international.diasend.com/patient/account/apps#" in url. do we need variable to set this?

I think the API that we use does not have that restriction.

  1. what is the format of setting NIGHTSCOUT_URL? Do we need it when we use diasend-nightscout-bridge as plugin by npm install + merge upload code?

If you use the bridge as part of your nightscout installation, e.g. because you based your nightscout of my fork (or merged my fork into your fork), then you don't need to use NIGHTSCOUT_URL.

If you run the bridge as a standalone project on a separate server, then you'll need to configure it. The format in this case is just the base url of nightscout so the same url that you'd use to access your nightscout via a browser.

  1. I live in AU & Use mmol/L but ns is mg/dL. Do i need to set time zone and bg unit heroku variables?

Yes, I think you need to set the DISPLAY_UNITS environment variable to mmol, as per the nightscout docs.

Also, remember that you need to also set the TZ variable to your timezone, e.g. Australia/Brisbane. Find the correct name e.g. in this list.

Closing this as the original issue has been resolved, feel free to open another issue if you run into other troubles.