As-is this default hurts local dev - one more setting you need to
export. Let's keep the setup simple instead.
Also the new default would have broken helm chart and production
when updating with new migrations - the cluster name there is `posthog`
for both it seems.
Let's force other deploys to be explicit instead.
* Make DDLs more friendly towards running on a cluster
* Use primary CLICKHOUSE host for migrations and DDL
* loose ends on person kafka create
* posthog -> cluster typo
* add cluster to KAFKA create for plugin logs
* Feed the type monster
* clusterfy local clickhouse
* test docker-compose backed github action
* run just clickhouse and postgres from docker-compose
* move option to between up and <services>
* posthog all the things
* suggest tests run on cluster
* posthog cluster for ci
* use deploy path for docker-compose
* fix for a clickhouse bug 🐛
* complete CH bug fixes
* 5439 the github actions pg configs
* remove CLICKHOUSE_DATABASE (handled automatically)
* update DATABASE_URL for code quality checks
* Missed a few DDLs on Person
* 5439 -> 5432 to please the people
* cleanup persons and use f strings <3 f strings
* remove auto parens
* Update requirements to use our fork of infi.clickhouse_orm
* fix person.py formatting
* Include boilerplate macros for a cluster
* Solve ospath issue
* try separate cypress cache
* Separate install
* ls
* try
* Try to put everything in same cache
* Remove cypress plugin snapshot
* fix cohorts and funnels
* Remove commented out test
* Update VERSION
* Don't run the automerge job on forks
* Revert "Update VERSION"
This reverts commit dc37f20133.
* Change automerge condition
* Change automerge condition a bit more
* Try scrolling
* Scroll by more
* Stop GitHub complaining about no jobs ran in a workflow
* Search for a different event name
* Try a different operator
* Don't default branch push jobs on forks
* Move clicks around
Co-authored-by: PostHog Bot <hey@posthog.com>
* Send info on insights query timing + route to posthog
This will help with determining the root cause of our problems
* Capture information on "timeouts" correctly
previously every error on insights was reported as a timeout.
* WIP
* Solve typing issues within insightslogic
* WIP part 2
* Add graphs for insight load times
* Add tests for new routes
* PR review iteration
* Make instance_status POST available for all
* Do some cache busting
* add "put_json_into_zip_archive" util
* add semantic version package
* compare posthog version requirement string in plugin.json if present
* Clarify posthogVersion error messages
* Don't check posthogVersion on Cloud
* Clarify error messages better
* Split test_create_plugin_version_ranges into multiple tests
* Add Cloud test and fix the rest
* Make mypy happy
* Update ci-backend.yml
* Fix typing
* Remove broad restore-keys
* Revert "Remove broad restore-keys"
This reverts commit b720e1e1cf.
* Attempt to make cached pip actually work
* Always run package installs even if cache hit just to be sure
* Avoid pytest from PATH
* Avoid PATH in Python CI altogether
* Roll back general CI changes
Co-authored-by: Michael Matloka <dev@twixes.com>
* Chunk session recording events
Closes https://github.com/PostHog/posthog/issues/3632 and replaces https://github.com/PostHog/posthog/pull/3566/files
This should make it possible to ingest large full snapshot events
Base64 is used to compress the data for serialization purposes.
pytest.mock is used for clean patching methods
* Mock time.time for py3.7 compatibility
* Group captured $snapshot events by $session_id
* Don't chunk already chunked payloads
* Compile requirements-dev.txt with latest pip-tools
* Install pytest
* Avoid picking up factories as tests
* New runner
* Always set TEST env variable running tests
Some of our tests rely on it.
* Remove repetition
* Fix a broken test
* Cut down noise from bin/tests
* Rename test factory
* Fix stickiness filter
* Skip a broken test
This has been broken since numpy removal PR. Sadly tests were not
running for this submodule
* Fix import on ee
* Run ee tests properly
The django_db_setup fixture will be automatically run when running ee/
module tests.
* Make tests run on CI
* Include REDIS_URL, fix cloud
* Set TEST env variable
* Hack cloud tests to work
* Attempt at workflow fix
* Import Person model when running ee tests
This module implicitly adds hooks, so this is needed when running tests
* Respect reuse-db for clickhouse
* Add custom markers to avoid warnings
* pytest: use ch test database always
Accidentally wiped by ch setup a few times without this. Oops
* Remove repetition in tests
* Pytest: Always run migrations
Testing a state cleanup fix
* Use same DB in conftest and main code
* Pytest: autoset TEST setting without env variable
* fix broken test
Co-authored-by: eric <eeoneric@gmail.com>
* Add AUTO_LOG_IN environment variable
This will be used when running tests on CI, setting up demo instances
and with cypress vcr
* Auto log in in review apps, e2e tests
This will speed up tests/reviewing significantly
* Rename AUTO_LOG_IN to AUTO_LOGIN
Co-authored-by: Michael Matloka <dev@twixes.com>
* WIP: get cypress something doing
* Get a test running
* Get css loading, stub posthog
* Move helpers to separate file
* Givens > given2
It plays nicer with beforeEach
* Test for session filters
* Test date navigation
* Test filtering
* Try keep old tests running
* Try get tests running under CI
* Prettify fixtures
* Cleanup, use cypress 6
* Add yarn build
* Fix e2e cypress tests
* given2 => givens
* Rename `frontend-test-runner` to `e2e-test-runner`
* Fix cypress test
* Add webpack-preprocessor as a devDependency
* Improve freezing time
* Make css inclusions automatic for component tests
