Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Analytics app doesn't display aggregate data with SQLite backend #182

Closed
1 task done
Gotfrid opened this issue Jun 17, 2024 · 0 comments · Fixed by #183
Closed
1 task done

[Bug]: Analytics app doesn't display aggregate data with SQLite backend #182

Gotfrid opened this issue Jun 17, 2024 · 0 comments · Fixed by #183
Labels

Comments

@Gotfrid
Copy link
Member

Gotfrid commented Jun 17, 2024

Guidelines

  • 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

  1. Copy existing example with Postgres from inst/examples/postgresql
  2. Modify the code so that shiny.telemetry uses SQLite backend
  3. Run the app, produce a few events
  4. Run analytics app
  5. Confirm that data was collected - particularly by exploring a user session.
  6. 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:
Screenshot 2024-06-17 at 16 28 24

However data is not aggregated properly on "Activity stats"
Screenshot 2024-06-17 at 16 28 27

Additional Information

I know that the problem is related to how timestamp is stored in SQLite and how its parsed by lubridate. See:

sqlite_ts <- 1718635448
lubridate::as_date(sqlite_ts)
# [1] "4707434-01-14"

Please take a look at the proposed solution in #183.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant