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

1st
Mar 2019
Scott Leibrand
@scottleibrand
Mar 01 00:00
not sure then: check ns-loop.log?
jaylagorio
@jaylagorio
Mar 01 00:00
It still does the actual basal changes and SMBs though
Looks normal?
Starting ns-loop at Thu Feb 28 18:59:02 EST 2019:
ns://JSON/shell/cgm/ns-glucose.json
reporting cgm/ns-glucose.json
ns://JSON/shell/settings/temptargets.json
reporting settings/temptargets.json
get-profile://text/shell/settings/profile.json
reporting settings/profile.json
Refreshed temptargetsns://JSON/shell/monitor/carbhistory.json
reporting monitor/carbhistory.json
 and meal-carbs
Uploaded
Hm, this is odd in carbhistory.json. Note that the 45 was delivered earlier today using a build of 0.6.2-master and the 12 is what I did just a little while ago on 0.7.0-dev:
{
    "carbs": 12,
    "eventType": "<none>",
    "created_at": "2019-02-28T21:06:58.257Z",
    "enteredBy": "",
    "reason": "",
    "insulin": null,
    "duration": 0,
    "_id": "5c784d723d96583a37664ac1"
  },
  {
    "carbs": 45,
    "ratio": "9",
    "bolus": {
      "_type": "Bolus",
      "timestamp": "2019-02-28T10:32:47-05:00",
      "programmed": 0.1,
      "amount": 0.1,
      "unabsorbed": 0,
      "duration": 0,
      "id": "AQEBAC+gShwT"
    },
    "timestamp": "2019-02-28T10:32:47-05:00",
    "created_at": "2019-02-28T10:32:47-05:00",
    "wizard": {
      "_type": "BolusWizard",
      "bg": 0,
      "bg_target_high": 100,
      "timestamp": "2019-02-28T10:32:47-05:00",
      "bolus_estimate": 5,
      "bg_target_low": 90,
      "sensitivity": 68,
      "carb_ratio": 9,
      "food_estimate": 5,
      "unabsorbed_insulin_total": 0,
      "correction_estimate": 0,
      "carb_input": 45,
      "units": "mgdl",
      "id": "WwAvoAocEy1QCURaADIAAAAAMmQ="
    },
    "enteredBy": "openaps://medtronic/722",
    "insulin": 0.1,
    "eventType": "Meal Bolus",
    "duration": 0,
    "_id": "5c7800083d96583a3765e56e",
    "notes": "Normal bolus with wizard.\nCalculated IOB: 0.454\nProgrammed bolus 0.1\nDelivered bolus 0.1\nPercent delivered:  100%\nFood estimate 5\nCorrection estimate 0\nBolus estimate 5\nTarget low 90\nTarget
high 100\nHypothetical glucose delta -6.800000000000001",
    "medtronic": "mm://openaps/mm-format-ns-treatments/Meal Bolus"
  }
Created at time for the 12 is way wrong
Scott Leibrand
@scottleibrand
Mar 01 00:08
Z is zulu: is it correct in UTC?
the 12 came from NS, the 45 from pump
that ns-loop.log looks like it's from 0.6.x?
jaylagorio
@jaylagorio
Mar 01 00:14
OK, now I remember - the 12 did come from NS and at the correct time. I thought that was the 12 I just did, which now I see doesn't show up here because that would be the first one in the list, and what I would expect to see having come from the pump along with 1.1U
Can't say why ns-loop.log looks like it would come from 0.6.x?
Starting ns-loop at Thu Feb 28 19:14:02 EST 2019:
ns://JSON/shell/cgm/ns-glucose.json
reporting cgm/ns-glucose.json
ns://JSON/shell/settings/temptargets.json
reporting settings/temptargets.json
get-profile://text/shell/settings/profile.json
reporting settings/profile.json
Refreshed temptargetsns://JSON/shell/monitor/carbhistory.json
reporting monitor/carbhistory.json
 and meal-carbs
