These are chat archives for nightscout/intend-to-bolus

9th
Oct 2018
peterfulvi
@peterfulvi
Oct 09 2018 10:34
Beacuse my OTG port is broke so i cannot reflash, i tried updating npm and node js, no luck, so i ordered a new board. I ran the bootstrap script again in an all out attempt to fix the issue and ended up with this
The following packages have unmet dependencies:
 npm : Depends: nodejs but it is not going to be installed
       Depends: node-abbrev (>= 1.0.4) but it is not going to be installed
       Depends: node-ansi (>= 0.3.0-2) but it is not going to be installed
       Depends: node-ansi-color-table but it is not going to be installed
       Depends: node-archy but it is not going to be installed
       Depends: node-block-stream but it is not going to be installed
       Depends: node-fstream (>= 0.1.22) but it is not going to be installed
       Depends: node-fstream-ignore but it is not going to be installed
       Depends: node-github-url-from-git but it is not going to be installed
       Depends: node-glob (>= 3.1.21) but it is not going to be installed
       Depends: node-graceful-fs (>= 2.0.0) but it is not going to be installed
       Depends: node-inherits but it is not going to be installed
       Depends: node-ini (>= 1.1.0) but it is not going to be installed
       Depends: node-lockfile but it is not going to be installed
       Depends: node-lru-cache (>= 2.3.0) but it is not going to be installed
       Depends: node-minimatch (>= 0.2.11) but it is not going to be installed
       Depends: node-mkdirp (>= 0.3.3) but it is not going to be installed
       Depends: node-gyp (>= 0.10.9) but it is not going to be installed
       Depends: node-nopt (>= 3.0.1) but it is not going to be installed
       Depends: node-npmlog but it is not going to be installed
       Depends: node-once but it is not going to be installed
       Depends: node-osenv but it is not going to be installed
       Depends: node-read but it is not going to be installed
       Depends: node-read-package-json (>= 1.1.0) but it is not going to be inst                                                                                                                                                             alled
       Depends: node-request (>= 2.25.0) but it is not going to be installed
       Depends: node-retry but it is not going to be installed
       Depends: node-rimraf (>= 2.2.2) but it is not going to be installed
       Depends: node-semver (>= 2.1.0) but it is not going to be installed
       Depends: node-sha but it is not going to be installed
       Depends: node-slide but it is not going to be installed
       Depends: node-tar (>= 0.1.18) but it is not going to be installed
       Depends: node-underscore but it is not going to be installed
       Depends: node-which but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
 Depends: node-request (>= 2.25.0) but it is not going to be installed
       Depends: node-retry but it is not going to be installed
       Depends: node-rimraf (>= 2.2.2) but it is not going to be installed
       Depends: node-semver (>= 2.1.0) but it is not going to be installed
       Depends: node-sha but it is not going to be installed
       Depends: node-slide but it is not going to be installed
       Depends: node-tar (>= 0.1.18) but it is not going to be installed
       Depends: node-underscore but it is not going to be installed
       Depends: node-which but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
Scott Leibrand
@scottleibrand
Oct 09 2018 12:42
@peterfulvi try removing nodejs and nodejs-legacy and reinstalling oref0 dev? It should now install nodejs 8.
peterfulvi
@peterfulvi
Oct 09 2018 13:11
@scottleibrand How do i remove it?
Do i just remove oref0 directory?
Scott Leibrand
@scottleibrand
Oct 09 2018 13:24
apt-get purge nodejs nodejs-legacy
peterfulvi
@peterfulvi
Oct 09 2018 13:28

I did that. I also removed oref0 directory (which probably was a mistke)

Package 'nodejs-legacy' is not installed, so not removed
The following packages will be REMOVED:
  nodejs*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 62.1 MB disk space will be freed.

Package 'nodejs-legacy' is not installed, so not removed
The following packages will be REMOVED:
nodejs*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 62.1 MB disk space will be freed.
Do you want to continue? [Y/n] y
Abort.
install -g oref0# cd ~/src/oref0 && git checkout master && git pull && sudo npm
-bash: cd: /root/src/oref0: No such file or directory
```

Scott Leibrand
@scottleibrand
Oct 09 2018 13:43
Go back to the curl of openaps-install to re-clone oref0 and reinstall node.
cameronrenwick
@cameronrenwick
Oct 09 2018 14:11
has anyone noticed that if your sensor goes past 30 days it no longer displays in NS?
peterfulvi
@peterfulvi
Oct 09 2018 14:19
@scottleibrand is that located in the docs.
Wiper70
@Wiper70
Oct 09 2018 14:19
Does anyone have experience with the Dana RS insulinpump and oref0? Seen it in Berlin on the EASD congres and it is an "open pump", does it work well with open APS?
peterfulvi
@peterfulvi
Oct 09 2018 14:19
Sorry
Scott Leibrand
@scottleibrand
Oct 09 2018 14:22
@cameronrenwick you’ll have to be more specific. Which sensor, transmitter, and upload method?
@Wiper70 that’s AndroidAPS.
cameronrenwick
@cameronrenwick
Oct 09 2018 14:59
Screen Shot 2018-10-09 at 10.58.17 AM.png
sorry @scottleibrand .. I'm using a G4, xdrip to android to NS. Works fine from 0hrs to 30 days, at day 31 the SAGE pill just lists nothing. I'm at day 31 right now, have recently donated data (and emptied database etc) so no worries with the "usual" reasons. Just seems like once day 30 hits, the pill goes blank.
peterfulvi
@peterfulvi
Oct 09 2018 15:03
ok i ran cd ~/src/oref0 && git checkout dev && git pull npm run global-install
Scott Leibrand
@scottleibrand
Oct 09 2018 15:04
Oh, you said “it” goes blank, so I assumed you meant all sensor (CGM) data.
@peterfulvi that is not a valid one-line command. Copy-paste issue?
peterfulvi
@peterfulvi
Oct 09 2018 15:04

this is what i got
```
oref0@0.7.0-dev global-install /root/src/oref0

