summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorcos <cos>2020-08-30 17:54:52 +0200
committercos <cos>2020-08-30 18:26:07 +0200
commitbfacbcb426f83b64a41d1365f9dacbf468f45122 (patch)
treeb6a060acecc3d79c65ad748454556de9cfbecea9
parent6ab4a03f9249a8b903d2e8c42a3f94bd614ff5c7 (diff)
downloadpostrunner-bfacbcb426f83b64a41d1365f9dacbf468f45122.zip
Workaround for import failureworkaround/import_regression
Starting with 1.0.0 postrunner has a bug which seems to make importing of FIT files fail for some devices. Unless I'm mistaken, there is no 'di' in scope when accessed on these lines. Simply returning 0 rather than attempting to find any proper manufacturer or product id:s makes postrunner useable again, but it is clearly not the correct fix. It would be great to properly fix this, but unfortunately I'm nowhere close to competent enough with ruby to figure out how.
-rw-r--r--lib/postrunner/FitFileStore.rb6
1 files changed, 4 insertions, 2 deletions
diff --git a/lib/postrunner/FitFileStore.rb b/lib/postrunner/FitFileStore.rb
index f2e80b6..d503826 100644
--- a/lib/postrunner/FitFileStore.rb
+++ b/lib/postrunner/FitFileStore.rb
@@ -537,8 +537,10 @@ module PostRunner
return {
:manufacturer => fid.manufacturer,
:product => fid.garmin_product || fid.product,
- :numeric_manufacturer => di.numeric_manufacturer,
- :numeric_product => di.numeric_product,
+ #:numeric_manufacturer => di.numeric_manufacturer,
+ #:numeric_product => di.numeric_product,
+ :numeric_manufacturer => 0,
+ :numeric_product => 0,
:serial_number => fid.serial_number
}
end