Uploaded
^C
root@tinyaps:~/myopenaps/monitor# oref0-version
0.7.0-dev [dev]
root@tinyaps:~/myopenaps/monitor#
I just wonder why meal.json refreshed: {"carbs":14,"nsCarbs":0,"bwCarbs":14,"journalCarbs":0,"mealCOB":2 is correct, and then it says it couldn't parse data later on. That data right there is correct.
jaylagorio
@jaylagorio
Mar 01 01:04
@scottleibrand I added a PR that is explicit about which data in oref0-meal is the one that fails processing. So this tells me that pumphistory is the culprit. Looking at my loop log oref0-meal is called at the beginning, right after pump clock and temp refresh check, and optionally at the end if enacted/bolus. It's this second call that fails even when the first one succeeds, but it's the second one that updates the loop's knowledge of COB. I seem to remember there used to be several files that held pumphistory, but now I'm just finding /myopenaps/monitor/pumphistory-24h-zoned.json. Is that where this bad data would be pulled from? And if so, why does it succeed at the beginning and the end but not the middle?
DaisyHK
@laurathiessen
Mar 01 04:44
Hey guys question:previously using android with BT tethering, xdrip& dexcom, edison/explorer and Sony smart watch 3. I got a new iphone SO: Is it possible to use OpenAPS with explorer/edison & iphone 8/spike ap &miaomiao/libre/NS ?? I can easily set it spike up with NS, but I am unsure of what to use in set up script for "what kind of CGM would you like to cofigure for offline use" spike is not an option & "what kind of CGM would you like to configure" miaomiao or libre is not an option i can see... ALSO guessing i follow the BT tethering instructions VIA OpenAPS and NOT LOOP?
TranceCake
@TranceCake
Mar 01 06:59
Hi, yesterday I tried to install oref0 on a new sd card for my backup rig and I noticed the installer was installing 0.2.1 instead of 0.7.0 dev, is there a way to manually correct this?
Dana Lewis
@danamlewis
Mar 01 07:10
Follow the steps to see what version of oref0 it finished installing, and if needed, refills the steps for installing dev: https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/update-your-rig.html
You may be seeing the version of a different package than oref0 itself, but check the version per the top of that page first
TranceCake
@TranceCake
Mar 01 07:15
oh, sorry for asking something that's in the docs! my bad!
and thanks!
JohnDoeAkira
@JohnDoeAkira
Mar 01 08:45
Hello, after some month of happy looping (oref0, only basal changes, enlite, 722, edison explorer) I'd like to try smb. I have one question about software version : do I have to upgrade to a newer version than the 0.6.2 ? My second question related to the basal level. Most of the time, my rates are between 0.5 and 0.6. During the night, I have periods of 0.45. Is this a problem for smb ? I read that a too low basal rate can be a problem ... What's your opinion/experience on this ?
djnoor
@djnoor
Mar 01 16:11
If I'm looping offline, will Pushover alerts and IFTTT commands still work? Or do those require an internet connection?
TranceCake
@TranceCake
Mar 01 16:53
@laurathiessen I don't know about Ios or spike, but I use the libre + miaomiao and in the setup I choose xdrip as CGM
@danamlewis you were right, I didn't switch to the def branch, derp. However now that I am, I'm getting an npm error that we cannot seem to solve on the diabetes discord:
(node:2474) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
npm WARN package.json crypto@0.0.3 crypto is also the name of a node core module.
npm WARN package.json crypto@0.0.3 No license field.
npm WARN package.json json@9.0.6 No license field.
npm WARN package.json share2nightscout-bridge@0.1.6 license should be a valid SPDX license expression
npm ERR! Error: Method Not Allowed
npm ERR!     at errorResponse (/usr/share/npm/lib/cache/add-named.js:260:10)
npm ERR!     at /usr/share/npm/lib/cache/add-named.js:120:12
npm ERR!     at saved (/usr/share/npm/node_modules/npm-registry-client/lib/get.js:167:7)
npm ERR!     at FSReqWrap.oncomplete (fs.js:135:15)
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR!     <http://github.com/npm/npm/issues>

npm ERR! System Linux 4.14.98+
npm ERR! command "/usr/bin/node" "/usr/bin/npm" "install"
npm ERR! cwd /root/src/oref0
npm ERR! node -v v8.11.1
npm ERR! npm -v 1.4.21
npm ERR! code E405
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /root/src/oref0/npm-debug.log
npm ERR! not ok code 0

npm ERR! oref0@0.7.0-dev global-install: `npm install && sudo npm link && sudo npm link oref0 && sudo npm install -g`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the oref0@0.7.0-dev global-install script.
npm ERR! This is most likely a problem with the oref0 package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm install && sudo npm link && sudo npm link oref0 && sudo npm install -g
npm ERR! You can get their info via:
npm ERR!     npm owner ls oref0
npm ERR! There is likely additional logging output above.
npm ERR! System Linux 4.14.98+
npm ERR! command "/usr/bin/node" "/usr/bin/npm" "run" "global-install"
npm ERR! cwd /root/src/oref0
npm ERR! node -v v8.11.1
npm ERR! npm -v 1.4.21
npm ERR! code ELIFECYCLE
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian

npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /root/src/oref0/npm-debug.log
npm ERR! not ok code 0
TranceCake
@TranceCake
Mar 01 17:01
someone there suggested to run these npm install && sudo npm link && sudo npm link oref0 && sudo npm install -g commands without sudo but that also did not work
jaylagorio
@jaylagorio
Mar 01 17:11
@djnoor Those require an Internet connection because the rig has to go out to those services to get/send info
Dana Lewis
@danamlewis
Mar 01 17:13
@JohnDoeAkira no, master (0.6.2) is fine for enabling smb and those basals aren’t too low. (That would be <.3, but some people even then choose to use it regardless)
@TranceCake :+1: no worries. Hmm I think someone might have had a similar problem a few days ago, trying to remember if it was npm or node and what they un and reinstalled to resolve.
TranceCake
@TranceCake
Mar 01 17:29
I could try both?
djnoor
@djnoor
Mar 01 17:47
@jaylagorio Thanks!
Dana Lewis
@danamlewis
Mar 01 17:49
@TranceCake might be worth scrolling back or searching and see if you can find what they uninstalled? Or do all the things and see what works? Sometimes it’s a choice driven by personality :smile:
I see someone posted on fbk w/ a similar issue, so would be good to figure out what it is.
TranceCake
@TranceCake
Mar 01 17:51
what do you mean by 'what they uninstalled'?
Dana Lewis
@danamlewis
Mar 01 17:51
(Also @cluckj might remember what was needed reinstalling? I think he helped with troubleshooting)
TranceCake
@TranceCake
Mar 01 17:51
I scrolled back through the error log (all 5000) and it is right after it deinstalled webpack
I reinstalled both and that didn't help
Dana Lewis
@danamlewis
Mar 01 17:51
(I can’t remember what package or tool they uninstalled and reinstalled to resolve; npm or node or apt or ..)
K
TranceCake
@TranceCake
Mar 01 17:52
oh, okay yeah I will scroll back here to find it
Dana Lewis
@danamlewis
Mar 01 17:53
While waiting for some input - you installed master but then switched to dev and then this is what happened? Or did you do a dev install from scratch? (Wondering if you attempted run-again for oref0-setup or did the full interactive script?)
TranceCake
@TranceCake
Mar 01 17:59
I ran the initial install command:
sudo bash curl -s https://raw.githubusercontent.com/openaps/oref0/dev/bin/openaps-install.sh > /tmp/openaps-install.sh && bash /tmp/openaps-install.sh
which went fine, then I contrl+c'd out and switched to dev branch, after that did the npm run global-install
I just checked my other rig that installed fine back in january and it runs the same node/npm versions, only difference is that it was flashed using pi bakery
TranceCake
@TranceCake
Mar 01 18:05
so that mean I did not yet get to the interactive part yet. although I did go through that when I accidentally ran the master version yesterday
I'm tempted to just flash the sd card again and start over but it might be nice to preserve this state so it can be debugged further since this isn't an isolated event
Dana Lewis
@danamlewis
Mar 01 18:06
hm, yes. wondering if the issue is connected to it running after master was installed and set up. might be worth trying a fresh reflash of the Edison (if you could stand it) and install dev immediately without doing master, and see if the same errors persist?
well - we have someone else with it so i'm pretty confident we can recreate it again. It might be more helpful to confirm if it's related to switching (my guess it is because the branches are so different) or not
TranceCake
@TranceCake
Mar 01 18:08
by that you mean running the curl command I posted above and then not going though the interactive stup right?
I'm going to do that and I will get back to you
Dana Lewis
@danamlewis
Mar 01 18:10
oh sorry. we are talking about Pi. I would do a fresh setup of the SD card (either Pi bakery or whatever method you did before) and then go from there. so start here in the docs: https://openaps.readthedocs.io/en/latest/docs/Build%20Your%20Rig/pi-install.html
(my brain said reflash Edison but what it meant was re-setting up the SD card with a new Raspian image)
TranceCake
@TranceCake
Mar 01 18:11
yeah I gocha :)
Dana Lewis
@danamlewis
Mar 01 18:18
(sounds like the person on Fbk had a Pi w/ same error that also had an older version of oref0 on it (maybe a pre-Go dev?) before attempting the dev install.)
JohnDoeAkira
@JohnDoeAkira
Mar 01 18:23
Thank you Dana.
TranceCake
@TranceCake
Mar 01 18:23
ooh, sounds promising!
BTW Dana I wanted to thank you for setting up this project, it has changed my life!
Dana Lewis
@danamlewis
Mar 01 18:24
@TranceCake :purple_heart: :smile:
TranceCake
@TranceCake
Mar 01 18:31
Travel rig.jpeg
Look how small I got it! Isn't it cute?
Dana Lewis
@danamlewis
Mar 01 18:32
nice!
TranceCake
@TranceCake
Mar 01 18:33
I did manage to kill the last one by putting it in an insulated envelope... It burned itself
Martin Haeberli
@mhaeberli
Mar 01 19:06
@jansche belated :+1:
renegadeandy
@renegadeandy
Mar 01 19:12
Hi all, can somebody help me understand why i have been administered a temp basal of 1.1 units per hour , when my bg is lower than my target, and i have been tending towards low for the past 2 hours :
Starting oref0-pump-loop at Fri Mar  1 19:05:03 GMT 2019 with 10 second wait_for_silence:
Waiting up to 4 minutes for new BG: ...............glucose.json newer than pump_loop_completed

