* adjust tooltip position
* fix crosshair snap
* allow clicking the correct datapoint
* optimize InsightTooltip
* fix no background colors in bar value chart
* fix positioning for bar value chart
* fix display on bar value charts with breakdown
* use custom chart.js
* add slight animation to tooltip position
* use posthog chartjs with "nearestX" mode
* update to a unborked @posthog/chart.js
Co-authored-by: Marius Andra <marius.andra@gmail.com>
* 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>
* allow passing project api key to api/feature_flag
* remove log
* handle GET requests appropriately
* add special handling
* nicer GET check
* remove special handling at routing level
* change get to post api
* tests
* fixed bug
* isort
* make funnels endpoint backwards compatible, add test to check this
* descriptive comment
* revert funnelLogic to current
* revert code removed in error
Co-authored-by: Alex Kim <alexkim@Alexs-MacBook-Pro-2.local>
Co-authored-by: Marius Andra <marius.andra@gmail.com>
We're hosting gunicorn behind an ELB with idle timeout of 120 seconds.
I think this is leading to sporatic 504 errors:
https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/ts-elb-error-message.html
> HTTP 504: Gateway timeout
> Cause 2: Registered instances closing the connection to Elastic Load Balancing.
> Solution 2: Enable keep-alive settings on your EC2 instances and make sure that the keep-alive timeout is greater than the idle timeout settings of your load balancer.
Related reading: https://serverfault.com/questions/782022/keepalive-setting-for-gunicorn-behind-elb-without-nginx
Not 100% this is appropriate for setups without ELB but let's deploy,
see if it makes a dent on monitoring and then move appropriately (e.g.
env variable this)
* add migration
* add fields
* remove comment
* change to is_deleted
* Update migration to work
* Update tests
* initial functions
* fix params
* add migration
* add named param
* working test
* update person prop and cohort tests
* use var
* move sql and fstring
* remove get inside django signal
* just create the table
* add replication logic
* add param
* change replacing name
* refactor and add event based cohorts
* add type
* add to model
* add test for event_id
* move sql
* add sql
* make sure actions work too and add test
* add ability to create cohort by event count
* glob match cypress cache
* fix type
* fix type
* refactor and add datetime support
* fix ordering issue in test
* add timestamp test
* fix type
* fix more types
* use var resolution
* add operators
* add necessary filter and test
* add call for calculating cohort on create
* add triggers to oncreate and onupdate
* breakup test and remove repeated subquery
Co-authored-by: Karl-Aksel Puulmann <oxymaccy@gmail.com>
Co-authored-by: Michael Matloka <dev@twixes.com>
