subsurface.git/core, branch v4.8.5forked from https://github.com/subsurface/subsurfacehttps://git.tsegers.com/subsurface.git/atom?h=v4.8.52019-01-23T01:35:23ZBluetooth: don't crash if BT is turned off2019-01-23T01:35:23ZDirk Hohndeldirk@hohndel.org2019-01-23T01:28:56Zurn:sha1:ec8eac185b5d42e5e250eac3678b67b36c89c46a
At least on a Mac we can get here without a discoveryAgent if BT is off,
so don't derefence the NULL pointer in that case.
Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
BLE debug: make things less verbose2019-01-22T00:07:26ZDirk Hohndeldirk@hohndel.org2019-01-21T22:14:03Zurn:sha1:0e1bd02df6cfd94c1fe61a23bccd6f86fbdc23be
Unless run with '-v -v -v'.
Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
libdivecomputer: small wording change in a warning2019-01-22T00:07:19ZDirk Hohndeldirk@hohndel.org2019-01-21T21:31:06Zurn:sha1:c000123121f64e6cb03a39d0e0e3bba12b3a0491
While in theory the DEVINFO event should give us the correct detected
product, it's also possible that the code that usually detects the
product gave up and returns an unknown model.
Try to have the message reflect that situation more accurately.
Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
Don't allow empty username for git2019-01-22T00:06:17ZRobert C. Hellinghelling@atdotde.de2019-01-12T09:04:05Zurn:sha1:fc66c767fbf552743c13ecec4141a4c153490cd5
When no real name is set in /etc/passwd the username ends
up being ",,,". Git does not like that. Actually, only the
part before the first comma is the name, the rest is office
and phone number. We don't want those.
Before we only testing for the username being a NULL pointer.
Reported-by: Keith Grimes
Signed-off-by: Robert C. Helling <helling@atdotde.de>
Use state structure for sample rate info2019-01-22T00:04:36ZMiika Turkiamiika.turkia@gmail.com2019-01-03T04:56:48Zurn:sha1:ddac55a3f12bd11fc8b3c412c919d1d9312b3a9c
Signed-off-by: Miika Turkia <miika.turkia@gmail.com>
Use correct value for PO22019-01-22T00:04:36ZMiika Turkiamiika.turkia@gmail.com2019-01-01T13:32:27Zurn:sha1:39d5860602494a550450756ca6ca0361b9fbbed1
averagePPO2 appears to be correct value instead of currentPPO2SetPoint.
Signed-off-by: Miika Turkia <miika.turkia@gmail.com>
Grab correct setpoint on Shearwater cloud import2019-01-22T00:04:36ZMiika Turkiamiika.turkia@gmail.com2018-12-31T04:21:53Zurn:sha1:6aa51c623240d4cf3fd75aef1162980c5f5f1d81
Signed-off-by: Miika Turkia <miika.turkia@gmail.com>
Use different time field as it seems to be more correct2019-01-22T00:04:36ZMiika Turkiamiika.turkia@gmail.com2018-12-30T14:31:51Zurn:sha1:f78f3075c49bcec322ba8e8077b8b72b5520b8fa
The starTimestamp is 4 hours apart on 2 different DCs within the sample
log. DiveDate on the dive_logs table seems to be correct, but must be
converted from human readable format.
Signed-off-by: Miika Turkia <miika.turkia@gmail.com>
Sample rate varies between dives2019-01-22T00:04:36ZMiika Turkiamiika.turkia@gmail.com2018-12-29T20:31:52Zurn:sha1:4aac746bf02148bdb9e2615ec6d8a9151c53b474
Seems that Shearwater cloud stores sample rate into the database and
it is not constant within the log.
Signed-off-by: Miika Turkia <miika.turkia@gmail.com>
Initial support for Shearwater Cloud2019-01-22T00:04:36ZMiika Turkiamiika.turkia@gmail.com2018-12-29T19:32:55Zurn:sha1:f5ef586c72d0f5b47bd019deda95c28633596a63
This works to some extent to part of a sample log I received. However,
still quite a bit more work is needed.
Signed-off-by: Miika Turkia <miika.turkia@gmail.com>