Listening for 10s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Fri Mar  1 19:08:20 GMT 2019
Preflight OK. Profile less than 60m old; Profile valid. Pump history updated through 2019-03-01T18:59:30Z with 0 new records; meal.json refreshed: {"carbs":84,"nsCarbs":84,"bwCarbs":0,"journalCarbs":0,"mealCOB":0,"currentDeviation":-0.39,"maxDeviation":0,"minDeviation":-2.78,"slopeFromMaxDeviation":0,"slopeFromMinDeviation":0.568,"allDeviations":[0,-1,-1,-2,-3,-1],"lastCarbTime":1551454969000,"bwFound":false}
Listening for 10s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Fri Mar  1 19:09:10 GMT 2019
Checking that pump clock: "2019-03-01T19:08:58Z" is within 90s of current time: 2019-03-01T19:09:12+0000
Temp refreshed: monitor/temp_basal.json: {"duration":21,"temp":"absolute","rate":1.1}
{"carbs":84,"nsCarbs":84,"bwCarbs":0,"journalCarbs":0,"mealCOB":0,"currentDeviation":-0.39,"maxDeviation":0,"minDeviation":-2.78,"slopeFromMaxDeviation":0,"slopeFromMinDeviation":0.553,"allDeviations":[0,-1,-1,-2,-3,-1],"lastCarbTime":1551454969000,"bwFound":false}
Autotune exists! Hoorah! You can use microbolus-related features.
{"iob":-0.442,"activity":-0.0021,"basaliob":-0.575,"bolusiob":0.133,"netbasalinsulin":-2.1,"bolusinsulin":3.4,"time":"2019-03-01T19:09:00.000Z","iobWithZeroTemp":{"iob":-0.442,"activity":-0.0021,"basaliob":-0.575,"bolusiob":0.133,"netbasalinsulin":-2.1,"bolusinsulin":3.4,"time":"2019-03-01T19:09:00.000Z"},"lastBolusTime":1551454969000,"lastTemp":{"rate":1.1,"timestamp":"2019-03-01T18:59:30Z","started_at":"2019-03-01T18:59:30.000Z","date":1551466770000,"duration":10.5}}
{"delta":-1,"glucose":79,"noise":1,"short_avgdelta":-0.94,"long_avgdelta":-1.25,"date":1551467243965,"last_cal":276}
Autosens ratio: 1; Basal unchanged: 1.15; ISF unchanged: 56.2; CR: 8.594
currenttemp: { duration: 21, temp: 'absolute', rate: 1.1 } lastTempAge: 10 m tempModulus: 1 m
SMB disabled (no enableSMB preferences active)
Last carbs 207 minutes ago; remainingCATime: 8.2 hours; 100% carbs absorbed
Carb Impact: -1.6 mg/dL per 5m; CI Duration: 0 hours; remaining CI (~2h peak): 0 mg/dL per 5m
UAM Impact: -1.6 mg/dL per 5m; UAM Duration: 0 hours
minPredBG: 81 minIOBPredBG: 86 minZTGuardBG: 80 minUAMPredBG: 81 avgPredBG: 95 COB: 0 / 84
BG projected to remain above 5.3 for 0 minutes
BG projected to remain above 3.8 for 240 minutes
naive_eventualBG: 104 bgUndershoot: -36.5 zeroTempDuration: 240 zeroTempEffect: 255 carbsReq: -45
2019-03-01T19:09:23.462Z
Checking deliverAt: 2019-03-01T19:09:23.462Z is within 1m of current time: Fri Mar  1 19:09:23 GMT 2019
and that smb-suggested.json is less than 1m old
enact/smb-suggested.json: {"temp":"absolute","bg":79,"tick":-1,"eventualBG":93,"insulinReq":0,"reservoir":"149.1\n","deliverAt":"2019-03-01T19:09:23.462Z","sensitivityRatio":1,"COB":0,"IOB":-0.442}
"COB: 0, Dev: -0.6, BGI: 0.0, ISF: 3.1, CR: 8.59, Target: 5.3, minPredBG 4.5, minGuardBG 4.3, IOBpredBG 5.3; Eventual BG 5.2 < 5.3, temp 1.1 ~< req 1U/hr. "
IOB: [79,78,77,77,77,77,77,77,78,78,79,80,81,82,83,84,85,85,86,87,88,88,89,90,90,91,91,92,92,92,93,93,93,94,94,94,94,94,95]
ZT:  [79,80,80,81,82,84,85,87,88,90,93,95]
No smb_enact needed. Checking pump status (suspended/bolusing): {"status":"normal","bolusing":false,"suspended":false}
Temp refreshed: monitor/temp_basal.json: {"duration":21,"temp":"absolute","rate":1.1}
image.png
Scott Leibrand
@scottleibrand
Mar 01 19:20
your IOB of -0.4 is calculated to be just enough to bring your BG back up to 5.2, which is close enough to your target of 5.3 that a low temp is not needed
if you want it to zero-temp sooner, you could raise your target to something between 5.5 and 6.
renegadeandy
@renegadeandy
Mar 01 19:24
it got it wrong here though....im not sure why the IOB of -0.4 is calculated to be enough to bring the bg back up to 5.2, if I am at 4.2,,,and have been coming down and down steadily over a number of hours. It seems wrong here?
and infact, was wrong..
even now, im at 4.0, and its still giving me a temp basal of 0.85
Scott Leibrand
@scottleibrand
Mar 01 19:29
your ISF is 56.2 mg/dL, and 0.4U * 56.2 = 22.5 mg/dL. so you're probably running more sensitive and your basal needs are lower than 1.15 U/h right now. one thing to double-check is whether autotune has been trying to lower your basals for this time of day...
you can also set a high temp target if you know you're running more sensitive than normal, particularly if you have the exercise mode preference active
TranceCake
@TranceCake
Mar 01 19:45
:( @danamlewis I still get the error with a fresh install
so it's not the switching
@scottleibrand I saw you mentioning someone above that had an error with npm install && sudo npm link && sudo npm link oref0 && sudo npm install -g and that you were interested in what kind of error they had. I didn't see a response from them but I think I have the same issue.
Scott Leibrand
@scottleibrand
Mar 01 19:53

looks like your error is:

npm ERR! Error: Method Not Allowed
npm ERR!     at errorResponse (/usr/share/npm/lib/cache/add-named.js:260:10)
npm ERR!     at /usr/share/npm/lib/cache/add-named.js:120:12
npm ERR!     at saved (/usr/share/npm/node_modules/npm-registry-client/lib/get.js:167:7)
npm ERR!     at FSReqWrap.oncomplete (fs.js:135:15)

I've never seen that before, and it's not referencing any of our code, so not sure where to look. I'd start by just trying again to make sure it wasn't transient. If it persists and you think it's related to any of the recent changes to oref0 dev, you could check out an older commit and see if that makes the problem go away. If so, it'd be good to try all of the individual commits to see which one broke it (maybe by introducing a broken dependency?)

TranceCake
@TranceCake
Mar 01 19:55
yeah I can try that
I had it 4 times earlier today on another flash of the sd card, but now also on the new one
gonna try running it a couple of times more. Do we know if there have been any other people trying a fresh install since yesterday that did succeed?
TranceCake
@TranceCake
Mar 01 20:11
after switching to an older commit should I do more than just re-run the global install?
Scott Leibrand
@scottleibrand
Mar 01 20:14
nope, that should do it
TranceCake
@TranceCake
Mar 01 20:17
ok, walking through them now
I think I already have a clue which commit it might be: 2f742c6ec755cb66212c001d351365c059a83f32
This commit added webpack to the install and I went through the npm error log and the error occurred right after it did something with webpack. Verifying anyway though.
TranceCake
@TranceCake
Mar 01 20:30
yeah commit fd53d84 get's past the spot where it crashed
since the next one is the one that introduces webpack and I also saw that in the error logs that might be the culprit
TranceCake
@TranceCake
Mar 01 21:29
I tried to just check that branch out and go from there. The installation worked but during the oref0-setup it automatically puts me back to the current head and re-installs oref0, which fails again.
Dana Lewis
@danamlewis
Mar 01 21:33
yea someone else's dev is bonking. @scottleibrand should we go ahead and roll back since no one with Pi can get a working install?
Scott Leibrand
@scottleibrand
Mar 01 21:33
ok, yeah, let me roll back the webpack commit and see if that fixes it
Dana Lewis
@danamlewis
Mar 01 21:34
:+1: (and @TranceCake thanks for being so thorough about helping us test!)
TranceCake
@TranceCake
Mar 01 21:34
yeah no problem, that is the least I could do!!
Scott Leibrand
@scottleibrand
Mar 01 21:35
reverted 2f742c6ec755cb66212c001d351365c059a83f32 and pushed to dev: can you confirm that fixes it?
TranceCake
@TranceCake
Mar 01 21:36
let me try, can I just try again or should I remove some stuff to clean up?
Scott Leibrand
@scottleibrand
Mar 01 21:36
just git checkout dev and git pull on dev and try again
TranceCake
@TranceCake
Mar 01 21:37
running it now
TranceCake
@TranceCake
Mar 01 22:05
hmm, It gave me 2 errors in the oref0-setup, the installation prior to that went fine though.
The first error was at the check for the oref0 installation in the oref0-setup. it tried to install oref0 again and that went ok. not sure why this happened:
Checking /root/myopenaps: mkdir: cannot create directory ‘/root/myopenaps’: File exists
/root/myopenaps initialized
/root/src/oref0/ already exists; pulling latest
Already up-to-date.
v8.11.1
Checking oref0 installation
(node:12139) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
npm ERR! invalid: oref0@0.7.0-dev /usr/local/lib/node_modules/oref0
npm ERR! not ok code 0
Installing latest oref0 from /root/src/oref0/
(node:12157) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.

> oref0@0.7.0-dev global-install /root/src/oref0
> npm install && sudo npm link && sudo npm link oref0 && sudo npm install -g
Scott Leibrand
@scottleibrand
Mar 01 22:06
I think those os.tmpDir() messages are just warnings, so not sure what the ERR is...
TranceCake
@TranceCake
Mar 01 22:06
in the middle, below the warning
Scott Leibrand
@scottleibrand
Mar 01 22:07
yeah, not sure what it means by "invalid"
TranceCake
@TranceCake
Mar 01 22:07
it did install it again succesfully I think
Scott Leibrand
@scottleibrand
Mar 01 22:07
if necessary you might try deleting /usr/local/lib/node_modules/oref0 and re-running in case it's barfing on a cached copy
Riko L
@Ricco555
Mar 01 22:07
if it helps, I'm on fd53d840 and that two NPM ERR were always there when running install
TranceCake
@TranceCake
Mar 01 22:07
the second error was near the end of the oref0-setup:
npm ERR! cb() never called!
npm ERR! not ok code 0

npm ERR! oref0@0.7.0-dev global-install: `npm install && sudo npm link && sudo npm link oref0 && sudo npm install -g`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the oref0@0.7.0-dev global-install script.
npm ERR! This is most likely a problem with the oref0 package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm install && sudo npm link && sudo npm link oref0 && sudo npm install -g
npm ERR! You can get their info via:
npm ERR!     npm owner ls oref0
npm ERR! There is likely additional logging output above.
npm ERR! System Linux 4.14.98+
npm ERR! command "/usr/bin/node" "/usr/bin/npm" "run" "global-install"
npm ERR! cwd /root/src/oref0
npm ERR! node -v v8.11.1
npm ERR! npm -v 1.4.21
npm ERR! code ELIFECYCLE
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian

npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /root/src/oref0/npm-debug.log
npm ERR! not ok code 0
/root/src/oref0/bin/oref0-setup.sh: line 751: oref0-get-profile: command not found
Could not run oref0-get-profile
this one was new
I thought I did see something like it somewhere here recently but could not find it again
Scott Leibrand
@scottleibrand
Mar 01 22:09
dunno
TranceCake
@TranceCake
Mar 01 22:10
I edited it, I missed two lines
jrw35
@jrw35
Mar 01 22:10
I'm the other person on Facebook that @danamlewis mentioned above. My results look very similar to what @TranceCake is seeing.
TranceCake
@TranceCake
Mar 01 22:15
deleted /usr/local/lib/node_modules/oref0 and am trying again
Dana Lewis
@danamlewis
Mar 01 22:18
@jrw35 thx for hopping over here - can you paste what you're getting here rather than Fbk so we can better cross compare error messages? thx
jrw35
@jrw35
Mar 01 22:22

Thanks. Of course. I just replied on there to @scottleibrand asking about gitter connectivity... one of the errors I see says

npm ERR! fatal: unable to connect to github.com:
npm ERR! github.com[0: 62.252.172.241]: errno=Connection timed out

but I can ping 62.252.172.241 perfectly well. The other errors I get look like they match the extract above.

TranceCake
@TranceCake
Mar 01 22:30
hmm, I don't see the cb() never called! error I got on my first line in your log
jrw35
@jrw35
Mar 01 22:32
No, you're right, it's not there.
TranceCake
@TranceCake
Mar 01 22:33
btw if this run fails I need to go to bed, so I won't be able to help more, I'll see if I can find more tomorrow if it does fail
jrw35
@jrw35
Mar 01 22:36

npm debug log:

https://www.dropbox.com/s/7oozlg8wfrhq2d0/npm-debug-log.png

(I've tried to get that to appear as an image but it won't)

TranceCake
@TranceCake
Mar 01 22:39
not much new info in there I think anyway
but don't rely on that, I just went low
Abigail Cember
@acember
Mar 01 22:40
Guys, I'm wondering this about autotune: I'm much more likely to have been looping overnight than during the day, but I see that autotune still has suggestions about my basal rate for the whole day. Is it analyzing the behavior of my BGs based on NS data only, even if I wasn't looping during those hours? I'm pretty good about entering all boluses and food, so if so that calculation is valuable.
Scott Leibrand
@scottleibrand
Mar 01 22:41
yes, it's assuming that you got your scheduled basal any time there wasn't a temp basal recorded
Abigail Cember
@acember
Mar 01 22:43
Cool and interesting. According to the rig, I need way less basal than my pump setting. Which is probably true, because I often use ridiculously low carb ratios.
Scott Leibrand
@scottleibrand
Mar 01 22:43
so if that's a correct assumption, and all other insulin dosing is recorded, it'll try to autotune the whole day. but we aware that it can't autotune periods that were excluded for meal absorption, so it may just end up recommend a flat interpolation between basal-tunable periods.
its CR suggestions should be pretty solid, though, in light of the suggested basal
the one thing to keep in mind is that autotune assumes that the autotuned basals are what's in effect, so if those differ a lot from your pump it may start to make other recommendations based on that assumption that aren't quite ideal.
jrw35
@jrw35
Mar 01 22:45
Hope you're ok now, @TranceCake. I'm trying it one last time before bed.
Nope. Same.
Scott Leibrand
@scottleibrand
Mar 01 22:46
probably worth trying different oref0 commits and see if you can narrow down the problem. we thought we'd identified it as the webpack commit, but reverting that doesn't seem to have helped?
you can also try reverting individual commits on your local copy of oref0 on the rig...
TranceCake
@TranceCake
Mar 01 22:47
it helped, but this is a different error for me
Scott Leibrand
@scottleibrand
Mar 01 22:48
were you ever able to get it to work all the way through with an older commit?
TranceCake
@TranceCake
Mar 01 22:48
added process://ns/nightscout/ns NIGHTSCOUT_HOST API_SECRET
jq: error: Could not open file jq: No such file or directory
jq: error: Could not open file .extra.args |= sub(" API_SECRET " ; " 0301a5199529eea6b53bfed7119726af4b242bcb "): No such file or directory
close failed in file object destructor:
sys.excepthook is missing
lost sys.stderr
Traceback (most recent call last):
  File "/usr/local/bin/openaps-import", line 89, in <module>
    app( )
  File "/usr/local/lib/python2.7/dist-packages/openaps/cli/__init__.py", line 51, in __call__
    self.run(self.args)
  File "/usr/local/bin/openaps-import", line 77, in run
    candidates = json.load(args.input)
  File "/usr/lib/python2.7/json/__init__.py", line 291, in load
    **kw)
  File "/usr/lib/python2.7/json/__init__.py", line 339, in loads
    return _default_decoder.decode(s)
  File "/usr/lib/python2.7/json/decoder.py", line 364, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/lib/python2.7/json/decoder.py", line 382, in raw_decode
    raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
Could not run nightscout autoconfigure-device-crud
no, because if went and pulled the newest commit from the branch
gotaa go no, hope this error helps a bit
jrw35
@jrw35
Mar 01 22:53
Thanks, @scottleibrand. Is there a quick way to explain how to choose a specific commit? I've tried git checkout <number> but git pull wants me to do stuff that I haven't done before. If this is a stupid beginner's question then tell me and I'll go back to lurking and waiting.
Scott Leibrand
@scottleibrand
Mar 01 22:57
you can do git log to see the recent commits, and then git checkout 4ccbd0af0a05081198c1ada96935edcd698730cf to check out that specific one. then repeat for each older one.
jrw35
@jrw35
Mar 01 22:58
Thanks. And then do npm run global-install?
Scott Leibrand
@scottleibrand
Mar 01 22:59
yeah, after each checkout
jrw35
@jrw35
Mar 01 22:59
Thanks. Trying it now.
jrw35
@jrw35
Mar 01 23:27
Hmm. I've changed ISP recently and have just been reading about other people having trouble connecting to git:// URLs with their router. I think I need to investigate the firewall in the morning to see whether that's behind all the other problems. Time for bed now. Thanks for all your help.
jrw35
@jrw35
Mar 01 23:32
Very weird. git clone git://github.com/nightscout/share2nightscout-bridge.git fails as part of the install (with the "unable to connect to github.com" error). It succeeds if I run it on its own from the command line.
Scott Leibrand
@scottleibrand
Mar 01 23:33
weird
jrw35
@jrw35
Mar 01 23:36
I'm going to bed now but will keep trying in the morning. Thanks again.
jrw35
@jrw35
Mar 01 23:45
Progress. sudo git config --global url.https://github.com/.insteadOf git://github.com/ has made a big difference. The installer is doing a lot of stuff very slowly and I'm going to leave it to get on with it.
It's actually finished. Wow.
Scott Leibrand
@scottleibrand
Mar 01 23:56
nice