Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Jan 31 2019 15:51
    xen0n starred openaps/oref0
  • Jan 31 2019 15:12
    cclauss opened #1191
  • Jan 31 2019 15:09
    cclauss edited #1190
  • Jan 31 2019 15:08
    cclauss edited #1189
  • Jan 31 2019 15:07
    cclauss edited #1190
  • Jan 31 2019 15:07
    cclauss opened #1190
  • Jan 31 2019 15:00
    cclauss synchronize #1189
  • Jan 31 2019 14:52
    cclauss opened #1189
  • Jan 31 2019 14:10
  • Jan 31 2019 14:06
    Owaisaaa starred openaps/docs
  • Jan 31 2019 12:20
    cclauss synchronize #22
  • Jan 31 2019 12:16
    cclauss opened #22
  • Jan 31 2019 12:11
    cclauss edited #21
  • Jan 31 2019 12:09
    cclauss opened #21
  • Jan 31 2019 11:31
    tuzoenduro commented #1406
  • Jan 31 2019 11:25
    cclauss opened #140
  • Jan 30 2019 05:53
  • Jan 29 2019 16:03
    tzachi-dar commented #1406
  • Jan 29 2019 14:46
    rostag starred openaps/oref0
  • Jan 27 2019 22:06
    PieterGit synchronize #1176
Katja Jacob
@straykatz
sounds good
Jon Cluck
@cluckj
thanks :D
Katja Jacob
@straykatz
:)
Jon Cluck
@cluckj
when it's done, make sure your preferences.json has that cgm_loop_path entry
Katja Jacob
@straykatz
will do, thankyou

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

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 minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated boom@2.10.1: This version is no longer maintained. Please upgrade to the latest version.
npm WARN deprecated hoek@2.16.3: This version is no longer maintained. Please upgrade to the latest version.
npm WARN deprecated cryptiles@2.0.5: This version is no longer maintained. Please upgrade to the latest version.
npm ERR! path /root/src/oref0/node_modules/yargs/node_modules/cliui/node_modules/wrap-ansi/node_modules/strip-ansi/node_modules/ansi-regex
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall rename
npm ERR! enoent ENOENT: no such file or directory, rename '/root/src/oref0/node_modules/yargs/node_modules/cliui/node_modules/wrap-ansi/node_modules/strip-ansi/node_modules/ansi-regex' -> '/root/src/oref0/node_modules/ansi-regex'
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/2019-02-25T04_23_25_692Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 254
npm ERR! oref0@0.6.2 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.6.2 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/2019-02-25T04_23_25_906Z-debug.log
root@Diabeetle:~/src/oref0#

Scott Leibrand
@scottleibrand
are you back online?
Katja Jacob
@straykatz
yes
well
I was :)
Jon Cluck
@cluckj
lol
Katja Jacob
@straykatz
NS has an entry from 2 minutes ago
from this rig
Scott Leibrand
@scottleibrand
try the command again first
JustineAnne
@MicheleJustine
@scottleibrand I ran the two commands you suggested to install node js and they seemed to go ok. Here is latest printout from terminal:
sudo apt-get install -y nodejs || die "Couldn't install nodejs"
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
nodejs-legacy
The following packages will be upgraded:
nodejs
1 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 13.1 MB of archives.
After this operation, 48.5 MB of additional disk space will be used.
Get:1 https://deb.nodesource.com/node_8.x stretch/main i386 nodejs i386 8.15.0-1nodesource1 [13.1 MB]
Fetched 13.1 MB in 5s (2377 kB/s)
(Reading database ... 36213 files and directories currently installed.)
Removing nodejs-legacy (4.8.2~dfsg-1) ...
(Reading database ... 36205 files and directories currently installed.)
Preparing to unpack .../nodejs_8.15.0-1nodesource1_i386.deb ...
Unpacking nodejs (8.15.0-1nodesource1) over (4.8.2~dfsg-1) ...
Setting up nodejs (8.15.0-1nodesource1) ...
Processing triggers for man-db (2.7.6.1-2) ...
Scott Leibrand
@scottleibrand
cool. does that allow you to proceed where you left off?
JustineAnne
@MicheleJustine
@scottleibrand Problem is I am not sure where I left off. We never got to the OpenAPS part..
Scott Leibrand
@scottleibrand
try the bootstrap script again?
JustineAnne
@MicheleJustine
From the start?
Scott Leibrand
@scottleibrand
I guess it must've gotten wifi working successfully, so...
which branch were you trying to install? master?
JustineAnne
@MicheleJustine
yes it did. I am not sure how to get the prompt for re-doing bootstrap again
Katja Jacob
@straykatz
ok, this time it stuck ... running setup next
Scott Leibrand
@scottleibrand
@MicheleJustine here's a custom excerpt of the bootstrap script to try:
(
BRANCH=master
echo "Press Enter to continue installing the current release (master) of oref0,"
read -p "or enter the oref0 branch name to install." -r
BRANCH=${REPLY:-master}
curl https://raw.githubusercontent.com/openaps/oref0/$BRANCH/bin/openaps-install.sh > /tmp/openaps-install.sh $BRANCH
bash /tmp/openaps-install.sh
)
Katja Jacob
@straykatz
G6 or G6-upload?
Scott Leibrand
@scottleibrand
do you want it to upload from the rig, or is your phone doing that?
@MicheleJustine if that doesn't work, it's fine to re-run bootstrap and set up wifi over again
Katja Jacob
@straykatz
Well, Ideally ... it would be from the rig - in case the phone is not available/\discharged etc. what are the disadvantages?
Scott Leibrand
@scottleibrand
if you have them both uploading, you'll have 2x as much data in NS
but it should be identical data, so other than watching for full mongo collections I don't think there's any problem with doing both
we routinely upload from three CGM receivers, but we also host our own mongo and NS on our own server, not heroku/mongolab
Katja Jacob
@straykatz
OK. Pros?
I assume, I don't need THAT phone, as long as I have the rig online?
Scott Leibrand
@scottleibrand
right
Katja Jacob
@straykatz
and, how would I stop the phone from uploading? take Dexcom app off?
Scott Leibrand
@scottleibrand
yeah, but only do that if you don't want to use Dexcom share/follow/clarity
Katja Jacob
@straykatz
oh, wait - does this mean the receiver would have to stay physically connected to the rig?
Scott Leibrand
@scottleibrand
most people leave the Dexcom app running for redundancy. if you wanted to you could disable the share bridge in NS
Katja Jacob
@straykatz
at all times?
riught
Scott Leibrand
@scottleibrand
yeah, that's not a great primary option: you'll still want to upload from your phone
just a question of whether you also want the rig uploading
Dana Lewis
@danamlewis
@mattlumpkin ^ @straykatz is doing all the g6 upload testing for you ;)
Katja Jacob
@straykatz
OK. Yes, I want to have that option, e.g. when I am out of phone
:) with a lot of self-interest ... win-win-win, huh :)
JustineAnne
@MicheleJustine
@scottleibrand any other ideas? once again, bootstrap won't complete and I get: "broken packages" message
Scott Leibrand
@scottleibrand
was that with my excerpt?
Katja Jacob
@straykatz
well. I'll go G6 first and see if that works, and later/tomorrow the G6-upload
Scott Leibrand
@scottleibrand
@MicheleJustine this is an edison rig, right?