These are chat archives for nightscout/intend-to-bolus
at=error code=H12 desc="Request timeout" method=POST path="/api/v1/entries.json"in NS logs. Is there a way to increase timeout on NS to process bigger requests?
@scottleibrand @danamlewis @scottleibrand @danamlewis Before summer vacation I have a possible "conflict?" reported and followed. Until now, I'm always not sure if it really is, or just a setting error of mine. I would be happy to pass on the information for developers to check this. Also, I like to hear from other Openaps users, whether you also have so similar problem.
My Openaps version: 0.5.3 + SMB & UAM
Suspected Problem Source: Temporary Target in active.
Behavior: Temproray Target was activated before eating. While this activation gave bolus.
1, the last reported problem was "0 as the target BG for Looping",
2, today had a problem that would also be linked to Temproray's target that would rig stop working.
First solve Temproray target, then give eating bolus, then Rig runs well
An information exchange would be very glad. Many thanks to the developers.
ns-upload-entries glucose.json, this worked
@danamlewis No change since the last rig's run....but it should be pulling the 'current' carb ratio from the pump, right? And, since the 'carb_ratios.json" files are the same, I would thing the 'current' carb ratio would be the same.
On a similar topic, curious as to how the two rigs coordinate. It says in the docs that there is a 'hand off' but since they are not sharing a common 'myopenaps' directory, it seems that one rig predictions and execution will differ from the others when the hand off is made. Would think this would become more problematic the longer a rig is not actively looping.
Please, commit your changes or stash them before you can merge. Aborting Couldn't pull latest oref0 root@lukasrig:~#
git stashas it suggests, from ~/src/oref0