npm install && sudo npm install -g && sudo npm link && sudo npm link oref0

npm WARN deprecated crypto@0.0.3: This package is no longer supported. It's now a built-in Node module. If you've depended on crypto, you should switch to the one that's built-in.
npm WARN deprecated jade@0.26.3: Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated to-iso-string@0.0.2: to-iso-string has been deprecated, use @segment/to-iso-string instead.
npm WARN deprecated node-uuid@1.4.8: Use uuid module instead
npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated hoek@2.16.3: The major version is no longer supported. Please update to 4.x or newer
npm notice created a lockfile as package-lock.json. You should commit this file.
added 228 packages from 531 contributors and audited 382 packages in 71.711s
found 15 vulnerabilities (1 low, 12 moderate, 1 high, 1 critical)
run npm audit fix to fix them, or npm audit for details
sudo: unable to resolve host rigns
npm ERR! path /home/.rootfs/usr/lib/node_modules/.staging/oref0-aa44602e/node_modules/abbrev
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall rename
npm ERR! enoent ENOENT: no such file or directory, rename '/home/.rootfs/usr/lib/node_modules/.staging/oref0-aa44602e/node_modules/abbrev' -> '/home/.rootfs/usr/lib/node_modules/.staging/abbrev-fd397e54'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2018-10-09T15_04_09_842Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 254
npm ERR! oref0@0.7.0-dev global-install: npm install && sudo npm install -g && sudo npm link && sudo npm link oref0
npm ERR! Exit status 254
npm ERR!
npm ERR! Failed at the oref0@0.7.0-dev global-install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2018-10-09T15_04_09_979Z-debug.log
``

Scott Leibrand
@scottleibrand
Oct 09 2018 15:05
I have no idea if sage supports >30d, but I would advise changing sensor before then.
@peterfulvi try again
I’ve seen some “couldn’t find X” errors recently that clear up on second install. Not sure why.
peterfulvi
@peterfulvi
Oct 09 2018 15:07
ok i will clone dev branch and run global install
peterfulvi
@peterfulvi
Oct 09 2018 15:13
ok i ran npm install npm install -gnpm install && sudo npm install -g && sudo npm link && sudo npm link oref0 and get tht error still
root@rigns:~/src/oref0# npm install && sudo npm install -g && sudo npm link && sudo npm link oref0
audited 382 packages in 21.865s
found 15 vulnerabilities (1 low, 12 moderate, 1 high, 1 critical)
  run `npm audit fix` to fix them, or `npm audit` for details
sudo: unable to resolve host rigns
npm ERR! path /home/.rootfs/usr/lib/node_modules/.staging/oref0-aa44602e/node_modules/abbrev
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall rename
npm ERR! enoent ENOENT: no such file or directory, rename '/home/.rootfs/usr/lib/node_modules/.staging/oref0-aa44602e/node_modules/abbrev' -> '/home/.rootfs/usr/lib/node_modules/.staging/abbrev-fd397e54'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2018-10-09T15_11_31_777Z-debug.log
root@rigns:~/src/oref0# root@rigns:~/src/oref0# npm install && sudo npm install -g && sudo npm link && sudo npm link oref0
-bash: root@rigns:~/src/oref0#: No such file or directory
root@rigns:~/src/oref0# audited 382 packages in 21.865s
-bash: audited: command not found
root@rigns:~/src/oref0# found 15 vulnerabilities (1 low, 12 moderate, 1 high, 1 critical)
-bash: syntax error near unexpected token `('
root@rigns:~/src/oref0#   run `npm audit fix` to fix them, or `npm audit` for details
cameronrenwick
@cameronrenwick
Oct 09 2018 15:18
@scottleibrand I can't disagree with you on the change of sensor time-frame but sometimes sensors just go on and on. I routinely get 24 days out of mine. I also cover the entire sensor with 10cm by 10 cm hypafix transparent dressing and don't get any sort of irritation or infection etc.
Scott Leibrand
@scottleibrand
Oct 09 2018 15:21
@peterfulvi maybe try the PieterGit-201808_upgrade branch? openaps/oref0#1136
peterfulvi
@peterfulvi
Oct 09 2018 15:45
Almost. Upgraded and ran got this
 oref0@0.7.0-dev global-install /root/src/oref0
> npm install && sudo npm install -g && sudo npm link && sudo npm link oref0

added 67 packages from 54 contributors, removed 73 packages, updated 41 packages and audited 360 packages in 54.888s
found 0 vulnerabilities

sudo: unable to resolve host rigns
npm ERR! path /home/.rootfs/usr/lib/node_modules/.staging/oref0-aa44602e/node_modules/abbrev
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall rename
npm ERR! enoent ENOENT: no such file or directory, rename '/home/.rootfs/usr/lib/node_modules/.staging/oref0-aa44602e/node_modules/abbrev' -> '/home/.rootfs/usr/lib/node_modules/.staging/abbrev-fd397e54'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2018-10-09T15_44_46_165Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 254
npm ERR! oref0@0.7.0-dev global-install: `npm install && sudo npm install -g && sudo npm link && sudo npm link oref0`
npm ERR! Exit status 254
npm ERR!
npm ERR! Failed at the oref0@0.7.0-dev global-install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2018-10-09T15_44_46_355Z-debug.log
Martin Haeberli
@mhaeberli
Oct 09 2018 21:28
pi zero w / pi hat rig got VERY hot charging ! (And the LCD screen got unglued when that happened). Still very hot afterwards on battery only. Any thoughts?