Skip to content

Monthly meeting notes

Jump to bottom Edit New page
Guido Petri edited this page Nov 25, 2023 · 8 revisions

Next meeting date: 2024-01-27, 8am EST / 2pm CET / 11:59pm AEDT

Time and date link: link

2023-11-25

Members present: Deecay, Sid

Note: We'll skip the 2023-12-30 meeting due to holidays, and we'll meet again on 2024-01-27.

Recent topics

Arm64 build

Recent changes

Security

  • werkzeug needs to be updated, but we need to update flask together with it fixed with werkzeug 2.3.8

Dev changes

  • small typo fix in CI -> faster builds

Backend changes

  • saml setup is now following guidelines
  • rockset runner allows for multiple/specific virtual instances
  • e6data query runner

Frontend changes

  • trino displays catalog information
  • fork-able dashboards
  • numeral/numbro switch - should we revert?

What do we need to do for our first official Redash Community release?

  • we both agree that we should maybe just do a release and if necessary, create patches to fix broken query runners/functionality
  • very little testing (especially on frontend) so we understand the view of wanting to test things out thoroughly before releasing
  • probably better to talk as a larger group

Project direction + organization

  • Sid might just set up github projects to try it out
  • also probably better to talk as a larger group

How is everyone doing backups currently (for automated upgrades/migrations)?

  • both of us are using pg_dump/pg_dumpall

2023-10-28

Members present: Justin, Deecay, Eric, Sid

Recent Topics

Docker preview image

  • seems to be catching some problems
  • how many people are using this? do we need to ask Arik for stats?
  • sub-accounts on redash dockerhub to use a "shared" login instead of Arik's?
  • Justin has some experience via pgautoupgrade
  • difference between pgautoupgrade and redash: officially sponsored OSS
  • date-tags?
    • maybe leave for later, maybe first time someone asks for a stable version?
    • currently has a permission problem, GHA currently works on a separate repo but we need to test on redash repo to see if permissions problem is still there

Ubuntu 22 upgrade

  • Eric's testing is all on ubuntu 22 + py3.10
  • only one file needs a patch: sqlalchemy-utils package, observer.py. which currently breaks redash on an existing db
  • binaries from dockerfile (mssql/databricks)
    • mssql should be ok, according to Justin (also is debian 12 so Sid agrees)
    • (databricks could be used as a pip dependency?) (do we need it?)
      • could open a poll in discussions?
  • should we move dev to this? maybe in ~3-6 months?
    • ubuntu 20 has support until april 2025, but py3.8 (bundled with ubuntu 20) only until october 2024
    • update wiki, docs
    • upgrade path?

Automatic migrations for redash

  • when someone boots up a newer version of redash, the application should migrate the database automatically
    • alembic? migration is already set up, but we need to run it manually
      • we should make sure the migration script is a no-op when no migrations available
      • ask Arik why it wasn't set up this way? maybe incompatibility with SaaS environment or something similar?

Security

  • Justin hasn't looked at security things in the past ~month, probably not again for next 6-8 weeks
  • security advisories - need to be closed to disappear from list?
    • we should read the docs lol
  • Eric to draft something on a current security problem
  • to discuss: fix/organize maintainer access (per-repo, for whole org, teams vs individuals?)
    • touchpoint from Arik: he seems to be the only one to add people to the whole org
      • might have private repos that we shouldn't be able to see (because of databricks ownership)

Recent changes

Development changes

  • removed Datree badge
    • appeared to be some kind of code analysis thing, but closed now
  • Dockerfile moved to debian 12 (bookworm)
  • arm64 build takes too long on CI, we reverted
    • might have to add arm runner for this
      • Justin has an M1 Mac Mini, but we could also provision a raspberry pi
  • docker compose version was changed
    • Eric already updated docs for this (install docker-compose-v2, could maybe install both v1 and v2?)

Backend changes

  • yandex metrica retries on 429
  • JSON runner now has pagination
    • this uses 2 pretty common forms of pagination, according to PR author, and is flexible/configurable
    • Sid doesn't think we updated the docs
  • mysql runner has new connection options

Frontend changes

  • bigger text area for query description
  • BQ schema now shows up on schema
  • counter font size changed
    • still in progress
    • find another example in another piece of software?
      • Deecay mentioned Plotly has similar-ish issues and they haven't really solved it
    • user needs to have some control
    • decision: we should revert for now and make a bigger PR that allows choices
    • Eric to continue work on this topic

Future topics for the monthly meetings

  • should we open a patreon for redash?
  • updating end user docs
  • project direction + organization
    • use github projects?

2023-09-30

Members present: Sid, Tak, Eric, Justin, deecay

Introductions

  • Sid:
    • based close to Kansas City
    • works in sports analytics
    • got to know Redash through hobby chess data work (~2019), now own exercise data
  • Eric:
    • Starfish Storage - analysis on filesystem data to minimize cost
    • up to ~30tb databases
    • Redash is a way for customers to look at their data
    • BSD license is critical - Redash is patched + passed through to clients
    • system to capture a PDF of dashboards and email to users
      • headless chrome
      • optionally attach CSVs
    • Metabase might work, but AGPL-3 doesn't work as a license
    • Redash lets you do whatever you want with the db (creating functions, temp tables, operators)
    • background mostly in Postgres
    • in upstate NY
  • Tak:
    • used to be a maintainer!
    • also used to organize a meetup in Japan: https://redash-meetup.connpass.com
    • 3-6y ago, used to work for advertising agency in Japan
    • doesn't work with Redash recently
  • Justin:
    • Now based in Australia (Brisbane)
    • Initially started using Redash for making charts, for DB Browser for SQLite project (sqlitebrowser.org)
    • Worked for Redash for a few months when between contracts ~2 years ago
    • Skills wise, is infra-focused. When Redash announced their shut down, he set up Newdash.io and inherited some of the customers who needed hosting
    • Mostly focused on security issues in Redash, as well as operational pain points like the excessive memory usage
    • Has an M1 Mac Mini (via DB Browser for SQLite project) that is useful for doing Apple Silicon builds on
  • deecay:
    • from Japan (Tokyo)
    • using Redash since ~2018-2019, long-time committer/maintainer

Community

Docker preview image

  • missing docker password
  • can't push images to Redash docker hub
  • if people are using the updates regularly, then problems we introduce will get caught
  • CI is also incorrect - not building when it's supposed to, but less of a blocker

Poetry setup

  • requires a new dependency: poetry itself
  • don't have to manage requirements.txt files
  • recursive dependency version pinning

Ubuntu 22

Future topics for these meetings

  • project direction for the future
Add a custom footer
Add a custom sidebar
Clone this wiki locally