You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I agree to follow this project's Contributing Guidelines.
Project Version
0.2.0, github:main
Platform and OS Version
macOS 14.5, Ubuntu 22.04.4 LTS (docker container)
Existing Issues
No response
What happened?
When using SQLite as a backend to store telemetry data, analytics app that comes with shiny.telemetry won't show values correctly - all aggregates show 0 counts.
Steps to reproduce
Copy existing example with Postgres from inst/examples/postgresql
Modify the code so that shiny.telemetry uses SQLite backend
Run the app, produce a few events
Run analytics app
Confirm that data was collected - particularly by exploring a user session.
Confirm that "Activity Stats" page displays "Amount: 0" on the plotly chart
Expected behavior
Expected to see correct counts for the user inputs.
Attachments
No response
Screenshots or Videos
Data is available when exploring a particular session:
However data is not aggregated properly on "Activity stats"
Additional Information
I know that the problem is related to how timestamp is stored in SQLite and how its parsed by lubridate. See:
Guidelines
Project Version
0.2.0, github:main
Platform and OS Version
macOS 14.5, Ubuntu 22.04.4 LTS (docker container)
Existing Issues
No response
What happened?
When using SQLite as a backend to store telemetry data, analytics app that comes with shiny.telemetry won't show values correctly - all aggregates show 0 counts.
Steps to reproduce
Expected behavior
Expected to see correct counts for the user inputs.
Attachments
No response
Screenshots or Videos
Data is available when exploring a particular session:
However data is not aggregated properly on "Activity stats"
Additional Information
I know that the problem is related to how timestamp is stored in SQLite and how its parsed by
lubridate
. See:Please take a look at the proposed solution in #183.
The text was updated successfully, but these errors were encountered: