search

pyrevitlabs / pyRevit

Rapid Application Development (RAD) Environment for Autodesk Revit®
http://wiki.pyrevitlabs.io
GNU General Public License v3.0
1.33k stars 338 forks source link

Telemetry issue #1034

Closed thumDer closed 4 years ago

thumDer commented 4 years ago

Describe the bug Telemetry server reports Invalid revit build number for Command Executed events. All other enabled events work fine and sent to db. We are using mongodb without https in LAN. It is the same for multiple Revit versions (2018, 2019, 2020)

eirannejad commented 4 years ago

Which version of pyRevit are you using?

thumDer commented 4 years ago

Sorry, I forgot to mention, it is 4.8.2, here is the environment:

==> Registered Clones (full git repos)
dev | Branch: "develop" | Version: "4.8.2:6fa0404" | Path: "C:\pyRevit\git\dev"
==> Registered Clones (deployed from archive/image)
main | Deploy: "base" | Branch: "master" | Version: "4.8.2" | Path: "C:\pyRevit\main"
==> Attachments
main | Product: "2021 First Customer Ship" | Engine: 277 | Path: "C:\pyRevit\main" | Manifest: "C:\ProgramData\Autodesk\Revit\Addins\2021\pyRevit.addin"
main | Product: "2020.2.2 (Full Install)" | Engine: 277 | Path: "C:\pyRevit\main" | Manifest: "C:\ProgramData\Autodesk\Revit\Addins\2020\pyRevit.addin"
main | Product: "2019.2.1" | Engine: 277 | Path: "C:\pyRevit\main" | Manifest: "C:\ProgramData\Autodesk\Revit\Addins\2019\pyRevit.addin"
main | Product: "2018.3.3 Security Fix" | Engine: 277 | Path: "C:\pyRevit\main" | Manifest: "C:\ProgramData\Autodesk\Revit\Addins\2018\pyRevit.addin"
==> Installed Extensions
pyNexTools | Type: Unknown | Repo: "" | Installed: "\\inex-fs-1\RVT\Revit_Library\General\pyRevit\Extensions\pyNexTools.extension"
==> Default Extension Search Path
C:\Users\tamas.deri\AppData\Roaming\pyRevit\Extensions
==> Extension Search Paths
\\inex-fs-1\RVT\Revit_Library\General\pyRevit\Extensions
==> Extension Sources - Default
https://github.com/eirannejad/pyRevit/raw/master/extensions/extensions.json
==> Extension Sources - Additional
==> Installed Revits
2021 First Customer Ship | Version: 21.0.0.383 | Build: 20200220_1100(x64) | Language: 1033 | Path: "C:\Program Files\Autodesk\Revit 2021"
2020.2.2 (Full Install) | Version: 20.2.11.3 | Build: 20200206_0915(x64) | Language: 1033 | Path: "C:\Program Files\Autodesk\Revit 2020"
2019.2.1 | Version: 19.2.10.7 | Build: 20190225_1515(x64) | Language: 1033 | Path: "C:\Program Files\Autodesk\Revit 2019"
2018.3.3 Security Fix | Version: 18.3.3.18 | Build: 20190510_1515(x64) | Language: 1033 | Path: "C:\Program Files\Autodesk\Revit 2018"
==> Running Revit Instances
PID: 11916 | 2019.2.1 | Version: 19.2.10.7 | Build: 20190225_1515(x64) | Language: 0 | Path: "C:\Program Files\Autodesk\Revit 2019"
PID: 36652 | 2019.2.1 | Version: 19.2.10.7 | Build: 20190225_1515(x64) | Language: 0 | Path: "C:\Program Files\Autodesk\Revit 2019"
PID: 31116 | 2018.3.3 Security Fix | Version: 18.3.3.18 | Build: 20190510_1515(x64) | Language: 0 | Path: "C:\Program Files\Autodesk\Revit 2018"
==> User Environment
Microsoft Windows 10 [Version 10.0.19041]
Executing User: IN-EX\tamas.deri
Active User:
Admin Access: No
%APPDATA%: "C:\Users\tamas.deri\AppData\Roaming"
Latest Installed .Net Framework: 4.8
Installed .Net Target Packs: v3.5 v4.0 v4.5 v4.5.1 v4.5.2 v4.6 v4.6.1 v4.7 v4.7.1 v4.7.2 v4.X
Installed .Net-Core Target Packs: v3.1.401
pyRevit CLI 4.8.2.0
eirannejad commented 4 years ago

Okay would you mind running the telemetry server with --debug --trace options and look at the dumps? I want to see what kind of build number is being sent to the server that is causing the invalidation

thumDer commented 4 years ago

yeah sure, it is below, but unfortunately i cannot see what build number is being sent

λ pyrevit-telemetryserver "mongodb://user:pass@172.20.1.35:27017/pyrevit" --scripts="scripts" --events="events" --port=8090 --debug --trace
2020/10/15 21:53:15 &{pyrevit-telemetryserver 0.19 0xc000006200 mongodb://user:pass@172.20.1.35:27017/pyrevit scripts events 8090 false true true}
2020/10/15 21:53:15 --debug=true
2020/10/15 21:53:15 --trace=true
2020/10/15 21:53:15 <db_uri>=mongodb://user:pass@172.20.1.35:27017/pyrevit
2020/10/15 21:53:15 --scripts=scripts
2020/10/15 21:53:15 --events=events
2020/10/15 21:53:15 --port=8090
2020/10/15 21:53:15 --https=false
Server listening on 8090...
2020/10/15 21:53:50 grabbing db name from connection string
2020/10/15 21:53:50 opening mongodb session
2020/10/15 21:53:50 getting mongodb version
2020/10/15 21:53:50 {"status":"pass","version":"0.19","output":"","serviceid":"36e27403-5413-4097-8d1c-f71fd359bde8","checks":{"mongodb":{"status":"pass","version":"4.4.1","output":""}}}
[ Invalid revit build number ] 2020-10-15T21:54:20.4173+02:00 [journal-command-exec] "IN-EX\\tamas.deri" @  doc="Project1" @
2020/10/15 21:54:20 vaidation error: Invalid revit build number
[ Invalid revit build number ] 2020-10-15T21:54:20.4941+02:00 [journal-command-exec] "IN-EX\\tamas.deri" @  doc="Project1" @
2020/10/15 21:54:20 vaidation error: Invalid revit build number
[ Invalid revit build number ] 2020-10-15T21:54:20.5060+02:00 [journal-command-exec] "IN-EX\\tamas.deri" @  doc="Project1" @
2020/10/15 21:54:20 vaidation error: Invalid revit build number
[ Invalid revit build number ] 2020-10-15T21:54:20.5200+02:00 [journal-command-exec] "IN-EX\\tamas.deri" @  doc="Project1" @
2020/10/15 21:54:20 vaidation error: Invalid revit build number
[ Invalid revit build number ] 2020-10-15T21:54:20.6810+02:00 [journal-command-exec] "IN-EX\\tamas.deri" @  doc="Project1" @
2020/10/15 21:54:20 vaidation error: Invalid revit build number
[ Invalid revit build number ] 2020-10-15T21:54:55.3935+02:00 [journal-command-exec] "IN-EX\\tamas.deri" @  doc="Project1" @
2020/10/15 21:54:55 vaidation error: Invalid revit build number
[ Invalid revit build number ] 2020-10-15T21:54:55.4214+02:00 [journal-command-exec] "IN-EX\\tamas.deri" @  doc="Project1" @
2020/10/15 21:54:55 vaidation error: Invalid revit build number
[ Invalid revit build number ] 2020-10-15T21:54:55.4384+02:00 [journal-command-exec] "IN-EX\\tamas.deri" @  doc="Project1" @
2020/10/15 21:54:55 vaidation error: Invalid revit build number
[ Invalid revit build number ] 2020-10-15T21:54:58.9163+02:00 [journal-command-exec] "IN-EX\\tamas.deri" @  doc="Project1" @
2020/10/15 21:54:58 vaidation error: Invalid revit build number
[ Invalid revit build number ] 2020-10-15T21:54:58.8974+02:00 [journal-command-exec] "IN-EX\\tamas.deri" @  doc="Project1" @
2020/10/15 21:54:58 vaidation error: Invalid revit build number
[ Invalid revit build number ] 2020-10-15T21:54:58.9273+02:00 [journal-command-exec] "IN-EX\\tamas.deri" @  doc="Project1" @
2020/10/15 21:54:58 vaidation error: Invalid revit build number
eirannejad commented 4 years ago

Fixed and will be published with next release