status
stringclasses 1
value | repo_name
stringclasses 13
values | repo_url
stringclasses 13
values | issue_id
int64 1
104k
| updated_files
stringlengths 11
1.76k
| title
stringlengths 4
369
| body
stringlengths 0
254k
⌀ | issue_url
stringlengths 38
55
| pull_url
stringlengths 38
53
| before_fix_sha
stringlengths 40
40
| after_fix_sha
stringlengths 40
40
| report_datetime
unknown | language
stringclasses 5
values | commit_datetime
unknown |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
closed | PostHog/posthog | https://github.com/PostHog/posthog | 19,895 | [".dockerignore"] | Unable to build with docker | ## Bug description
We used to build PostHog using Docker. However since this [commit](https://github.com/PostHog/posthog/commit/d6e15ccb0610b80db4b20d31854b4daf878a7b4a) the project cannot be built - keeps throwing error:
```
=> ERROR [frontend-build 4/10] COPY patches/ patches/ 0.0s
------
> [frontend-build 4/10] COPY patches/ patches/:
------
failed to compute cache key: failed to calculate checksum of ref 0b8a30b3-d2e9-481b-9c93-06b6eea5c34e::tick1p0qn9epjaeymqgrdbbdq: "/patches": not found
Exited with code exit status 1
```
## How to reproduce
1. execute docker build -t image .
## Environment
- [ ] PostHog self-hosted with `docker`, version/commit: [current](https://github.com/PostHog/posthog/commit/a9f9a2db2ba65bcf02374f51468ac921dc1c681d)
| https://github.com/PostHog/posthog/issues/19895 | https://github.com/PostHog/posthog/pull/19896 | 4a1b0c8d9cc31d1052a76da77e34401c492de261 | 1ee5df84ad24a43ab0c8e21971ad9f346a966d78 | "2024-01-22T08:45:56Z" | python | "2024-01-22T10:03:21Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 19,867 | ["frontend/src/lib/components/PropertyFilters/components/FilterRow.scss"] | Date selector is only partially visible | ## Bug description
## How to reproduce
1. Try to filter any time field
2. Try to select the date
## Additional context
https://posthoghelp.zendesk.com/agent/tickets/9539
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/19867 | https://github.com/PostHog/posthog/pull/19972 | 35a3c45ee9b23c683f45df68a2a917cc7c9cc1dd | c59f04ba84a5839a1f1c236998fb3ca258f1e8cf | "2024-01-19T14:12:20Z" | python | "2024-01-25T22:42:08Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 19,350 | ["posthog/api/authentication.py"] | Workaround Needed for Cookie Validation Issue During Django Upgrade | We've encountered an issue related to two-factor authentication cookie validation after a major Django version upgrade, as detailed in issue [#686](https://github.com/jazzband/django-two-factor-auth/issues/686). This issue arises due to the change in user password hashes when Django's hash iteration count is updated in a new version, leading to a mismatch in the two-factor authentication cookies' validation.
We can for now implement a workaround. This involves catching the `BadSignature` exception raised during the cookie validation process when there's a mismatch in the hashes. This situation occurs after upgrading Django, which causes the user's password hash to change, thereby invalidating the existing two-factor authentication cookies.
This issue is critical for us to upgrade our Django version without disrupting the user experience of people coming back and having a 2FA cookie.
| https://github.com/PostHog/posthog/issues/19350 | https://github.com/PostHog/posthog/pull/19351 | fcb52364937ebf71bc91ac0db46c4714e5b1a199 | 87fdf3f2350b76bcbcfe47639a694c95cb371631 | "2023-12-15T11:21:49Z" | python | "2023-12-20T08:23:01Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 17,890 | ["frontend/src/queries/nodes/DataTable/DataTableExport.tsx"] | Static cohort exports don't export person properties | ## Bug description
When I create a static cohort, and try to export 'current columns', the properties.email field is empty, when it shouldn't be.
Need to figure out why exports aren't gathering all properties for persons here.
| https://github.com/PostHog/posthog/issues/17890 | https://github.com/PostHog/posthog/pull/18928 | 8865be443ef0581607c4f778b27d8f3a4547012a | 4e3809a853d5ac7a63e467ed7a8095cb204a1f5f | "2023-10-10T13:30:51Z" | python | "2023-12-21T12:59:18Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 17,841 | ["cypress/e2e/early-access-management.cy.ts", "frontend/src/scenes/early-access-features/EarlyAccessFeature.tsx", "frontend/src/scenes/early-access-features/EarlyAccessFeatures.tsx", "frontend/src/scenes/early-access-features/earlyAccessFeatureLogic.ts"] | Early Access Management issues | ## Bug description
1. Early access management says its in beta on the page but not the sidebar (I get that there probably isn't room).
2. It is slightly jarring for the button to be "New public beta" as there is no mention of beta elsewhere
3. The empty state button is "Create feature" which it is inconsistent with the public beta button (but I think it's better).
| https://github.com/PostHog/posthog/issues/17841 | https://github.com/PostHog/posthog/pull/17857 | dd4374857a283492e9b6c8cd114af091e9074858 | 45d5794f0339dab7dcaf9aa19bd47e4ff9b6cf4d | "2023-10-06T10:56:02Z" | python | "2023-10-12T14:43:06Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 17,793 | ["frontend/src/scenes/organization/Settings/InviteModal.tsx", "frontend/src/scenes/organization/Settings/Invites.tsx"] | Expired invite link isn't actionable? | When an invite has expired, it looks like you should be able to click it to recreate the invite. But it appears to just be text. Should either be:
- An actual link that deletes and recreates the invite
- Different text that just says _Invite expired_
<img width="642" alt="image" src="https://github.com/PostHog/posthog/assets/154479/d85cb1ca-aec7-443b-9060-e3260581f8fe">
| https://github.com/PostHog/posthog/issues/17793 | https://github.com/PostHog/posthog/pull/17862 | f247c674b4570c48d9ad68870bc7dda6e104d6ce | eb8071cb6ee2fc76b7d2e188483080e5e4f0d4cf | "2023-10-04T22:33:55Z" | python | "2023-10-10T14:35:59Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 17,254 | ["frontend/src/lib/components/PropertyFilters/components/PropertyValue.tsx", "frontend/src/lib/lemon-ui/LemonSelectMultiple/LemonSelectMultiple.tsx"] | Cohorts property id filter copy and pasting values bug | ## Bug description
*Please describe.*
*If this affects the front-end, screenshots would be of great help.*
ex: We want to create a cohort based on certain organization IDs. When we copy and paste that list into the property filter in cohort creation, the values paste properly in the field, but the cohort persons return based on the first ID only.
https://posthoghelp.zendesk.com/agent/tickets/5430
*If you are on PostHog Cloud it would be really valuable if you can share any links where the problem occurs. This speeds up our ability to troubleshoot tremendously.*
## How to reproduce
1.
2.
3.
## Environment
- [ ] PostHog Cloud US, project ID: [please provide from https://app.posthog.com/project/settings#project-id]
- [ ] PostHog Cloud EU, project ID: [please provide from https://eu.posthog.com/project/settings#project-id]
- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]
- [ ] PostHog self-hosted with Kubernetes (deprecated, see ["Sunsetting Kubernetes support"](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/17254 | https://github.com/PostHog/posthog/pull/17303 | 2ce6105c01898e7688a7c3e12f66eeb132a9552b | b9cfb93d322cfbc69cab8afbb99084add0d881e4 | "2023-08-30T19:43:41Z" | python | "2023-09-13T10:31:49Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 17,250 | ["frontend/src/lib/components/DateFilter/DateFilter.tsx", "frontend/src/lib/components/DateFilter/dateFilterLogic.ts", "frontend/src/lib/lemon-ui/LemonCalendarRange/LemonCalendarRange.test.tsx", "frontend/src/lib/lemon-ui/LemonCalendarRange/LemonCalendarRange.tsx", "frontend/src/lib/lemon-ui/LemonCalendarRange/LemonCalendarRangeInline.tsx", "mypy-baseline.txt", "posthog/hogql_queries/utils/query_date_range.py"] | Selecting the same day in "custom fixed date range" will show no events in event explorer | ## Bug description
When selecting the same start and end date as the "custom fixed date range", the event explorer will show not events, because the query looks for events which are:
- greater than `toDateTime64('2023-08-23 00:00:00.000000', 6, 'UTC')`
- less than `toDateTime64('2023-08-23 00:00:00.000000', 6, 'UTC')`
I would expect to see all events from the `2023-08-23`
## How to reproduce
1. Open event explorer
2. Select "custom fixed date range"
3. Select same start and ending day
A solution here would be to not allow the same day to be selected.
## Additional context
related ticket: https://posthoghelp.zendesk.com/agent/tickets/5458
clickhouse query: [here](http://metabase-prod-us/question#eyJkYXRhc2V0X3F1ZXJ5Ijp7InR5cGUiOiJuYXRpdmUiLCJuYXRpdmUiOnsicXVlcnkiOiJTRUxFQ1QgdHVwbGUoZXZlbnRzLnV1aWQsIGV2ZW50cy5ldmVudCwgZXZlbnRzLnByb3BlcnRpZXMsIHRvVGltZVpvbmUoZXZlbnRzLnRpbWVzdGFtcCwgJ1VUQycpLCBldmVudHMudGVhbV9pZCwgZXZlbnRzLmRpc3RpbmN0X2lkLCBldmVudHMuZWxlbWVudHNfY2hhaW4sIHRvVGltZVpvbmUoZXZlbnRzLmNyZWF0ZWRfYXQsICdVVEMnKSksXG4gICAgICAgZXZlbnRzLmV2ZW50LFxuICAgICAgIGV2ZW50cy5kaXN0aW5jdF9pZCxcbiAgICAgICByZXBsYWNlUmVnZXhwQWxsKG51bGxJZihudWxsSWYoSlNPTkV4dHJhY3RSYXcoZXZlbnRzLnByb3BlcnRpZXMsICdhcnRpY2xlSUQnKSwgJycpLCAnbnVsbCcpLCAnXlwifFwiJCcsICcnKSxcbiAgICAgICByZXBsYWNlUmVnZXhwQWxsKG51bGxJZihudWxsSWYoSlNPTkV4dHJhY3RSYXcoZXZlbnRzLnByb3BlcnRpZXMsICdrYklEJyksICcnKSwgJ251bGwnKSwgJ15cInxcIiQnLCAnJyksXG4gICAgICAgbnVsbElmKG51bGxJZihldmVudHMuYG1hdF8kbGliYCwgJycpLCAnbnVsbCcpLFxuICAgICAgIHRvVGltZVpvbmUoZXZlbnRzLnRpbWVzdGFtcCwgJ1VUQycpXG5GUk9NIGV2ZW50c1xuV0hFUkUgYW5kKGVxdWFscyhldmVudHMudGVhbV9pZCwgMjAyOCksIGlmTnVsbChsZXNzKHRvVGltZVpvbmUoZXZlbnRzLnRpbWVzdGFtcCwgJ1VUQycpLCB0b0RhdGVUaW1lNjQoJzIwMjMtMDgtMjMgMDA6MDA6MDAuMDAwMDAwJywgNiwgJ1VUQycpKSwgMCksIGlmTnVsbChncmVhdGVyKHRvVGltZVpvbmUoZXZlbnRzLnRpbWVzdGFtcCwgJ1VUQycpLCB0b0RhdGVUaW1lNjQoJzIwMjMtMDgtMjMgMDA6MDA6MDAuMDAwMDAwJywgNiwgJ1VUQycpKSwgMCkpXG5PUkRFUiBCWSB0b1RpbWVab25lKGV2ZW50cy50aW1lc3RhbXAsICdVVEMnKSBERVNDXG5MSU1JVCAxMDFcbk9GRlNFVCAwIFNFVFRJTkdTIHJlYWRvbmx5PTIsXG4gICAgICAgICAgICAgICAgICBtYXhfZXhlY3V0aW9uX3RpbWU9NjAsXG4gICAgICAgICAgICAgICAgICBhbGxvd19leHBlcmltZW50YWxfb2JqZWN0X3R5cGU9VHJ1ZSIsInRlbXBsYXRlLXRhZ3MiOnt9fSwiZGF0YWJhc2UiOjM2fSwiZGlzcGxheSI6InRhYmxlIiwicGFyYW1ldGVycyI6W10sInZpc3VhbGl6YXRpb25fc2V0dGluZ3MiOnt9fQ==)
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/17250 | https://github.com/PostHog/posthog/pull/20154 | cbf09b50ae8b23a154b64e1f2b511ca33fcbb47e | cf31c279758125066e14dfaa7297d314d70a9e97 | "2023-08-30T16:06:58Z" | python | "2024-02-07T08:36:38Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 16,986 | ["frontend/src/scenes/actions/actionEditLogic.tsx", "frontend/src/scenes/insights/insightSceneLogic.tsx"] | Errant confirmation dialog | ## Bug description
After saving an action, then clicking to any other tab in the product, there's a prompt to save changes, even though there aren't any changes to be saved.
<img width="458" alt="image" src="https://github.com/PostHog/posthog/assets/154479/c2bb73db-44ce-471e-90e5-49131657447d">
| https://github.com/PostHog/posthog/issues/16986 | https://github.com/PostHog/posthog/pull/16989 | 3c8b4cc0a59d444892796eb142fbddb3fa6758df | bd84ef779284736c9bdb1d658e771a10396eb2e5 | "2023-08-10T15:10:56Z" | python | "2023-08-10T17:07:43Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 15,412 | ["posthog/hogql/property.py", "posthog/hogql/test/test_property.py"] | CHQueryErrorTypeMismatch: Code: 53. | Sentry Issue: [POSTHOG-EU-3YC](https://posthog.sentry.io/issues/4121292376/?referrer=github_integration)
```
ServerException: Code: 53.
DB::Exception: Cannot convert string true to type UInt8: while executing 'FUNCTION equals(equals(replaceRegexpAll(JSONExtractRaw(properties, 'metadata.isApp'), '^"|"$', ''), 'true') : 30, 'true' : 16) -> equals(equals(replaceRegexpAll(JSONExtractRaw(properties, 'metadata.isApp'), '^"|"$', ''), 'true'), 'true') UInt8 : 31'. Stack trace:
0. DB::Exception::Exception(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, int, bool) @ 0x8e2df48 in /usr/bin/clickhouse
1. DB::Exception::Exception<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > >(int, fmt::v8::basic_format_string<char, fmt::v8::type_identity<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&>::type, fmt::v8::type_identity<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > >::type>, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >&&) @ 0xae40760 in /usr/bin/clickhouse
2. ? @ 0x11e833ac in /usr/bin/clickhouse
3. DB::FunctionComparison<DB::EqualsOp, DB::NameEquals>::executeImpl(std::__1::vector<DB::ColumnWithTypeAndName, std::__1::allocator<DB::ColumnWithTypeAndName> > const&, std::__1::shared_ptr<DB::IDataType const> const&, unsigned long) const @ 0xc621128 in /usr/bin/clickhouse
4. DB::IExecutableFunction::executeWithoutLowCardinalityColumns(std::__1::vector<DB::ColumnWithTypeAndName, std::__1::allocator<DB::ColumnWithTypeAndName> > const&, std::__1::shared_ptr<DB::IDataType const> const&, unsigned long, bool) const @ 0x10c99c9c in /usr/bin/clickhouse
5. DB::IExecutableFunction::executeWithoutSparseColumns(std::__1::vector<DB::ColumnWithTypeAndName, std::__1::allocator<DB::ColumnWithTypeAndName> > const&, std::__1::shared_ptr<DB::IDataType const> const&, unsigned long, bool) const @ 0x10c9a574 in /usr/bin/clickhouse
6. DB::IExecutableFunction::execute(std::__1::vector<DB::ColumnWithTypeAndName, std::__1::allocator<DB::ColumnWithTypeAndName> > const&, std::__1::shared_ptr<DB::IDataType const> const&, unsigned long, bool) const @ 0x10c9bb7c in /usr/bin/clickhouse
7. DB::ExpressionActions::execute(DB::Block&, unsigned long&, bool) const @ 0x117f49d8 in /usr/bin/clickhouse
8. DB::ExpressionActions::execute(DB::Block&, bool) const @ 0x117f5930 in /usr/bin/clickhouse
9. DB::ExpressionAnalysisResult::ExpressionAnalysisResult(DB::SelectQueryExpressionAnalyzer&, std::__1::shared_ptr<DB::StorageInMemoryMetadata const> const&, bool, bool, bool, std::__1::shared_ptr<DB::FilterDAGInfo> const&, std::__1::shared_ptr<DB::FilterDAGInfo> const&, DB::Block const&) @ 0x1186417c in /usr/bin/clickhouse
10. DB::InterpreterSelectQuery::getSampleBlockImpl() @ 0x11bb4000 in /usr/bin/clickhouse
11. ? @ 0x11bacdd8 in /usr/bin/clickhouse
12. DB::InterpreterSelectQuery::InterpreterSelectQuery(std::__1::shared_ptr<DB::IAST> const&, std::__1::shared_ptr<DB::Context> const&, std::__1::optional<DB::Pipe>, std::__1::shared_ptr<DB::IStorage> const&, DB::SelectQueryOptions const&, std::__1::vector<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > > const&, std::__1::shared_ptr<DB::StorageInMemoryMetadata const> const&, std::__1::shared_ptr<DB::PreparedSets>) @ 0x11ba84ec in /usr/bin/clickhouse
13. DB::InterpreterSelectWithUnionQuery::buildCurrentChildInterpreter(std::__1::shared_ptr<DB::IAST> const&, std::__1::vector<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > > const&) @ 0x11bee304 in /usr/bin/clickhouse
14. DB::InterpreterSelectWithUnionQuery::InterpreterSelectWithUnionQuery(std::__1::shared_ptr<DB::IAST> const&, std::__1::shared_ptr<DB::Context>, DB::SelectQueryOptions const&, std::__1::vector<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > > const&) @ 0x11bec654 in /usr/bin/clickhouse
15. DB::InterpreterFactory::get(std::__1::shared_ptr<DB::IAST>&, std::__1::shared_ptr<DB::Context>, DB::SelectQueryOptions const&) @ 0x11b5d12c in /usr/bin/clickhouse
16. ? @ 0x11e9e7bc in /usr/bin/clickhouse
17. DB::executeQuery(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::shared_ptr<DB::Context>, bool, DB::QueryProcessingStage::Enum) @ 0x11e9c59c in /usr/bin/clickhouse
18. DB::TCPHandler::runImpl() @ 0x12835ec4 in /usr/bin/clickhouse
19. DB::TCPHandler::run() @ 0x128480a4 in /usr/bin/clickhouse
20. Poco::Net::TCPServerConnection::start() @ 0x134653c0 in /usr/bin/clickhouse
21. Poco::Net::TCPServerDispatcher::run() @ 0x13466938 in /usr/bin/clickhouse
22. Poco::PooledThread::run() @ 0x1364f150 in /usr/bin/clickhouse
23. Poco::ThreadImpl::runnableEntry(void*) @ 0x1364cae4 in /usr/bin/clickhouse
24. start_thread @ 0x7624 in /usr/lib/aarch64-linux-gnu/libpthread-2.31.so
25. ? @ 0xd149c in /usr/lib/aarch64-linux-gnu/libc-2.31.so
(2 additional frame(s) were not displayed)
...
File "clickhouse_driver/client.py", line 491, in process_ordinary_query
return self.receive_result(with_column_types=with_column_types,
File "clickhouse_driver/client.py", line 151, in receive_result
return result.get_result()
File "clickhouse_driver/result.py", line 50, in get_result
for packet in self.packet_generator:
File "clickhouse_driver/client.py", line 167, in packet_generator
packet = self.receive_packet()
File "clickhouse_driver/client.py", line 184, in receive_packet
raise packet.exception
CHQueryErrorTypeMismatch: Code: 53.
DB::Exception: Cannot convert string true to type UInt8: while executing 'FUNCTION equals(equals(replaceRegexpAll(JSONExtractRaw(properties, 'metadata.isApp'), '^"|"$', ''), 'true') : 30, 'true' : 16) -> equals(equals(replaceRegexpAll(JSONExtractRaw(properties, 'metadata.isApp'), '^"|"$', ''), 'true'), 'true') UInt8 : 31'. Stack trace:
0. DB::Exception::Exception(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, int, bool) @ 0x8e2df48 in /usr/bin/clickhouse
1. DB::Exception::Exception<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > >(int, fmt::v8::basic_format_string<char, fmt::v8::type_identity<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&>::type, fmt::v8::type_identity<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > >::type>, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >&&) @ 0xae40760 in /usr/bin/clickhouse
2. ? @ 0x11e833ac in /usr/bin/clickhouse
3. DB::FunctionComparison<DB::EqualsOp, DB::NameEquals>::executeImpl(std::__1::vector<DB::ColumnWithTypeAndName, std::__1::allocator<DB::ColumnWithTypeAndName> > const&, std::__1::shared_ptr<DB::IDataType const> const&, unsigned long) const @ 0xc621128 in /usr/bin/clickhouse
4. DB::IExecutableFunction::executeWithoutLowCardinalityColumns(std::__1::vector<DB::ColumnWithTypeAndName, std::__1::allocator<DB::ColumnWithTypeAndName> > const&, std::__1::shared_ptr<DB::IDataType const> const&, unsigned long, bool) const @ 0x10c99c9c in /usr/bin/clickhouse
5. DB::IExecutableFunction::executeWithoutSparseColumns(std::__1::vector<DB::ColumnWithTypeAndName, std::__1::allocator<DB::ColumnWithTypeAndName> > const&, std::__1::shared_ptr<DB::IDataType const> const&, unsigned long, bool) const @ 0x10c9a574 in /usr/bin/clickhouse
6. DB::IExecutableFunction::execute(std::__1::vector<DB::ColumnWithTypeAndName, std::__1::allocator<DB::ColumnWithTypeAndName> > const&, std::__1::shared_ptr<DB::IDataType const> const&, unsigned long, bool) const @ 0x10c9bb7c in /usr/bin/clickhouse
7. DB::ExpressionActions::execute(DB::Block&, unsigned long&, bool) const @ 0x117f49d8 in /usr/bin/clickhouse
8. DB::ExpressionActions::execute(DB::Block&, bool) const @ 0x117f5930 in /usr/bin/clickhouse
9. DB::ExpressionAnalysisResult::ExpressionAnalysisResult(DB::SelectQueryExpressionAnalyzer&, std::__1::shared_ptr<DB::StorageInMemoryMetadata const> const&, bool, bool, bool, std::__1::shared_ptr<DB::FilterDAGInfo> const&, std::__1::shared_ptr<DB::FilterDAGInfo> const&, DB::Block const&) @ 0x1186417c in /usr/bin/clickhouse
10. DB::InterpreterSelectQuery::getSampleBlockImpl() @ 0x11bb4000 in /usr/bin/clickhouse
11. ? @ 0x11bacdd8 in /usr/bin/clickhouse
12. DB::InterpreterSelectQuery::InterpreterSelectQuery(std::__1::shared_ptr<DB::IAST> const&, std::__1::shared_ptr<DB::Context> const&, std::__1::optional<DB::Pipe>, std::__1::shared_ptr<DB::IStorage> const&, DB::SelectQueryOptions const&, std::__1::vector<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > > const&, std::__1::shared_ptr<DB::StorageInMemoryMetadata const> const&, std::__1::shared_ptr<DB::PreparedSets>) @ 0x11ba84ec in /usr/bin/clickhouse
13. DB::InterpreterSelectWithUnionQuery::buildCurrentChildInterpreter(std::__1::shared_ptr<DB::IAST> const&, std::__1::vector<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > > const&) @ 0x11bee304 in /usr/bin/clickhouse
14. DB::InterpreterSelectWithUnionQuery::InterpreterSelectWithUnionQuery(std::__1::shared_ptr<DB::IAST> const&, std::__1::shared_ptr<DB::Context>, DB::SelectQueryOptions const&, std::__1::vector<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > > const&) @ 0x11bec654 in /usr/bin/clickhouse
15. DB::InterpreterFactory::get(std::__1::shared_ptr<DB::IAST>&, std::__1::shared_ptr<DB::Context>, DB::SelectQueryOptions const&) @ 0x11b5d12c in /usr/bin/clickhouse
16. ? @ 0x11e9e7bc in /usr/bin/clickhouse
17. DB::executeQuery(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::shared_ptr<DB::Context>, bool, DB::QueryProcessingStage::Enum) @ 0x11e9c59c in /usr/bin/clickhouse
18. DB::TCPHandler::runImpl() @ 0x12835ec4 in /usr/bin/clickhouse
19. DB::TCPHandler::run() @ 0x128480a4 in /usr/bin/clickhouse
20. Poco::Net::TCPServerConnection::start() @ 0x134653c0 in /usr/bin/clickhouse
21. Poco::Net::TCPServerDispatcher::run() @ 0x13466938 in /usr/bin/clickhouse
22. Poco::PooledThread::run() @ 0x1364f150 in /usr/bin/clickhouse
23. Poco::ThreadImpl::runnableEntry(void*) @ 0x1364cae4 in /usr/bin/clickhouse
24. start_thread @ 0x7624 in /usr/lib/aarch64-linux-gnu/libpthread-2.31.so
25. ? @ 0xd149c in /usr/lib/aarch64-linux-gnu/libc-2.31.so
(3 additional frame(s) were not displayed)
...
File "posthog/models/event/events_query.py", line 142, in run_events_query
query_result = execute_hogql_query(query=stmt, team=team, workload=Workload.OFFLINE, query_type="EventsQuery")
File "posthog/hogql/query.py", line 77, in execute_hogql_query
results, types = insight_sync_execute(
File "posthog/queries/insight.py", line 12, in insight_sync_execute
return sync_execute(query, args=args, **kwargs)
File "posthog/utils.py", line 1257, in inner
return inner._impl(*args, **kwargs) # type: ignore
File "posthog/clickhouse/client/execute.py", line 111, in sync_execute
raise err
``` | https://github.com/PostHog/posthog/issues/15412 | https://github.com/PostHog/posthog/pull/15420 | 105d7e8b104805a15681c5f27d108f05c367f47a | 4d78965d20db5fdff13d84bdb76af428001ce2f0 | "2023-05-05T17:37:32Z" | python | "2023-05-08T15:25:35Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 15,411 | ["requirements.in", "requirements.txt"] | Retry-After header missing from rate limited / throttled requests | Django Rest Framework's docs on their throttling says that if the `wait` method is implemented, a `Retry-After` header will be added to the response. We do implement the method, but don't get the header.
I suspect some middleware somewhere is removing that header. Tried to fix in a few ways but with no success. | https://github.com/PostHog/posthog/issues/15411 | https://github.com/PostHog/posthog/pull/15424 | aa1fc7d4d5ac954370f339dc8fda0693d6bdf63e | f01add97b1ff009e05fcb8d719ed20038c8c4562 | "2023-05-05T17:35:34Z" | python | "2023-05-08T17:49:04Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 14,978 | [".github/workflows/ci-e2e.yml", ".github/workflows/container-images-ci.yml", "frontend/src/scenes/trends/viz/ActionsHorizontalBar.tsx", "frontend/src/scenes/trends/viz/ActionsPie.tsx"] | Show cohort name in pie chart with multiple cohorts breakdown | ## Is your feature request related to a problem?
Right now if you create a pie chart with multiple cohorts breakdown, the cohorts show up as its ID on the pie chart display
## Describe the solution you'd like
Show the names of the cohorts on the pie chart instead of ID
## Describe alternatives you've considered
## Additional context
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/14978 | https://github.com/PostHog/posthog/pull/15590 | 004116773eca0401c3d5489c923009e70fcd8c03 | 57de4acc4befba2c3c49925c9467ee79af7b9302 | "2023-04-04T20:38:56Z" | python | "2023-05-23T11:14:46Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 14,955 | ["frontend/__snapshots__/scenes-other-login--second-factor.png", "frontend/src/lib/lemon-ui/LemonInput/LemonInput.tsx", "frontend/src/scenes/authentication/Login.stories.tsx", "frontend/src/scenes/authentication/Login2FA.tsx", "frontend/src/scenes/authentication/Setup2FA.tsx", "frontend/src/scenes/authentication/login2FALogic.ts", "frontend/src/scenes/me/Settings/TwoFactorAuthentication.tsx"] | 2FA token field should not be type=number | ## Bug description
The 2FA input field currently has type=number on it, so stepper arrows are shown next to it. This is not intuitive for a 2FA code that will always consist of random digits.
## How to reproduce
1. Set up 2FA on an account
2. Login in
## Environment
- [x] PostHog Cloud US, project ID: [please provide from https://app.posthog.com/project/settings#project-id]
- [ ] PostHog Cloud EU, project ID: [please provide from https://eu.posthog.com/project/settings#project-id]
- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]
- [ ] PostHog self-hosted with Kubernetes (deprecated, see ["Sunsetting Kubernetes support"](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/14955 | https://github.com/PostHog/posthog/pull/15768 | c704cb16fd570e82f4b7204f60870323f2c4c9d0 | 5ebd58ef4629da904a2162587c2b51e5b8b8af04 | "2023-04-02T02:58:32Z" | python | "2023-05-31T18:23:29Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 14,654 | ["frontend/src/lib/lemon-ui/LemonLabel/LemonLabel.tsx"] | Bug: Clicking breakdown tooltip opens new tab | ## Bug description
As per title. Click the breakdown tooltip and we open a new, blank insight in a new tab. Dunno why.
I'm not lying, see?
## How to reproduce
1.
2.
3.
## Environment
- [ ] PostHog Cloud US, project ID: [please provide from https://app.posthog.com/project/settings#project-id]
- [ ] PostHog Cloud EU, project ID: [please provide from https://eu.posthog.com/project/settings#project-id]
- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]
- [ ] PostHog self-hosted with Kubernetes (deprecated, see ["Sunsetting Kubernetes support"](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/14654 | https://github.com/PostHog/posthog/pull/14689 | 89d694c8d2ee0ea104497a2a4e87c1e981d1e9cf | c08f71ac03188e513a529d19173b844878e4b750 | "2023-03-09T13:22:01Z" | python | "2023-03-13T10:50:59Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 14,598 | ["cypress/e2e/events.cy.ts", "frontend/__snapshots__/exporter-exporter--dashboard.png", "frontend/src/lib/lemon-ui/Popover/Popover.scss", "playwright/e2e-vrt/scenes-app/insights.spec.ts-snapshots/annotations-popover-displays-correctly-1-chromium-linux.png"] | Dashboard can't scroll to date range option | ## Bug description
*Please describe.*
- when a dashboard only has 1 row of items, you can't scroll to the bottom of the date range picker
*If this affects the front-end, screenshots would be of great help.*
<img width="776" alt="Screen Shot 2023-03-07 at 8 27 13 AM" src="https://user-images.githubusercontent.com/13127476/223468201-47c3c0cc-c4b7-454f-9ea6-3017e7dce9ec.png">
*If you are on PostHog Cloud it would be really valuable if you can share any links where the problem occurs. This speeds up our ability to troubleshoot tremendously.*
## How to reproduce
1. Make a dashboard with 1 or 2 items in a row
2. Click on date range
3. Try to get to the last option
## Environment
- [ ] PostHog Cloud US, project ID: [please provide from https://app.posthog.com/project/settings#project-id]
- [ ] PostHog Cloud EU, project ID: [please provide from https://eu.posthog.com/project/settings#project-id]
- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]
- [ ] PostHog self-hosted with Kubernetes (deprecated, see ["Sunsetting Kubernetes support"](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/14598 | https://github.com/PostHog/posthog/pull/14519 | 7730ddf908b142d3487da6111b3a33617620eba4 | c9ab01390a47cb9b4f435bfc893cb49cd4b81cd6 | "2023-03-07T15:28:54Z" | python | "2023-03-07T16:56:17Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 14,585 | ["frontend/src/lib/components/DateFilter/RollingDateRangeFilter.tsx", "frontend/src/lib/components/DateFilter/rollingDateRangeFilterLogic.ts", "frontend/src/lib/utils.tsx"] | Last X (quarters) doesn't work as expected in insights | ## Bug description
## How to reproduce
1. go to [an insight](https://app.posthog.com/insights/-XmLO32n)
2. change date range to <img width="278" alt="Screenshot 2023-03-07 at 10 11 32" src="https://user-images.githubusercontent.com/47497682/223391541-cc519615-30fc-4b46-bbc9-6967e8db6926.png">
3. click the 'in the last' text to select the date range
4. it hasn't updated with the 'quarters' appropriately
<img width="245" alt="Screenshot 2023-03-07 at 10 12 02" src="https://user-images.githubusercontent.com/47497682/223391668-c08b0ccb-864c-4f8d-ba17-3aa790854d45.png">
## Environment
- [x] PostHog Cloud US, project ID: [please provide from https://app.posthog.com/project/settings#project-id]
- [ ] PostHog Cloud EU, project ID: [please provide from https://eu.posthog.com/project/settings#project-id]
- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]
- [ ] PostHog self-hosted with Kubernetes (deprecated, see ["Sunsetting Kubernetes support"](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide] | https://github.com/PostHog/posthog/issues/14585 | https://github.com/PostHog/posthog/pull/14610 | a170efbee2f5a138351d93f981aefda177a6fc63 | 2b544a8c06d355a64143eec3320994e59067e578 | "2023-03-07T10:12:49Z" | python | "2023-03-08T08:36:52Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 14,580 | ["frontend/__snapshots__/exporter-exporter--dashboard.png", "frontend/src/toolbar/elements/heatmapLogic.ts"] | Changing date on heatmap always adds events | ## Bug description
Running locally, when you change the date of the heatmap, it sums the events, always seeming to add to the count, even if those events don't exist.
I don't have data older than a week old in this PostHog Cloud project
## How to reproduce
1. Launch heatmap from toolbar
2. Change date repeatedly
3. Numbers always go up
## Environment
- [x] PostHog Cloud US, project ID: 21711
- [ ] PostHog Cloud EU, project ID: [please provide from https://eu.posthog.com/project/settings#project-id]
- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]
- [ ] PostHog self-hosted with Kubernetes (deprecated, see ["Sunsetting Kubernetes support"](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/14580 | https://github.com/PostHog/posthog/pull/14583 | 784594b3f50bd2a310ee33b0e1df4d4ee794541a | 92899527ff27e8dcec3cc37c6f6334190cba126e | "2023-03-07T01:11:01Z" | python | "2023-03-07T14:49:12Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 14,517 | ["cypress/e2e/events.cy.ts", "frontend/__snapshots__/exporter-exporter--dashboard.png", "frontend/src/lib/lemon-ui/Popover/Popover.scss", "playwright/e2e-vrt/scenes-app/insights.spec.ts-snapshots/annotations-popover-displays-correctly-1-chromium-linux.png"] | UI of dropdown in Cohort is messed up | ## Bug description
<img width="672" alt="image" src="https://user-images.githubusercontent.com/344958/222497653-44f099ae-27b2-48d9-85a7-41f4be2f08ba.png">
*Please describe.*
*If this affects the front-end, screenshots would be of great help.*
*If you are on PostHog Cloud it would be really valuable if you can share any links where the problem occurs. This speeds up our ability to troubleshoot tremendously.*
## How to reproduce
1. https://app.posthog.com/cohorts/new
2. click on "completed event" dropdown in the first matching criteria
3.
## Environment
- [x] PostHog Cloud US, project ID: [please provide from https://app.posthog.com/project/settings#project-id]
- [ ] PostHog Cloud EU, project ID: [please provide from https://eu.posthog.com/project/settings#project-id]
- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]
- [ ] PostHog self-hosted with Kubernetes (deprecated, see ["Sunsetting Kubernetes support"](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/14517 | https://github.com/PostHog/posthog/pull/14519 | 7730ddf908b142d3487da6111b3a33617620eba4 | c9ab01390a47cb9b4f435bfc893cb49cd4b81cd6 | "2023-03-02T16:54:50Z" | python | "2023-03-07T16:56:17Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 14,432 | ["frontend/src/scenes/insights/InsightPageHeader.tsx"] | Bug: Tooltip displaying incorrectly | ## Bug description
This tooltip floats over the nav bar in a way I didn't expect
## How to reproduce
1.
2.
3.
## Environment
- [ ] PostHog Cloud US, project ID: [please provide from https://app.posthog.com/project/settings#project-id]
- [ ] PostHog Cloud EU, project ID: [please provide from https://eu.posthog.com/project/settings#project-id]
- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]
- [ ] PostHog self-hosted with Kubernetes (deprecated, see ["Sunsetting Kubernetes support"](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/14432 | https://github.com/PostHog/posthog/pull/14466 | 8987024145efdd57b7ae2c3afddcad650f1a78e1 | d63c133a93bc9e2ace12e537027f42d36ca2aa71 | "2023-02-28T09:27:35Z" | python | "2023-03-01T13:39:54Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 14,347 | ["frontend/src/lib/components/HTMLElementsDisplay/HTMLElementsDisplay.tsx", "frontend/src/lib/components/HTMLElementsDisplay/htmlElementsDisplayLogic.ts", "frontend/src/lib/components/HTMLElementsDisplay/preselectWithCSS.test.ts", "frontend/src/toolbar/actions/actionsTabLogic.tsx"] | The HTMLElementsDisplay truncates the element chain without telling you | When you view an autocapture event's elements in the HTMLElementsDisplay it only shows 10 levels of the elements chain. Which can make you think that the autocapture event doesn't capture the other parts of the chain (when it does)
*Please describe.*
## Describe the solution you'd like
* allow more than 10 elements to be visible in the `HTMLElementsDisplay`
* or maybe indicate that there’s indeed more (“+5 levels hidden”)
## Additional context
Would be good to solve this _after_ https://github.com/PostHog/posthog/pull/14194 since that refactors this component substantially
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/14347 | https://github.com/PostHog/posthog/pull/17749 | 7332c4681e7fb727f72df3da5814ad84d39035fd | 6004fa25102872a18aae09bb79371da046acf2fb | "2023-02-21T17:14:06Z" | python | "2023-10-24T12:23:48Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 14,346 | ["frontend/src/scenes/insights/views/InsightsTable/columns/WorldMapColumn.tsx"] | React Error Attempting to Edit 'Website Users by Location' default insight | On PostHog cloud Dashboards (or Insights), when you attempt to edit or select the 'Website Users by Location', a react error is thrown.
Yields
```
Error: Minified React error #152; visit https://reactjs.org/docs/error-decoder.html?invariant=152&args[]=_k for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
at https://app-static-prod.posthog.com/static/chunk-TJPH6XP2.js:2:48402
at Fi (https://app-static-prod.posthog.com/static/chunk-TJPH6XP2.js:2:57800)
at EV (https://app-static-prod.posthog.com/static/chunk-TJPH6XP2.js:4:8606)
at CV (https://app-static-prod.posthog.com/static/chunk-TJPH6XP2.js:4:858)
at _ve (https://app-static-prod.posthog.com/static/chunk-TJPH6XP2.js:4:781)
at X5 (https://app-static-prod.posthog.com/static/chunk-TJPH6XP2.js:2:85914)
at https://app-static-prod.posthog.com/static/chunk-TJPH6XP2.js:2:37219
at rr.unstable_runWithPriority (https://app-static-prod.posthog.com/static/chunk-TJPH6XP2.js:1:11562)
at Nc (https://app-static-prod.posthog.com/static/chunk-TJPH6XP2.js:2:36928)
at $F (https://app-static-prod.posthog.com/static/chunk-TJPH6XP2.js:2:37165)
at Xs (https://app-static-prod.posthog.com/static/chunk-TJPH6XP2.js:2:37100)
at Rc (https://app-static-prod.posthog.com/static/chunk-TJPH6XP2.js:2:82670)
at ZF (https://app-static-prod.posthog.com/static/chunk-TJPH6XP2.js:2:54274)
at https://app-static-prod.posthog.com/static/chunk-TJPH6XP2.js:5:4427
at s (https://app-static-prod.posthog.com/static/chunk-TJPH6XP2.js:5:7239)
at Object.d [as dispatch] (https://app-static-prod.posthog.com/static/chunk-TJPH6XP2.js:4:23266)
at e (<anonymous>:1:37227)
at https://app-static-prod.posthog.com/static/chunk-M4F5WCNY.js:1:8824
at https://app-static-prod.posthog.com/static/chunk-AFOQASK2.js:1:1459
at Object.dispatch (https://app-static-prod.posthog.com/static/chunk-TJPH6XP2.js:5:21084)
at Object.dispatch (<anonymous>:1:55003)
at t.actions.<computed> [as setScene] (https://app-static-prod.posthog.com/static/chunk-TJPH6XP2.js:5:11717)
at loadScene (https://app-static-prod.posthog.com/static/chunk-Q4OWXYAV.js:5:32711)
```
*Links:*
Example Page where screen shot was taken: https://app.posthog.com/dashboard/62518
Page where error occurs: https://app.posthog.com/insights/vISeHxhh/edit
## How to reproduce
1. In PostHog Cloud, create a new dashboard
2. Choose template Website Traffic.
3. On the default insight 'Website Users by location', click the ellipses, then select 'Edit' to present the error. (See screenshot)
4. Replace step 3 by clicking on the 'Website Users by location' title to give the same error.
## Environment
PostHog Cloud US project ID: 19840 | https://github.com/PostHog/posthog/issues/14346 | https://github.com/PostHog/posthog/pull/14354 | 736638828f28794422da410dc3db90cb435f424b | 0221a25e5d306c2c3665903d1d437aafd744a660 | "2023-02-21T16:56:10Z" | python | "2023-02-22T11:39:07Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 14,327 | ["plugin-server/src/main/ingestion-queues/batch-processing/each-batch-ingestion.ts", "plugin-server/src/main/ingestion-queues/metrics.ts", "plugin-server/src/worker/ingestion/event-pipeline/populateTeamDataStep.ts", "plugin-server/src/worker/ingestion/team-manager.ts", "plugin-server/tests/helpers/metrics.ts", "plugin-server/tests/main/ingestion-queues/analytics-events-ingestion-consumer.test.ts", "plugin-server/tests/main/ingestion-queues/analytics-events-ingestion-overflow-consumer.test.ts", "plugin-server/tests/main/ingestion-queues/each-batch.test.ts", "plugin-server/tests/worker/ingestion/event-pipeline/populateTeamDataStep.test.ts", "plugin-server/tests/worker/ingestion/team-manager.test.ts"] | Lightweigth capture 1/4: always resolve team_id at p-s and compare result | Let's start doing it as soon as possible to build trust on the performance and accuracy of the resolution code in plugin-server.
- [ ] Always hit postgres for resolution, even if `team_id` is found in the event
- [ ] If `team_id` is found in the event, compare the lookup result, and increment a prometheus metric with ok/error status. Log differences if found, and keep the value from capture
- [ ] Let's review the caching logic doesn't get into edge cases when tokens are rotated.
## Why now?
This has been identified as something not to port in a rewrite of capture. Regardless of whether capture v2 plans move forward in Q1, this will help with:
- making sure we don't DLQ & timeout when PG is unhealthy
- allowing infra to have a less stressful PG upgrade (version 11 goes EOL in October)
- scaling down posthog-events, as the team resolution is a 20%-ish part of the endpoint latency | https://github.com/PostHog/posthog/issues/14327 | https://github.com/PostHog/posthog/pull/14341 | 7402439c6142bdd8936ec7690a291a5c40baa175 | 25cb653c1bdb21cf6839e17211491b05f2d106f5 | "2023-02-21T10:38:50Z" | python | "2023-02-22T13:24:05Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 13,910 | ["posthog/clickhouse/migrations/0039_person_overrides_dict.py", "posthog/clickhouse/schema.py", "posthog/clickhouse/test/test_person_overrides.py", "posthog/management/commands/setup_test_environment.py", "posthog/models/person_overrides/sql.py"] | Add dictionary to ClickHouse | null | https://github.com/PostHog/posthog/issues/13910 | https://github.com/PostHog/posthog/pull/13946 | da482a3cba83ac9c5ff731f696f85ae13cf3d003 | e5b3c32eb56a729c98d5c2868c8b119b6bd30f69 | "2023-01-24T19:13:50Z" | python | "2023-01-27T14:28:23Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 13,707 | ["frontend/src/scenes/dashboard/NewDashboardModal.tsx"] | Bug when trying to create a dahsboard by filling all inputs (optional and mandatory) | ## Bug description
*Please describe.*
*If this affects the front-end, screenshots would be of great help.*
When I try to create a dashboard, if I fill the description PostHog doesn't create the dashboard, but if I don't fill it PostHog creates the dashboard.
When I create the dashboard without the description and I try to add it afterwards, postHog tells me that to add it I have to be in premium plan.
https://user-images.githubusercontent.com/33268490/212322865-119ba439-79b2-47ab-88ce-aafe99fb4b23.mov
*If you are on PostHog Cloud it would be really valuable if you can share any links where the problem occurs. This speeds up our ability to troubleshoot tremendously.*
## How to reproduce
1. New dashboard
2. Fill in all inputs: Name, Description and template.
3. Create
## Environment
- [X] PostHog Cloud
- [ ] self-hosted PostHog, version/commit: please provide
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/13707 | https://github.com/PostHog/posthog/pull/13709 | cdbdaba69579eafd87fb726c5bb4d8e31c63edea | d7755e1726ef1be6979ad6ad6248214577b878ca | "2023-01-13T12:43:07Z" | python | "2023-01-13T19:43:30Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 13,667 | ["ee/clickhouse/models/test/__snapshots__/test_property.ambr", "ee/clickhouse/models/test/test_cohort.py", "ee/clickhouse/models/test/test_property.py", "posthog/models/cohort/util.py", "posthog/models/property/util.py"] | CHQueryErrorAmbiguousColumnName (person_id) | Sentry Issue: [POSTHOG-8YY](https://sentry.io/organizations/posthog/issues/3842781226/?referrer=github_integration)
```
ServerException: Code: 352.
DB::Exception: Ambiguous column 'person_id': While processing SELECT toTimeZone(toDateTime(timestamp, 'UTC'), 'UTC') AS timestamp, `--pdi.person_id` AS actor_id FROM events ..... [Check Sentry for raw sql]. timestamp, actor_id. Stack trace:
0. DB::Exception::Exception(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, int, bool) @ 0xa3f9b5a in /usr/bin/clickhouse
1. ? @ 0x14e99975 in /usr/bin/clickhouse
2. DB::JoinToSubqueryTransformMatcher::visit(DB::ASTSelectQuery&, std::__1::shared_ptr<DB::IAST>&, DB::JoinToSubqueryTransformMatcher::Data&) @ 0x14ec7880 in /usr/bin/clickhouse
3. DB::InDepthNodeVisitor<DB::JoinToSubqueryTransformMatcher, true, false, std::__1::shared_ptr<DB::IAST> >::visit(std::__1::shared_ptr<DB::IAST>&) @ 0x14e73eb2 in /usr/bin/clickhouse
4. DB::InterpreterSelectQuery::InterpreterSelectQuery(std::__1::shared_ptr<DB::IAST> const&, std::__1::shared_ptr<DB::Context> const&, std::__1::optional<DB::Pipe>, std::__1::shared_ptr<DB::IStorage> const&, DB::SelectQueryOptions const&, std::__1::vector<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > > const&, std::__1::shared_ptr<DB::StorageInMemoryMetadata const> const&, std::__1::shared_ptr<DB::PreparedSets>) @ 0x14e52b39 in /usr/bin/clickhouse
5. DB::InterpreterSelectWithUnionQuery::buildCurrentChildInterpreter(std::__1::shared_ptr<DB::IAST> const&, std::__1::vector<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > > const&) @ 0x14ea06cc in /usr/bin/clickhouse
6. DB::InterpreterSelectWithUnionQuery::InterpreterSelectWithUnionQuery(std::__1::shared_ptr<DB::IAST> const&, std::__1::shared_ptr<DB::Context>, DB::SelectQueryOptions const&, std::__1::vector<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > > const&) @ 0x14e9e3cc in /usr/bin/clickhouse
7. DB::InterpreterSelectWithUnionQuery::getSampleBlock(std::__1::shared_ptr<DB::IAST> const&, std::__1::shared_ptr<DB::Context const>, bool) @ 0x14ea185b in /usr/bin/clickhouse
8. DB::getDatabaseAndTablesWithColumns(std::__1::vector<DB::ASTTableExpression const*, std::__1::allocator<DB::ASTTableExpression const*> > const&, std::__1::shared_ptr<DB::Context const>, bool, bool) @ 0x151ad121 in /usr/bin/clickhouse
9. DB::JoinedTables::resolveTables() @ 0x14ed9901 in /usr/bin/clickhouse
10. DB::InterpreterSelectQuery::InterpreterSelectQuery(std::__1::shared_ptr<DB::IAST> const&, std::__1::shared_ptr<DB::Context> const&, std::__1::optional<DB::Pipe>, std::__1::shared_ptr<DB::IStorage> const&, DB::SelectQueryOptions const&, std::__1::vector<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > > const&, std::__1::shared_ptr<DB::StorageInMemoryMetadata const> const&, std::__1::shared_ptr<DB::PreparedSets>) @ 0x14e523f5 in /usr/bin/clickhouse
11. DB::InterpreterSelectWithUnionQuery::buildCurrentChildInterpreter(std::__1::shared_ptr<DB::IAST> const&, std::__1::vector<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > > const&) @ 0x14ea06cc in /usr/bin/clickhouse
12. DB::InterpreterSelectWithUnionQuery::InterpreterSelectWithUnionQuery(std::__1::shared_ptr<DB::IAST> const&, std::__1::shared_ptr<DB::Context>, DB::SelectQueryOptions const&, std::__1::vector<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > > const&) @ 0x14e9e3cc in /usr/bin/clickhouse
13. DB::InterpreterSelectWithUnionQuery::getSampleBlock(std::__1::shared_ptr<DB::IAST> const&, std::__1::shared_ptr<DB::Context const>, bool) @ 0x14ea185b in /usr/bin/clickhouse
14. DB::getDatabaseAndTablesWithColumns(std::__1::vector<DB::ASTTableExpression const*, std::__1::allocator<DB::ASTTableExpression const*> > const&, std::__1::shared_ptr<DB::Context const>, bool, bool) @ 0x151ad121 in /usr/bin/clickhouse
15. DB::JoinedTables::resolveTables() @ 0x14ed9901 in /usr/bin/clickhouse
16. DB::InterpreterSelectQuery::InterpreterSelectQuery(std::__1::shared_ptr<DB::IAST> const&, std::__1::shared_ptr<DB::Context> const&, std::__1::optional<DB::Pipe>, std::__1::shared_ptr<DB::IStorage> const&, DB::SelectQueryOptions const&, std::__1::vector<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > > const&, std::__1::shared_ptr<DB::StorageInMemoryMetadata const> const&, std::__1::shared_ptr<DB::PreparedSets>) @ 0x14e523f5 in /usr/bin/clickhouse
17. DB::InterpreterSelectWithUnionQuery::buildCurrentChildInterpreter(std::__1::shared_ptr<DB::IAST> const&, std::__1::vector<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > > const&) @ 0x14ea06cc in /usr/bin/clickhouse
18. DB::InterpreterSelectWithUnionQuery::InterpreterSelectWithUnionQuery(std::__1::shared_ptr<DB::IAST> const&, std::__1::shared_ptr<DB::Context>, DB::SelectQueryOptions const&, std::__1::vector<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > > const&) @ 0x14e9e3cc in /usr/bin/clickhouse
19. DB::InterpreterSelectWithUnionQuery::getSampleBlock(std::__1::shared_ptr<DB::IAST> const&, std::__1::shared_ptr<DB::Context const>, bool) @ 0x14ea185b in /usr/bin/clickhouse
20. DB::getDatabaseAndTablesWithColumns(std::__1::vector<DB::ASTTableExpression const*, std::__1::allocator<DB::ASTTableExpression const*> > const&, std::__1::shared_ptr<DB::Context const>, bool, bool) @ 0x151ad121 in /usr/bin/clickhouse
21. DB::JoinedTables::resolveTables() @ 0x14ed9901 in /usr/bin/clickhouse
22. DB::InterpreterSelectQuery::InterpreterSelectQuery(std::__1::shared_ptr<DB::IAST> const&, std::__1::shared_...
(2 additional frame(s) were not displayed)
...
File "clickhouse_driver/client.py", line 453, in process_ordinary_query
return self.receive_result(with_column_types=with_column_types,
File "clickhouse_driver/client.py", line 117, in receive_result
return result.get_result()
File "clickhouse_driver/result.py", line 50, in get_result
for packet in self.packet_generator:
File "clickhouse_driver/client.py", line 133, in packet_generator
packet = self.receive_packet()
File "clickhouse_driver/client.py", line 150, in receive_packet
raise packet.exception
CHQueryErrorAmbiguousColumnName: Code: 352.
DB::Exception: Ambiguous column 'person_id': While processing SELECT toTimeZone(toDateTime(timestamp, 'UTC'), 'UTC') AS timestamp, `--pdi.person_id` AS actor_id FROM events AS e INNER JOIN (SELECT distinct_id, argMax(person_id, version) AS person_id FROM person_distinct_id2 WHERE team_id = 12128 GROUP BY distinct_id HAVING argMax(is_deleted, version) = 0) AS pdi ON e.distinct_id = pdi.distinct_id INNER JOIN (SELECT id FROM person WHERE (team_id = 12128) AND (id IN (SELECT id FROM person WHERE (team_id = 12128) AND ((NOT (person.pmat_email ILIKE '%@kiter.app%')) AND (NOT has(['[email protected]', '[email protected]'], person.pmat_email))))) GROUP BY id HAVING (max(is_deleted) = 0) AND ((NOT (argMax(person.pmat_email, version) ILIKE '%@kiter.app%')) AND (NOT has(['[email protected]', '[email protected]'], argMax(person.pmat_email, version))))) AS person ON person.id = pdi.person_id WHERE (team_id = 12128) AND ((match(elements_chain, '(text="GET\\ STARTED")') AND (event = '$autocapture') AND (person_id IN (SELECT person_id FROM cohortpeople WHERE (team_id = 12128) AND (cohort_id = 15929) GROUP BY person_id, cohort_id, team_id, version HAVING sum(sign) > 0))) OR ((match(elements_chain, '(^|;)button(\\.|$|;|:)') AND match(elements_chain, '(text="Get\\ Started")')) AND (event = '$autocapture') AND (person_id IN (SELECT person_id FROM cohortpeople WHERE (team_id = 12128) AND (cohort_id = 15929) GROUP BY person_id, cohort_id, team_id, version HAVING sum(sign) > 0)))) AND (toDateTime(timestamp, 'UTC') >= toDateTime('2022-12-05 00:00:00', 'UTC')) AND (toDateTime(timestamp, 'UTC') <= toDateTime('2023-01-11 23:59:59', 'UTC')) AND (NOT has(['localhost:8000', 'localhost:5000', '127.0.0.1:8000', '127.0.0.1:3000', 'localhost:3000'], `mat_$host`)) GROUP BY timestamp, actor_id. Stack trace:
0. DB::Exception::Exception(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, int, bool) @ 0xa3f9b5a in /usr/bin/clickhouse
1. ? @ 0x14e99975 in /usr/bin/clickhouse
2. DB::JoinToSubqueryTransformMatcher::visit(DB::ASTSelectQuery&, std::__1::shared_ptr<DB::IAST>&, DB::JoinToSubqueryTransformMatcher::Data&) @ 0x14ec7880 in /usr/bin/clickhouse
3. DB::InDepthNodeVisitor<DB::JoinToSubqueryTransformMatcher, true, false, std::__1::shared_ptr<DB::IAST> >::visit(std::__1::shared_ptr<DB::IAST>&) @ 0x14e73eb2 in /usr/bin/clickhouse
4. DB::InterpreterSelectQuery::InterpreterSelectQuery(std::__1::shared_ptr<DB::IAST> const&, std::__1::shared_ptr<DB::Context> const&, std::__1::optional<DB::Pipe>, std::__1::shared_ptr<DB::IStorage> const&, DB::SelectQueryOptions const&, std::__1::vector<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > > const&, std::__1::shared_ptr<DB::StorageInMemoryMetadata const> const&, std::__1::shared_ptr<DB::PreparedSets>) @ 0x14e52b39 in /usr/bin/clickhouse
5. DB::InterpreterSelectWithUnionQuery::buildCurrentChildInterpreter(std::__1::shared_ptr<DB::IAST> const&, std::__1::vector<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > > const&) @ 0x14ea06cc in /usr/bin/clickhouse
6. DB::InterpreterSelectWithUnionQuery::InterpreterSelectWithUnionQuery(std::__1::shared_ptr<DB::IAST> const&, std::__1::shared_ptr<DB::Context>, DB::SelectQueryOptions const&, std::__1::vector<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > > const&) @ 0x14e9e3cc in /usr/bin/clickhouse
7. DB::InterpreterSelectWithUnionQuery::getSampleBlock(std::__1::shared_ptr<DB::IAST> const&, std::__1::shared_ptr<DB::Context const>, bool) @ 0x14ea185b in /usr/bin/clickhouse
8. DB::getDatabaseAndTablesWithColumns(std::__1::vector<DB::ASTTableExpression const*, std::__1::allocator<DB::ASTTableExpression const*> > const&, std::__1::shared_ptr<DB::Context const>, bool, bool) @ 0x151ad121 in /usr/bin/clickhouse
9. DB::JoinedTables::resolveTables() @ 0x14ed9901 in /usr/bin/clickhouse
10. DB::InterpreterSelectQuery::InterpreterSelectQuery(std::__1::shared_ptr<DB::IAST> const&, std::__1::shared_ptr<DB::Context> const&, std::__1::optional<DB::Pipe>, std::__1::shared_ptr<DB::IStorage> const&, DB::SelectQueryOptions const&, std::__1::vector<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > > const&, std::__1::shared_ptr<DB::StorageInMemoryMetadata const> const&, std::__1::shared_ptr<DB::PreparedSets>) @ 0x14e523f5 in /usr/bin/clickhouse
11. DB::InterpreterSelectWithUnionQuery::buildCurrentChildInterpreter(std::__1::shared_ptr<DB::IAST> const&, std::__1::vector<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > > const&) @ 0x14ea06cc in /usr/bin/clickhouse
12. DB::InterpreterSelectWithUnionQuery::InterpreterSelectWithUnionQuery(std::__1::shared_ptr<DB::IAST> const&, std::__1::shared_ptr<DB::Context>, DB::SelectQueryOptions const&, std::__1::vector<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > > const&) @ 0x14e9e3cc in /usr/bin/clickhouse
13. DB::InterpreterSelectWithUnionQuery::getSampleBlock(std::__1::shared_ptr<DB::IAST> const&, std::__1::shared_ptr<DB::Context const>, bool) @ 0x14ea185b in /usr/bin/clickhouse
14. DB::getDatabaseAndTablesWithColumns(std::__1::vector<DB::ASTTableExpression const*, std::__1::allocator<DB::ASTTableExpression const*> > const&, std::__1::shared_ptr<DB::Context const>, bool, bool) @ 0x151ad121 in /usr/bin/clickhouse
15. DB::JoinedTables::resolveTables() @ 0x14ed9901 in /usr/bin/clickhouse
16. DB::InterpreterSelectQuery::InterpreterSelectQuery(std::__1::shared_ptr<DB::IAST> const&, std::__1::shared_ptr<DB::Context> const&, std::__1::optional<DB::Pipe>, std::__1::shared_ptr<DB::IStorage> const&, DB::SelectQueryOptions const&, std::__1::vector<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > > const&, std::__1::shared_ptr<DB::StorageInMemoryMetadata const> const&, std::__1::shared_ptr<DB::PreparedSets>) @ 0x14e523f5 in /usr/bin/clickhouse
17. DB::InterpreterSelectWithUnionQuery::buildCurrentChildInterpreter(std::__1::shared_ptr<DB::IAST> const&, std::__1::vector<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > > const&) @ 0x14ea06cc in /usr/bin/clickhouse
18. DB::InterpreterSelectWithUnionQuery::InterpreterSelectWithUnionQuery(std::__1::shared_ptr<DB::IAST> const&, std::__1::shared_ptr<DB::Context>, DB::SelectQueryOptions const&, std::__1::vector<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > > const&) @ 0x14e9e3cc in /usr/bin/clickhouse
19. DB::InterpreterSelectWithUnionQuery::getSampleBlock(std::__1::shared_ptr<DB::IAST> const&, std::__1::shared_ptr<DB::Context const>, bool) @ 0x14ea185b in /usr/bin/clickhouse
20. DB::getDatabaseAndTablesWithColumns(std::__1::vector<DB::ASTTableExpression const*, std::__1::allocator<DB::ASTTableExpression const*> > const&, std::__1::shared_ptr<DB::Context const>, bool, bool) @ 0x151ad121 in /usr/bin/clickhouse
21. DB::JoinedTables::resolveTables() @ 0x14ed9901 in /usr/bin/clickhouse
22. DB::InterpreterSelectQuery::InterpreterSelectQuery(std::__1::shared_ptr<DB::IAST> const&, std::__1::shared_...
(17 additional frame(s) were not displayed)
...
File "posthog/queries/base.py", line 62, in handle_compare
base_entitites = func(filter=filter, team=team, **kwargs)
File "posthog/queries/trends/formula.py", line 76, in _run_formula_query
result = insight_sync_execute(
File "posthog/queries/insight.py", line 12, in insight_sync_execute
return sync_execute(query, args=args, **kwargs)
File "posthog/utils.py", line 1204, in inner
return inner._impl(*args, **kwargs) # type: ignore
File "posthog/clickhouse/client/execute.py", line 91, in sync_execute
raise err
``` | https://github.com/PostHog/posthog/issues/13667 | https://github.com/PostHog/posthog/pull/13781 | 8930d9e46039c44d5c59157104b6ae6fbec0c5b5 | 7bd5574861227ae5fd0c84b71c830b3cbd69d5d1 | "2023-01-12T08:54:56Z" | python | "2023-01-20T14:25:18Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 13,098 | ["posthog/models/entity/entity.py"] | `"avg" is not a valid choice` error is raised by API | Sentry Issue: [POSTHOG-EU-3K](https://sentry.io/organizations/posthog/issues/3662211615/?referrer=github_integration)
```
ValidationError: {'events': [{'math': [ErrorDetail(string='"avg" is not a valid choice.', code='invalid_choice')]}]}
File "posthog/api/insight.py", line 604, in trend
serializer.is_valid(raise_exception=True)
File "rest_framework/serializers.py", line 228, in is_valid
raise ValidationError(self.errors)
``` | https://github.com/PostHog/posthog/issues/13098 | https://github.com/PostHog/posthog/pull/13099 | 5634ab4d7fb6f62229b85e0635e59bd775bbb468 | 393503c764cfee89af99c7c82b6cfc89f84b221a | "2022-12-02T16:46:18Z" | python | "2022-12-02T17:16:56Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 13,039 | ["frontend/src/layout/navigation/ProjectSwitcher.tsx"] | Project "Demo" label doesn't get wrapped properly | ## Bug description
This looks off:
<img width="337" alt="Screenshot 2022-11-30 at 16 36 18" src="https://user-images.githubusercontent.com/4550621/204841296-a0d407c4-cf9e-46ae-9314-736f284fd3bc.png">
Seen in Cypress tests. CC @raquelmsmith
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/13039 | https://github.com/PostHog/posthog/pull/13043 | 8878673e443c143bc70d6abf425ebc38494a2085 | 7e9e0fac95af179b78271651edf2056fe3d672f9 | "2022-11-30T15:37:41Z" | python | "2022-11-30T18:15:11Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 12,999 | ["cypress/e2e/projectHomepage.js", "frontend/src/scenes/project-homepage/ProjectHomepage.tsx", "frontend/src/scenes/project-homepage/projectHomepageLogic.tsx"] | Home page: dashboard logic is mounted twice, causing excessive API load | ## Bug description
PostHog home page contains a home dashboard. However when checking the network tab, all requests are made twice
## How to reproduce
1. Reload a dashboard
2. Check network tab
3. See multiple requests to load dashboard
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog, version/commit: please provide
## Additional context
I added console.logs to `afterMount` and `beforeUnmount` - issue seems to stem from the logic getting mounted and immediately unmounted and then mounted again - all with the same props. Something something kea?
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/12999 | https://github.com/PostHog/posthog/pull/13001 | d647f1edfc231fc4342de13822c971a564c68148 | b2cddc330310967401277e1019fb69165b999936 | "2022-11-29T09:35:46Z" | python | "2022-11-29T10:57:58Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 12,986 | ["ee/clickhouse/views/test/__snapshots__/test_clickhouse_trends.ambr", "posthog/queries/breakdown_props.py", "posthog/queries/person_query.py", "posthog/queries/test/__snapshots__/test_trends.ambr", "posthog/queries/test/test_trends.py", "posthog/queries/trends/breakdown.py", "posthog/queries/trends/sql.py", "posthog/queries/trends/total_volume.py", "posthog/queries/trends/trends_event_query.py", "posthog/queries/trends/util.py"] | WAU/MAU don't work with aggregated Trends display modes | ## Bug description
When calculating Trends results with an aggregated (e.g. single output, like big number) display type, WAU/MAU don't work. This is because we have an `ACTIVE_USERS_SQL` query for time series display types, but we don't have a version of this for aggregated display types. (See ZEN-1043.)
## How to reproduce
1. Create an insight with a single WAU or MAU series.
2. Switch display type to "Number".
3. Open the "Debug ClickHouse queries" modal from the command palette.
4. See `COUNT(*)` instead of `COUNT(DISTINCT person_id)`.
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/12986 | https://github.com/PostHog/posthog/pull/13131 | 4635648eb0e25f671f84d576184c288abb8b91f1 | 777fa5a3156e29b3b4e772da1d4b23916398b866 | "2022-11-28T17:35:55Z" | python | "2022-12-05T18:51:35Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 12,891 | ["posthog/rate_limit.py"] | Rate-limiting fails for organization-based endpoints | Sentry Issue: [POSTHOG-7DN](https://sentry.io/organizations/posthog/issues/3562256605/?referrer=github_integration) | https://github.com/PostHog/posthog/issues/12891 | https://github.com/PostHog/posthog/pull/12892 | 4716878857e6560732dd3a21a39cbe3982c5bcb9 | 51998650b4ac524fa29c870553091a1a95a5df22 | "2022-11-21T15:13:12Z" | python | "2022-11-21T17:13:56Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 12,853 | ["posthog/models/team/util.py"] | 500 response for DELETE /projects/<id> | ## Bug description
We use the Posthog API to create ephemeral projects while developing our app locally. The script that creates these projects attempts to delete an existing project that matches the naming convention to prevent a pile of projects from being created. It was working fine for weeks but started to receive a 500 response consistently as of NOV 16, 2022. After encountering the 500 error, the project still appears in the front end but cannot be deleted there either.
## How to reproduce
0. Using NodeJS 16 and [email protected]
1. Create a project via the API `POST /projects`
2. Delete the project via the API `DELETE /projects/<id>`
3. _500 error_
4. Try to delete the project in the front-end
5. _500 error_
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog, version/commit: please provide
## Additional context
> Script logs
<img width="528" alt="Screen Shot 2022-11-17 at 10 16 26 AM" src="https://user-images.githubusercontent.com/5888427/202525627-f055f2fe-3237-4d76-820f-bc4c5158f3cb.png">
> Error in Chrome Dev Tools - Network Tab
<img width="1472" alt="Screen Shot 2022-11-17 at 10 17 26 AM" src="https://user-images.githubusercontent.com/5888427/202526222-b5467c0c-702a-4282-8578-5144bd31a54d.png">
<img width="1475" alt="Screen Shot 2022-11-17 at 10 17 38 AM" src="https://user-images.githubusercontent.com/5888427/202526242-6d6b4330-f55b-452a-8972-c12c68f4d8f0.png">
> Script Source Code - `setup-posthog-project.ts` _(pardon the roughness)_
```typescript
import axios from 'axios';
import { config } from 'dotenv';
import { expand } from 'dotenv-expand';
import { readFile, writeFile } from 'node:fs/promises';
import { join } from 'node:path';
import { inspect } from 'node:util';
import { PostHog } from 'posthog-node';
import PrettyError from 'pretty-error';
type EnvironmentVariables = {
POSTHOG_PERSONAL_API_KEY: string;
POSTHOG_PERSONAL_PROJECT: string;
POSTHOG_REAL_PROJECT_ID: number;
};
type Paginated<T> = {
count: number;
next: null | string;
results: T[];
};
type ProjectMinimal = {
id: number;
uuid: string;
organization: string;
api_token: string;
name: string;
completed_snippet_onboarding: boolean;
ingested_event: boolean;
is_demo: boolean;
timezone: string;
access_control: boolean;
effective_membership_level: number;
};
type ProjectFull = ProjectMinimal & {
app_urls: string[];
slack_incoming_webhook: string;
anonymize_ips: boolean;
test_account_filters: Record<string, any>;
test_account_filters_default_checked: boolean;
path_cleaning_filters: Record<string, any>;
timezone: string;
data_attributes: Record<string, any>;
person_display_name_properties: string[];
correlation_config: Record<string, any>;
session_recording_opt_in: boolean;
access_control: boolean;
primary_dashboard: number;
live_events_columns: string[];
recording_domains: string[];
};
type PropertyType = 'DateTime' | 'String' | 'Numeric' | 'Boolean';
type EventProperty = {
id: string;
name: string;
description: string;
tags: any[];
is_numerical: boolean;
is_event_property: string;
property_type: PropertyType;
};
type Cohort = {
id: number;
name: string;
description: string;
deleted: boolean;
groups: Record<string, any>;
filters: Record<string, any>;
is_calculating: boolean;
last_calculation: string;
errors_calculating: number;
count: number;
is_static: boolean;
};
type Experiment = {
id: number;
name: string;
description: string;
start_date: string;
end_date: string;
feature_flag_key: string;
feature_flag: number;
parameters: Record<string, any>;
secondary_metrics: Record<string, any>;
filters: Record<string, any>;
archived: boolean;
};
type FeatureFlag = {
id: number;
name: string;
key: string;
filters: Record<string, any>;
deleted: boolean;
active: boolean;
is_simple_flag: boolean;
rollout_percentage: number;
ensure_experience_continuity: boolean;
experiment_set: number[];
};
function createProjectObject<
T extends Omit<
ProjectFull,
| 'primary_dashboard'
| Exclude<
keyof ProjectMinimal,
'name' | 'completed_snippet_onboarding' | 'timezone' | 'access_control'
>
>
>(payload: T): T {
return payload;
}
const DEV_PROJECT_PREFIX = 'Webapp DEV - ';
async function main() {
const pathToEnvFile = join(__dirname, '../../../../.env');
console.log('Loading .env file');
const beforeExpansion = config({
path: pathToEnvFile
});
if (beforeExpansion.error) {
throw beforeExpansion.error;
}
if (!beforeExpansion.parsed) {
throw new Error('No `beforeExpansion.parsed` property found');
}
const INITIAL_VARS =
beforeExpansion.parsed as unknown as EnvironmentVariables;
const printableInitialVars = inspect(INITIAL_VARS, false, null, true);
if (!INITIAL_VARS.POSTHOG_PERSONAL_API_KEY) {
throw new Error(
`The current '.env' file (before variable expansion) does not have a 'POSTHOG_PERSONAL_API_KEY' variable or it's empty. This variable should point to another variable "POSTHOG_DEV_API_KEY" that is set in your shell startup script or "~/.mayan/env". Are you sure you are in an "emulation" flow? \n${printableInitialVars}`
);
}
if (!INITIAL_VARS.POSTHOG_PERSONAL_PROJECT) {
throw new Error(
`The current '.env' file (before variable expansion) does not have a 'POSTHOG_PERSONAL_PROJECT' variable or it's empty. This variable should point to another variable "POSTHOG_DEV_PROJECT" that is set in your shell startup script or "~/.mayan/env". Are you sure you are in an "emulation" flow? \n${printableInitialVars}`
);
}
if (!INITIAL_VARS.POSTHOG_REAL_PROJECT_ID) {
throw new Error(
`The current '.env' file (before variable expansion) does not have a 'POSTHOG_REAL_PROJECT_ID' variable or it's empty. This variable should be an integer. Are you sure you are in an "emulation" flow? \n${printableInitialVars}`
);
}
// console.log('initial `.env` contents = ', INITIAL_VARS);
console.log('Expanding `.env` file');
const afterExpansion = expand(beforeExpansion);
if (afterExpansion.error) {
throw afterExpansion.error;
}
if (!afterExpansion.parsed) {
throw new Error('No `afterExpansion.parsed` property found');
}
const FINAL_VARS = afterExpansion.parsed as unknown as EnvironmentVariables;
const printableFinalVars = inspect(FINAL_VARS, false, null, true);
if (!FINAL_VARS.POSTHOG_PERSONAL_API_KEY) {
throw new Error(
`The current '.env' file (after variable expansion) does not have a 'POSTHOG_PERSONAL_API_KEY' variable or it's empty. This variable should point to another variable "POSTHOG_DEV_API_KEY" that is set in your shell startup script or "~/.mayan/env". Are you sure you are in an "emulation" flow? \n${printableFinalVars}`
);
}
if (!FINAL_VARS.POSTHOG_PERSONAL_PROJECT) {
throw new Error(
`The current '.env' file (after variable expansion) does not have a 'POSTHOG_PERSONAL_PROJECT' variable or it's empty. This variable should point to another variable "POSTHOG_DEV_PROJECT" that is set in your shell startup script or "~/.mayan/env". Are you sure you are in an "emulation" flow? \n${printableFinalVars}`
);
}
if (!FINAL_VARS.POSTHOG_REAL_PROJECT_ID) {
throw new Error(
`The current '.env' file (after variable expansion) does not have a 'POSTHOG_REAL_PROJECT_ID' variable or it's empty. This variable should be an integer. Are you sure you are in an "emulation" flow? \n${printableFinalVars}`
);
}
// console.log('expanded `.env` contents = ', FINAL_VARS);
const posthogApi = axios.create({
baseURL: 'https://app.posthog.com/api',
headers: {
Authorization: `Bearer ${FINAL_VARS.POSTHOG_PERSONAL_API_KEY}`
}
});
const paginationOptions = {
params: {
limit: 1000
}
};
console.log('Fetching real project info');
const { data: realProject } = await posthogApi.get<ProjectFull>(
`/projects/${FINAL_VARS.POSTHOG_REAL_PROJECT_ID}`
);
// console.log('real project contents = ', realProject);
console.log('Fetching real property definitions');
const { data: propertyDefinitions } = await posthogApi.get<
Paginated<EventProperty>
>(`/projects/${realProject.id}/property_definitions`, paginationOptions);
// console.dir(propertyDefinitions, {
// depth: null,
// colors: true
// });
console.log('Fetching real cohorts');
const { data: cohorts } = await posthogApi.get<Paginated<Cohort>>(
`/projects/${realProject.id}/cohorts`,
paginationOptions
);
// console.log('real experiments contents = ', realProject);
console.log('Fetching real experiments');
const { data: experiments } = await posthogApi.get<Paginated<Experiment>>(
`/projects/${realProject.id}/experiments`,
paginationOptions
);
// console.log('real experiments contents = ', realProject);
console.log('Fetching real feature flags');
const { data: featureFlags } = await posthogApi.get<Paginated<FeatureFlag>>(
`/projects/${realProject.id}/feature_flags`,
paginationOptions
);
// console.log('real feature flags contents = ', realProject);
console.log('Fetching project list');
const { data } = await posthogApi.get<Paginated<ProjectMinimal>>(
'/projects',
paginationOptions
);
// console.log('Project list loaded; searching for existing dev project');
if (data.count > 100) {
throw new Error('More that 100 projects?!');
}
let existingProject: ProjectMinimal | undefined;
const projectName = `${DEV_PROJECT_PREFIX}${FINAL_VARS.POSTHOG_PERSONAL_PROJECT}`;
for (const item of data.results) {
if (item.name === projectName) {
existingProject = item;
continue;
}
}
if (existingProject) {
console.log('Existing dev project found; cleaning up...');
await posthogApi.delete(`/projects/${existingProject.id}`);
console.log('Existing dev project deleted');
} else {
console.log('No existing dev project found so nothing to cleanup');
}
console.log(`Creating new project named: ${projectName}`);
const { data: newProject } = await posthogApi.post<ProjectFull>(
'/projects',
createProjectObject({
name: projectName,
completed_snippet_onboarding: true,
access_control: realProject.access_control,
app_urls: realProject.app_urls,
anonymize_ips: realProject.anonymize_ips,
slack_incoming_webhook: realProject.slack_incoming_webhook,
timezone: realProject.timezone,
test_account_filters: realProject.test_account_filters,
test_account_filters_default_checked:
realProject.test_account_filters_default_checked,
path_cleaning_filters: realProject.path_cleaning_filters,
person_display_name_properties:
realProject.person_display_name_properties,
data_attributes: realProject.data_attributes,
correlation_config: realProject.correlation_config,
session_recording_opt_in: realProject.session_recording_opt_in,
// primary_dashboard: realProject.primary_dashboard,
live_events_columns: realProject.live_events_columns,
recording_domains: realProject.recording_domains
})
);
// await axios.post('https://app.posthog.com/capture', {
// api_key: newProject.api_token,
// event: 'Emulation Setup',
// properties: propertyDefinitions.results.map(({ name, property_type }) => {
// let stub: any;
// if (property_type === 'DateTime') {
// stub = new Date().toISOString();
// } else if (property_type === 'String') {
// stub = 'stub';
// } else if (property_type === 'Numeric') {
// stub = 1;
// } else if (property_type === 'Boolean') {
// stub = true;
// } else {
// throw new Error(`Unknown property type: ${property_type}`);
// }
// return [name, stub];
// })
// });
console.log('Creating cohorts');
const cohortMapping: Record<number, number> = {};
for (const cohort of cohorts.results) {
if (cohort.deleted) {
continue;
}
const { data: newCohort } = await posthogApi.post<Cohort>(
`/projects/${newProject.id}/cohorts`,
{
name: cohort.name,
description: cohort.description,
groups: cohort.groups,
filters: cohort.filters,
is_static: cohort.is_static
}
);
cohortMapping[cohort.id] = newCohort.id;
}
const experimentMapping: Record<number, number> = {};
console.log('Creating experiments');
for (const experiment of experiments.results) {
if (
new Date(experiment.end_date).getTime() < Date.now() ||
experiment.archived
) {
continue;
}
const { data: newExperiment } = await posthogApi.post<Experiment>(
`/projects/${newProject.id}/experiments`,
{
name: experiment.name,
description: experiment.description,
start_date: experiment.start_date,
end_date: experiment.end_date,
feature_flag_key: experiment.feature_flag_key,
parameters: experiment.parameters,
secondary_metrics: experiment.secondary_metrics,
filters: experiment.filters
}
);
experimentMapping[experiment.id] = newExperiment.id;
}
console.log('Creating feature flags');
const activeFeatureFlags: number[] = [];
for (const featureFlag of featureFlags.results) {
if (featureFlag.deleted) {
continue;
}
const { data: newFeatureFlag } = await posthogApi.post<FeatureFlag>(
`/projects/${newProject.id}/feature_flags`,
{
name: featureFlag.name,
key: featureFlag.key,
filters: Object.fromEntries(
Object.entries(featureFlag.filters).map(([key, value]) => {
let finalValue: any = value;
if (key === 'groups') {
finalValue = value.map(
(group: {
properties: Array<{
key: string;
type: string;
value: any;
operator: any;
}>;
}) => {
const newGroup = { ...group };
newGroup.properties = newGroup.properties.map((property) => {
const newProperty = { ...property };
if (newProperty.type === 'cohort') {
newProperty.value = cohortMapping[newProperty.value];
}
return newProperty;
});
return newGroup;
}
);
}
return [key, finalValue];
})
),
active: false,
ensure_experience_continuity: featureFlag.ensure_experience_continuity
}
);
if (featureFlag.active) {
activeFeatureFlags.push(newFeatureFlag.id);
}
}
const client = new PostHog(newProject.api_token);
console.log('Creating events');
client.identify({
distinctId: 'local_dev_script',
properties: {
email: '[email protected]'
}
});
client.capture({
distinctId: 'local_dev_script',
event: 'Emulation Setup'
});
await client.shutdownAsync();
// This still doesn't work... The flag and in the active state (according to the UI) but it doesn't actually work
console.log('Activating feature flags');
for (const featureFlagId of activeFeatureFlags) {
await posthogApi.patch(
`/projects/${newProject.id}/feature_flags/${featureFlagId}`,
{
active: true
}
);
}
console.log('Reading raw `.env` file');
const envFileContent = await readFile(pathToEnvFile, 'utf8');
console.log('Updating `.env` file');
const envFileUpdated = [
envFileContent
.trim()
.replace(/^POSTHOG_PERSONAL_PROJECT_ID=\w+\s*$/gm, '')
.replace(/^POSTHOG_PERSONAL_PROJECT_API_TOKEN=\w+\s*$/gm, '')
.trim(),
`POSTHOG_PERSONAL_PROJECT_ID=${newProject.id}`,
`POSTHOG_PERSONAL_PROJECT_API_TOKEN=${newProject.api_token}`,
''
].join('\n');
await writeFile(pathToEnvFile, envFileUpdated, 'utf8');
console.log('Done');
}
const pe = new PrettyError();
function logError(err: any) {
if (err instanceof Error === false) {
err = new Error(err);
}
console.error(pe.render(err));
if (axios.isAxiosError(err)) {
const { code, name, message, status, response } = err;
const { data } = response || {};
console.error({
status,
code,
name,
message,
data
});
}
}
try {
main().catch((err) => {
logError(err);
process.exit(1);
});
} catch (err) {
logError(err);
process.exit(1);
}
```
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/12853 | https://github.com/PostHog/posthog/pull/12919 | 5764ffd4175f25f9927f06a3a0204d1e189bd047 | 635498cea4faa48619547f100c8fe32e9ca66fe8 | "2022-11-17T18:24:40Z" | python | "2022-11-23T00:32:43Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 12,800 | ["ee/clickhouse/views/test/__snapshots__/test_clickhouse_trends.ambr", "posthog/queries/breakdown_props.py", "posthog/queries/person_query.py", "posthog/queries/test/__snapshots__/test_trends.ambr", "posthog/queries/test/test_trends.py", "posthog/queries/trends/breakdown.py", "posthog/queries/trends/sql.py", "posthog/queries/trends/total_volume.py", "posthog/queries/trends/trends_event_query.py", "posthog/queries/trends/util.py"] | Monthly active users metric wrong when using Number as chart type | ## Bug description
Monthly Active Users metric seems wrong when choosing "# Number" as chart type.
Number:
Line chart:
**490 != 70**
## How to reproduce
1. Create a new insight using any event and the "Monthly active users" metric
2. Date range = This month + Grouped by = Day
3. Choose chart type as Number => remember value
4. Change chart type as Linear => check last data point
=> the 2 values do not match
=> in other words there's a diff between a total aggregation and an aggregation per bucket of time ?
## Environment
- [x] PostHog Cloud | https://github.com/PostHog/posthog/issues/12800 | https://github.com/PostHog/posthog/pull/13131 | 4635648eb0e25f671f84d576184c288abb8b91f1 | 777fa5a3156e29b3b4e772da1d4b23916398b866 | "2022-11-15T17:06:53Z" | python | "2022-12-05T18:51:35Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 12,712 | ["frontend/src/scenes/ingestion/v2/IngestionWizard.tsx", "frontend/src/scenes/ingestion/v2/ingestionLogic.ts", "frontend/src/scenes/ingestion/v2/panels/TeamInvitedPanel.tsx", "frontend/src/scenes/organization/Settings/inviteLogic.ts"] | Onboarding V2: After inviting a technical user to help, prompt them to explore the product | **As a** non-technical user,
**I'd like to** be able to explore the product before the engineering team implements it,
**so that** I can figure out if it's the right solution for us.
### Details
We now ask if someone is technical at the beginning of onboarding. If they are not technical, they still should be able to explore PostHog to see if it's the right fit for them before they invite their team, or before their team has time to install it.
| https://github.com/PostHog/posthog/issues/12712 | https://github.com/PostHog/posthog/pull/12731 | 848a7754352b7eccca960b0add9bcd9d9a1cca1a | 4133379be230d62a405787d2cf09af14da65ea8a | "2022-11-09T17:22:21Z" | python | "2022-11-10T16:12:23Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 12,645 | ["frontend/src/lib/components/Cards/TextCard/TextCardModal.tsx", "frontend/src/lib/components/PayGateMini/PayGateMini.tsx", "frontend/src/lib/constants.tsx", "frontend/src/scenes/dashboard/DashboardHeader.tsx", "posthog/settings/feature_flags.py"] | Missing upsell prompt for dashboard text cards | ## Bug description
I was super confused why I can't add text cards to a dashboard locally… turns out that's a paid feature, which is not communicated in the product, and I happened not to have a license. This is suboptimal in two cases:
1. User is not aware we've built text cards – it's very unlikely they'll learn about this feature
2. User is aware we've built text cards, but for some reason doesn't currently have a subscription – they'll be confused why the feature's suddenly gone with the wind (like me)
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/12645 | https://github.com/PostHog/posthog/pull/12729 | accbe412f6602f9746bf17ffef7b8eff8f17810a | 8891aea77e909f0e8cfe781e611bf3ab65aa686f | "2022-11-07T12:03:26Z" | python | "2022-11-14T17:53:51Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 12,617 | ["posthog/api/session_recording.py", "posthog/api/test/__snapshots__/test_session_recordings.ambr", "posthog/api/test/test_session_recordings.py"] | N+1 Query: SELECT "posthog_persondistinctid"."distinct_id" FROM "posthog_persondistinctid" WHERE ("posthog_persondistinctid"."person_id" = %s AND "posthog_persondistinctid"."team_id" = %s) ORDER BY "posthog_persondistinctid"."id" ASC | Sentry Issue: [POSTHOG-821](https://sentry.io/organizations/posthog/issues/3707400683/?referrer=github_integration)
Sentry is reporting that when listing session recordings loading persons is n+1
Looking at how the query works
we
* load person distinct ids for recordings in the list
* load the persons that have those distinct ids
* create a fict of distinct id to person
* for each of the recordings
* look up the person in the dict and pass them to a `PersonSerializer`
* that looks up the person's distinct ids while choosing Person's `name`
* (maybe only when there's no email) in order to determine the first distinct id for the person
That final lookup of distinct ids is (**I think**) where the n plus 1 problem is.
For each person one at a time we go to the DB and get their distinct ids
There's no foreign key from `Person` to `PersonDistinctId` so we can't utilise `select_related` here.
_maybe_ we can if we use a list serializer for Persons and then combine the two lists
Some of the reports suggest 50% of the time generating the list is spent loading persons | https://github.com/PostHog/posthog/issues/12617 | https://github.com/PostHog/posthog/pull/13573 | a895b3fc46a14396e1499ca503de287015bb9198 | fbd650dd2084f5d67e0ec084e049da5407179a62 | "2022-11-03T18:25:44Z" | python | "2023-01-10T09:57:42Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 12,588 | ["frontend/src/scenes/instance/SystemStatus/systemStatusLogic.ts"] | Load instance settings on reduce Instance settings failed: You are not a staff user, contact your instance admin | ## Bug description
I see the following everytime I refresh the page on app.posthog.com:
<img width="541" alt="Screenshot Homepage • PostHog (Google Chrome) 2022-11-03 at 08 54@2x" src="https://user-images.githubusercontent.com/22766134/199680522-7ef9afea-6577-4812-ab63-2618a07ef3fe.png">
<img width="1728" alt="Screenshot Homepage • PostHog (Google Chrome) 2022-11-03 at 08 56@2x" src="https://user-images.githubusercontent.com/22766134/199680779-f62fd8fd-3e68-44b3-8ffd-dc66b0696a0c.png">
Here's the request:
<img width="1073" alt="Screenshot Homepage • PostHog (Google Chrome) 2022-11-03 at 08 57@2x" src="https://user-images.githubusercontent.com/22766134/199680946-f99cf7fd-ba89-476c-9446-2cf268c4f19d.png">
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog, version/commit: please provide
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/12588 | https://github.com/PostHog/posthog/pull/12590 | b2da30a686ef8ed2aea451e32d0bf4b9a806307b | e91c4a7e1b38740ab0e3249bfcfca81719ac2a1e | "2022-11-03T08:57:23Z" | python | "2022-11-03T10:32:45Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 12,539 | ["frontend/src/lib/components/LemonModal/LemonModal.scss", "frontend/src/lib/components/LemonModal/LemonModal.tsx", "frontend/src/lib/components/UnitPicker/CustomUnitModal.tsx", "frontend/src/lib/components/UnitPicker/UnitPicker.tsx", "frontend/src/lib/constants.tsx", "frontend/src/styles/vars.scss"] | Y-axis unit blocks screen | ## Bug description
Sometimes the Y-axis randomly opens for me and then blocks the screen which is super frustrating. The y-axis dropdown is the only one that does this.
<img width="1144" alt="image" src="https://user-images.githubusercontent.com/1727427/199070208-9efe4f86-6818-4712-99ec-2eeada7eee4d.png">
## How to reproduce
1. Click on the y-axis
2. Try exiting it by clicking anywhere else on the screen
3. Get a `confirm()` box which blocks everything.
4. One way of getting out of this is pressing the escape key. Weirdly, if you press the escape key again the box opens again. Feels like a listener gone rogue.
## Environment
- [ ] PostHog Cloud
- [ ] self-hosted PostHog, version/commit: please provide
## Additional context
@Twixes
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/12539 | https://github.com/PostHog/posthog/pull/12536 | 6babc16815f065aa29ab5c74984525aae8fda41a | 47d7a6a27ce6c3f306f1fd5413c0f8ee19e41799 | "2022-10-31T17:24:42Z" | python | "2022-11-02T12:42:57Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 12,535 | ["frontend/src/lib/components/LemonModal/LemonModal.scss", "frontend/src/lib/components/LemonModal/LemonModal.tsx", "frontend/src/lib/components/UnitPicker/CustomUnitModal.tsx", "frontend/src/lib/components/UnitPicker/UnitPicker.tsx", "frontend/src/lib/constants.tsx", "frontend/src/styles/vars.scss"] | Bug: Unit selection modal hard to dismiss | ## Bug description
Most modals, such as the date selector modal, can be de-selected by clicking anywhere on the screen outside the modal. E.g. If I see this, and click on the blue area of the pie chart, it disappears.
<img width="707" alt="Screenshot 2022-10-31 at 15 38 26" src="https://user-images.githubusercontent.com/84011561/199048475-a060e109-24cf-489e-9d0a-4a5686dcccb3.png">
This isn't true with the unit selector. If I see this and click anywhere on the screen, the modal stays open. The only way to close it is to click 'Unit' again.
<img width="600" alt="Screenshot 2022-10-31 at 15 38 41" src="https://user-images.githubusercontent.com/84011561/199048556-d51ec434-f830-49a1-81f7-29fdfd08d531.png">
And this behavior can lead to some broken UI, eg:
<img width="1172" alt="Screenshot 2022-10-31 at 15 40 45" src="https://user-images.githubusercontent.com/84011561/199048679-d5e5a494-d975-4680-a9b6-087967721e7f.png">
## How to reproduce
1. Click 'Unit' on an insight
2. Click anywhere else.
3.
## Environment
- [ ] PostHog Cloud
- [ ] self-hosted PostHog, version/commit: please provide
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/12535 | https://github.com/PostHog/posthog/pull/12536 | 6babc16815f065aa29ab5c74984525aae8fda41a | 47d7a6a27ce6c3f306f1fd5413c0f8ee19e41799 | "2022-10-31T15:41:29Z" | python | "2022-11-02T12:42:57Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 12,534 | ["frontend/src/scenes/dashboard/Dashboards.tsx", "frontend/src/scenes/dashboard/dashboardsLogic.ts"] | Request: Find dashboards by me | ## Is your feature request related to a problem?
Last week I made a dashboard. I can't remember what I called it. Now I can't find it because, while I can find pinned or shared dashboards, I can't find 'My dashboards'.
<img width="346" alt="Screenshot 2022-10-31 at 15 31 04" src="https://user-images.githubusercontent.com/84011561/199046766-f0724b88-399f-495a-8d33-432093e00b76.png">
This would be less annoying if I was called Andy or Yakko, because then I could sort by 'Created by' and look at one end of the list. Alas, 'Joe' exists squarely in the center of the alphabet.
## Describe the solution you'd like
A third tab, next to Pinned and Shared, which lets me see dashboards made by me only.
## Describe alternatives you've considered
Something something tags
## Additional context
For now, I'm just going to recreate the dashboard instead of looking.
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/12534 | https://github.com/PostHog/posthog/pull/12537 | 5aafc7a115309eb24910c03dcb421418bd38cb3b | 878a014be4a559cc1ec5b7117edd4d202df5b80f | "2022-10-31T15:34:04Z" | python | "2022-10-31T19:42:31Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 12,510 | ["frontend/src/scenes/funnels/funnelLogic.ts", "frontend/src/scenes/insights/utils/cleanFilters.test.ts", "frontend/src/scenes/insights/utils/cleanFilters.ts", "frontend/src/types.ts"] | Can't save funnel conversion rate calculation setting | ## Bug description
*Please describe.*
*If this affects the front-end, screenshots would be of great help.*
Unless I'm missing something, it's impossible to change the funnel rate calculation setting then **save** that change.
## How to reproduce
1. Open an existing funnel.
2. Click on "Conversion rate calculation" dropdown and change it.
3. Notice that the Save button says "No Changes to be Saved", and even if you change something else in the funnel and save changes, a change to the setting for "conversion rate calculation" is not saved, as you can see when the page is reloaded.
## Environment
- [X ] PostHog Cloud
- [ ] self-hosted PostHog, version/commit: please provide
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/12510 | https://github.com/PostHog/posthog/pull/12598 | 9f74d8c4630dbc73ed53d58496e2187fb8e6d436 | 21dff704a34fc4e06ba46fcd25cdca020a9a65e9 | "2022-10-28T18:07:42Z" | python | "2022-11-03T13:32:03Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 12,460 | ["frontend/src/scenes/funnels/FunnelCanvasLabel.tsx", "frontend/src/scenes/funnels/funnelLogic.ts", "frontend/src/scenes/insights/views/Funnels/FunnelCorrelation.tsx", "frontend/src/scenes/insights/views/Funnels/FunnelCorrelationTable.tsx", "frontend/src/scenes/insights/views/Funnels/FunnelPropertyCorrelationTable.tsx"] | Funnels with 1 user show 100% conversion when they should show 0% | ## Bug description
This funnel should show 0% conversion in the top right, but some bad rounding(?) causes it to show 100%
Note that funnels with more users appear to be calculating this correctly, so it's an anomaly related to the logic for computing this, possibly related to catching a division by zero error?
## How to reproduce
1. setup a funnel with some filters such that only one person enters and completes stage two, but never completes stage three
2.
3.
## Environment
- [ ] PostHog Cloud
- [ ] self-hosted PostHog, version/commit: please provide
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/12460 | https://github.com/PostHog/posthog/pull/12470 | 083d13b2d06f962b51290e19b1006f3da1b75383 | 69647a2b6148124abd7a8b28afebc8e464c2ea6c | "2022-10-26T23:26:55Z" | python | "2022-10-28T07:57:59Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 12,354 | ["frontend/src/lib/components/InsightLabel/InsightLabel.scss", "frontend/src/lib/components/InsightLabel/index.tsx", "frontend/src/scenes/insights/InsightTooltip/InsightTooltip.scss", "frontend/src/scenes/insights/InsightTooltip/InsightTooltip.tsx", "frontend/src/scenes/insights/views/LineGraph/lineGraphLogic.ts", "frontend/src/styles/utilities.scss"] | Insights with a group by sometimes resulting in a NaN | ## Bug description
When doing an insight and grouping by more than a day it sometimes results in a NaN showing in either the table below or when hovering over the insight
## How to reproduce
You can see it at this insight: https://app.posthog.com/insights/iULRRRFR
<img width="586" alt="Screenshot feature flag updated unique users feature flag created unique users by person's clearbit__person__employment__role • Insights • PostHog (Google Chrome) 2022-10-19 at 14 28@2x" src="https://user-images.githubusercontent.com/22766134/196774536-c40f1fee-d672-4bae-a4af-3ac8e8772317.png">
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog, version/commit: please provide
cc @PostHog/team-product-analytics
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/12354 | https://github.com/PostHog/posthog/pull/12423 | 78379f09c696d41537786dd9f6b818dba4b3e685 | c192d8add79a4b9aaf0d90c6378177fdd63cb959 | "2022-10-19T18:30:02Z" | python | "2022-10-25T14:44:44Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 12,288 | ["frontend/src/scenes/insights/EditorFilters/TrendsSeries.tsx"] | Can't add variable for forumla using Big Number view | ## Bug description
Tried to create a formula for a nice big number but it seems impossible to add a variable when in this view mode
## How to reproduce
1. Create an insight with view "Big Number"
2. There is no "add variable" button
3.
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog, version/commit: please provide
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/12288 | https://github.com/PostHog/posthog/pull/12291 | a99ca709dbe8fb4eedd2f2a734055486933e6f95 | 24d0c7eeffe2225e8c40ff00c3589b1e7cad7add | "2022-10-17T11:32:23Z" | python | "2022-10-17T12:32:55Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 12,210 | ["posthog/api/insight.py"] | Accessing insight from API returns null | ## Bug description
From [a customer report](https://posthoghelp.zendesk.com/agent/tickets/653):
```
I'm accessing insight results through the API, and I’ve noticed that sometimes the result is null in the response.
When I go and view the insight in Posthog and tap “refresh” the result starts to return in the API response.
I’ve also noticed there is a “refreshing” boolean flag in the insight response.
How do I set the insight to either refresh periodically or on request so I always get a result through the API?
```
It seems like the insight returns null if it's not refreshed manually from the frontend.
## How to reproduce
1. Call an insight with GET | /api/projects/:project_id/insights/:id
2. Response is `null`
3. Refresh the insight from the frontend
4. Response is populated
## Environment
- [ ] PostHog Cloud
- [ ] self-hosted PostHog, version/commit: please provide
## Additional context
| https://github.com/PostHog/posthog/issues/12210 | https://github.com/PostHog/posthog/pull/12212 | fffe2770417a7be0308cf9f3ab1069b514cba5cf | 75d3bf5dee05152857c547975bba35b38b8d06d8 | "2022-10-12T09:45:16Z" | python | "2022-10-12T10:13:49Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 12,208 | ["frontend/src/scenes/funnels/FunnelBarGraph.tsx"] | Bug: Persons not clickable on 'Top to bottom' funnel view | ## Bug description
It's no longer possible to click on the persons total on the 'top to bottom' funnel view to see the persons modal. This used to work and works correctly on the 'left to right' view. See video:
https://user-images.githubusercontent.com/92976667/195295629-b8c986d6-3df8-419a-bba4-6ba2732efa97.mov
## How to reproduce
1. Load a funnel insight
2. Click on the thingy
3. Make sad face
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog, version/commit: please provide
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/12208 | https://github.com/PostHog/posthog/pull/12332 | b33347205cf473296fdc2025c01c29c63487d892 | 8c9b26df2f3fdadc25b6c9858d5943cfca70cd50 | "2022-10-12T08:45:45Z" | python | "2022-10-19T10:34:22Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 11,916 | ["frontend/src/scenes/scenes.ts"] | You can get to the password reset screen even if you are logged in | ## Bug description
There is no security issue here but it is just weird that you can technically go to the password reset screen even if you are currently logged in.
## How to reproduce
1. In an private tab request a password reset
2. Click the reset link (or click here [https://app.posthog.com/reset/foo/bar](https://app.posthog.com/reset/foo/bar) )
3. You get to the password reset screen despite being loggedin
No biggy but we should probably redirect away or at least tell the user they are already logged in
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog, version/commit: please provide
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/11916 | https://github.com/PostHog/posthog/pull/11928 | f68846de828a3ffd21a5b9acb6877d6ba28b881a | 4fbea5baa3ee5fe111bfad35e04588d5f1ab62d8 | "2022-09-21T16:22:58Z" | python | "2022-09-22T14:23:35Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 11,895 | ["ee/clickhouse/views/test/__snapshots__/test_clickhouse_trends.ambr", "posthog/queries/trends/test/__snapshots__/test_breakdowns.ambr", "posthog/queries/trends/test/__snapshots__/test_formula.ambr", "posthog/queries/trends/util.py"] | Product insights: All formulas are resulting in an error | The bar chart shows normally however when I enter a formula the query errors.
See the following video for steps to reproduce: https://share.cleanshot.com/gYbA6F
Link to the insight: https://app.posthog.com/insights/eswxiLCU/edit | https://github.com/PostHog/posthog/issues/11895 | https://github.com/PostHog/posthog/pull/11909 | fcdf313e63fec19571df4eb27b44060c9b762362 | cc2db2e469e29f60601737d2c0152a706dae8ab0 | "2022-09-20T13:47:46Z" | python | "2022-09-22T14:58:24Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 11,878 | ["frontend/src/scenes/insights/views/LineGraph/LineGraph.tsx"] | Scroll bars on dashboards | ## Bug description
Since developers are using macs, we often forget about overflows and scroll bars, leading to issues like below.
## How to reproduce
https://app.posthog.com/dashboard/26574
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog, version/commit: please provide
## Additional context
cc @mariusandra for bug bashing prioritization
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/11878 | https://github.com/PostHog/posthog/pull/11890 | 91a43ea413f262bb55403fbab281508d86cd8c64 | e5d52e0d20d11d6d05ddf37d1827638dd169782e | "2022-09-20T06:23:13Z" | python | "2022-09-20T12:48:21Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 11,872 | ["frontend/src/scenes/funnels/FunnelBarChart.tsx", "frontend/src/scenes/funnels/funnelLogic.ts", "frontend/src/scenes/funnels/funnelUtils.ts", "frontend/src/scenes/insights/Insight.scss", "frontend/src/scenes/insights/InsightContainer.tsx", "frontend/src/scenes/insights/insightLogic.test.ts", "frontend/src/scenes/insights/insightLogic.ts", "frontend/src/scenes/insights/views/Funnels/FunnelStepsTable.tsx"] | Funnel bars not showing for first funnel stage on cohort breakdown for some teams | ## Bug description
funnel bars are not appearing as expected. This persists even if I remove cohort breakdowns
<img width="866" alt="image" src="https://user-images.githubusercontent.com/56287180/191066215-84d245bc-4f93-445c-9aa8-a872b9d34695.png">
not sure exactly how to repro this state, but on 2299 you can see it [here](https://app.posthog.com/insights/KbalvGPj). I've tried just breaking down by 6 + cohorts, but no luck there. There are some 4xx responses from `/decide` I see, but unsure if related.
## How to reproduce
1. ???
2.
3.
## Environment
- [ ] PostHog Cloud
- [ ] self-hosted PostHog, version/commit: please provide
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/11872 | https://github.com/PostHog/posthog/pull/12113 | e540a53d31626a77f1d63a7746d565df8b0c32fd | 50727dd4c66c5aacd11a43feca8d1b6267ccd9e3 | "2022-09-19T16:36:29Z" | python | "2022-10-06T12:28:07Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 11,863 | ["frontend/src/lib/components/InsightLegend/InsightLegend.scss", "frontend/src/lib/components/InsightLegend/InsightLegend.tsx", "frontend/src/scenes/insights/insightLogic.ts", "frontend/src/scenes/insights/views/LineGraph/LineGraph.tsx", "frontend/src/scenes/insights/views/LineGraph/PieChart.tsx", "frontend/src/scenes/trends/trendsLogic.ts", "frontend/src/scenes/trends/viz/ActionsPie.scss", "frontend/src/scenes/trends/viz/ActionsPie.tsx"] | Dashboards: Allow showing pie chart legend | ## Is your feature request related to a problem?
From a user:
> On the details page of the insight (currently specifically the pie chart), I can choose whether to show the legend or not. I would like to know if there is or can be added an option to allow viewing the legend of the pie chart on the dashboard page.
>
> Currently I need to use mouse hover to see the data labels corresponding to the different sections.
## Describe the solution you'd like
Allow toggling the legend. Note that the legend might be automatically shown if the panel is large enough or hidden if it's too small.
## Additional context
cc @Twixes as feature owner
Ref: https://squeak.cloud/question/207
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/11863 | https://github.com/PostHog/posthog/pull/12248 | 0c34a2ab3bd7231dbd9b1632a4b892f2e428c780 | fe47e17511c6bea3f9811924a8bf0a94afb1671f | "2022-09-19T08:01:22Z" | python | "2022-10-14T14:47:14Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 11,856 | ["frontend/src/lib/components/ObjectTags/ObjectTags.tsx", "frontend/src/lib/components/ObjectTags/objectTagsLogic.test.ts", "frontend/src/lib/components/ObjectTags/objectTagsLogic.ts"] | Error when adding tags to dashboards | ## Bug description
When adding a tag to a dashboard, selecting an autocompleted result applies the partially entered text instead – e.g. if I type `mar` and then selection `marketing` from the dropdown, it'll apply the tag as `mar`. See video
https://user-images.githubusercontent.com/92976667/190686626-b31adcf1-197d-47bc-853f-1811b25c129d.mov
## How to reproduce
1. Open dashboard
2. Attempt to add existing tag
3. Select autocomplete result
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog, version/commit: please provide
## Additional context
n/a
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/11856 | https://github.com/PostHog/posthog/pull/12279 | e38824c3aa229d5fc4d5c0a47464d2613c73952b | aabd22c8a42ade9ab40d6025df3245c33d51cc1c | "2022-09-16T16:32:25Z" | python | "2022-10-17T10:44:18Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 11,837 | ["frontend/src/scenes/insights/views/InsightsTable/InsightsTable.tsx"] | select all/none button on tables | ## Is your feature request related to a problem?
in (insights) tables the checkbox values are tedious as I tend to sometimes want to drill down on only a few rows which can require a lot of clicks
## Describe the solution you'd like
a button in the header bar to select all/none
## Describe alternatives you've considered
## Additional context
select/unselect checkbox values seem to be persisted on (insghts) tables which means even a reload does not help
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/11837 | https://github.com/PostHog/posthog/pull/11945 | efe92f7dd31a52ad3df4b862fee326d694213023 | 9bd09448021d30d981dee1b36e4900f77fb9a7f3 | "2022-09-15T15:25:46Z" | python | "2022-09-23T10:46:57Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 11,678 | ["frontend/src/lib/components/AnnotationsOverlay/AnnotationsOverlay.scss", "frontend/src/lib/components/AnnotationsOverlay/AnnotationsOverlay.tsx", "frontend/src/lib/components/AnnotationsOverlay/annotationsOverlayLogic.ts", "frontend/src/lib/components/Popup/Popup.tsx", "frontend/src/styles/vars.scss"] | Annotation popups are hidden behind insight cards | ## Bug description
Annotation popups are hidden behind insight cards headers, in dashboards.
<img width="613" alt="image" src="https://user-images.githubusercontent.com/7335343/188629629-cfafe8fb-3d3b-45ca-bf04-09a57e477f13.png">
## How to reproduce
1. Create a dashboard
2. Create an insight with annotations
3. Try to hover over an annotation
## Environment
- [X] PostHog Cloud
- [ ] self-hosted PostHog, version/commit: please provide
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/11678 | https://github.com/PostHog/posthog/pull/11688 | dc32a8aa86bdf328bf58b03fa68dcac0178d7bc8 | a063f602241eee92cee74eed00ce1c84703cb936 | "2022-09-06T11:59:14Z" | python | "2022-09-08T15:26:42Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 11,646 | ["frontend/src/scenes/funnels/useFunnelTooltip.tsx", "frontend/src/styles/vars.scss"] | Regression: Tooltips are lacking a contrasting background | ## Bug description
Tooltips should have a white background to contrast with the underlying content.
## How to reproduce
1. Create a funnel
2. Add steps
3. Hover the funnel and observe that the tooltip background is transparent
## Environment
- [ ] PostHog Cloud
- [ ] self-hosted PostHog, version/commit: please provide
## Additional context
- [Slack thread](https://posthog.slack.com/archives/C0368RPHLQH/p1662142082123639)
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/11646 | https://github.com/PostHog/posthog/pull/11648 | 9ecfe221c9e05295218eb1d8511360cf2e1f0993 | e80587754d960f45c6ec41f32d6365f95a150faf | "2022-09-02T18:09:27Z" | python | "2022-09-05T07:10:19Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 11,635 | ["frontend/src/models/dashboardsModel.tsx", "frontend/src/scenes/dashboard/dashboardLogic.test.ts", "frontend/src/scenes/dashboard/dashboardLogic.tsx"] | Last updated on dashboard is slow to update | ## Bug description
When i update all charts on a dashboard the "Last Updated" thingy does not itself actually update. Often i refresh all charts - jump around and maybe end up back and original dashboard where last updated might still say 3 days ago - even though i just updated it. I get confused then and just press to update again (im not sure then if i can trust that the actual charts are based on the updated data i just did - i think they are). This can then be slow if im needlessly updating a dash with like 20 charts.
## How to reproduce
1. go to a medium sized dashboard you use regulalry
2. update it
3. see if the last updated changes
## Environment
- [X] PostHog Cloud
- [ ] self-hosted PostHog, version/commit: please provide
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/11635 | https://github.com/PostHog/posthog/pull/12271 | 3e1ab7c2a5311f6384a96c6bb1d7e97fb779c247 | 82c201a5f6550123acaf235cd16a83928e97bc7b | "2022-09-02T11:18:42Z" | python | "2022-10-18T10:11:49Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 11,551 | ["frontend/src/lib/components/EditableField/EditableField.scss", "frontend/src/lib/components/EditableField/EditableField.stories.tsx", "frontend/src/lib/components/EditableField/EditableField.tsx", "frontend/src/scenes/insights/Insight.tsx", "frontend/src/scenes/insights/insightLogic.ts", "frontend/src/scenes/saved-insights/savedInsightsLogic.ts"] | Having to save title changes as well as insight changes can be confusing | ## Bug description
https://posthogusers.slack.com/archives/CTLTM70RM/p1661521059037479
i often add a title in here, forget to press save on the title, then save the insight itself. And then end up with strange names. I'd expect that when i type into the title box, clicking anywhere else on the screen is same as clicking save.
having to save the title name and then save the insight sometimes is strange.
## How to reproduce
1.
2.
3.
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog, version/commit: please provide
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/11551 | https://github.com/PostHog/posthog/pull/11552 | 48bf038bc6ffe692a914f8594f54f24c1d11508f | 87cd298599e4c7f43e991f84a1e5074f83c9c3a4 | "2022-08-30T13:05:35Z" | python | "2022-08-31T19:58:05Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 11,521 | ["frontend/src/scenes/events/eventsTableLogic.test.ts", "frontend/src/scenes/events/eventsTableLogic.ts"] | Events for a single person won't load | ## Bug description
Selecting the Events Tab in a single Persons view to see the events for this specific user, will lead to an infinite loading screen.
<img width="1440" alt="Bildschirmfoto 2022-08-26 um 16 56 01" src="https://user-images.githubusercontent.com/6574869/186933646-aa201310-c1c4-40ef-9757-93750a6e1c76.png">
## How to reproduce
1. Open PostHog
2. Click on [Persons & Groups](https://app.posthog.com/person/)
3. Select any person
4. Move to the Events tap
5. You will see an infinity loading screen
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog, version/commit: please provide
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/11521 | https://github.com/PostHog/posthog/pull/11585 | c09d15917d1905149ccf191cfc88e04ae445428e | 5bc958dc31a32cdcf9c279f61a154477535a2e71 | "2022-08-26T14:59:32Z" | python | "2022-09-01T09:00:17Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 11,513 | ["frontend/src/toolbar/flags/featureFlags.scss"] | Toolbar feature flag multivariate contrast | ## Bug description
Moving to strong primary colors changed this:
<img width="473" alt="image" src="https://user-images.githubusercontent.com/53387/186881664-3e3e8ed0-895d-400d-a2f9-45ecd7a7aef2.png">
We should remove the background color from the selected multivariate option. We can use a blue left border to indicate selection, or just keep it bold.
## Environment
- [ ] PostHog Cloud
- [ ] self-hosted PostHog, version/commit: please provide
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/11513 | https://github.com/PostHog/posthog/pull/11671 | 4cd07041dd181b98411d655e7aeb02858407a931 | 8b5a65112eb773f6f1fad22390f18ab6cb7823da | "2022-08-26T10:11:32Z" | python | "2022-09-06T09:04:10Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 11,400 | ["frontend/src/scenes/insights/EmptyStates/EmptyStates.tsx"] | Insight keyword filter - empty state doesn't match context | ## Bug description
When you filter the list of insishts such that there aren't any matching results, the empty state shown doesn't really align to the context. The header is accurate to this context, but the rest of the empty state content is more targeted towards creation.
<img width="1144" alt="Screen Shot 2022-08-19 at 11 22 52 AM" src="https://user-images.githubusercontent.com/254612/185683369-7620a181-afa4-4388-b1e3-5123e2151456.png">
Ideally this empty state would guide the user on how to find what they're looking for, not push them to create something new. The insight count should also reflect that there are no matching insights, not that there are "no insights yet".
An example of content that would be more targeted in this scenario:
```
Header: No insights matched your search for "[keyword]"
Description: Refine your keyword search, or try using other filters such as type, last modified, created or by.
```
## How to reproduce
1. Go to insights
2. Filter the list on a non-matching keyword
3. Observe the empty state content
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog, version/commit: please provide
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/11400 | https://github.com/PostHog/posthog/pull/13645 | 14b90977b8b4ed59768aaa7423043c925c940a1a | 96785e5334344131f72d96285b9b3867506bba26 | "2022-08-19T18:35:51Z" | python | "2023-01-19T16:16:32Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 11,337 | ["frontend/src/lib/components/PropertyKeyInfo.tsx"] | Icon position regression - Web performance | ## Bug description
Icons should be center aligned vertically and horizontally within a 24px square container.
<img width="312" alt="Screen Shot 2022-08-16 at 3 35 29 PM" src="https://user-images.githubusercontent.com/254612/184997075-897370f7-a2f3-4699-8455-59bc6f150ae5.png">
## How to reproduce
1. Go to web performance
2. Observe icon placement
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog, version/commit: please provide
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/11337 | https://github.com/PostHog/posthog/pull/11554 | 7146b492c3d82b6de49477f30ea3b7e3e77471fb | 1623b954637ba30fd05498332d557cab31f2a818 | "2022-08-16T22:37:50Z" | python | "2022-09-01T09:23:54Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 11,336 | ["frontend/src/lib/components/TaxonomicFilter/TaxonomicFilter.tsx"] | Insight builder - "foo" text in taxonomic filter placeholder attribute | ## Bug description
On the insight creation page, when selecting a graph series or funnel step, when you select a property or other value, the taxonomic filter placeholder attribute contains the value `Search events or calculated events foo`.
**Edit** it seems that the `foo` value is being appended to all taxonomic filter placeholder values. Some placeholder values are just so long that the `foo` isn't displayed prominently.
<img width="581" alt="Screen Shot 2022-08-16 at 2 22 23 PM" src="https://user-images.githubusercontent.com/254612/184987648-5b4935de-1b2f-4db9-a4ab-5f374a77a6f7.png">
The contents of the search placeholder vary based on the context of the taxonomic filter. Generally the placeholder should represent the scope of the categories the filter represents.
## How to reproduce
1. Create a new insight
2. Select an event or property or other value in the query builder
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog, version/commit: please provide
| https://github.com/PostHog/posthog/issues/11336 | https://github.com/PostHog/posthog/pull/11339 | dd82d54087c7c5d1ab7fcbac24092991a04fe1e5 | b051578f0b1e4b2051df50f4afaf2b75bf892cbc | "2022-08-16T21:27:35Z" | python | "2022-08-17T08:00:50Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 11,232 | ["frontend/src/scenes/insights/views/BoldNumber/BoldNumber.tsx"] | Card layouts are broken on cloud | ## Bug description
When viewing the list of insights if you select the card layout option you get an error.
<img width="1374" alt="Screen Shot 2022-08-10 at 9 10 46 AM" src="https://user-images.githubusercontent.com/254612/183960454-d514de0c-1671-4bd8-acdc-a5e69fb064e5.png">
## How to reproduce
1. View insights
2. Select card layout
3. See error
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog, version/commit: please provide
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/11232 | https://github.com/PostHog/posthog/pull/11235 | 4c3b8a2fd8b97d9f1c5326952a0d822981552b59 | 54623f2561d4ba780608db28ecbfea18ffaf44b2 | "2022-08-10T16:13:35Z" | python | "2022-08-10T19:42:22Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 11,214 | ["frontend/src/styles/global.scss"] | Accessibility: Button contrast | Not all of our button states pass color contrast checking (updated following #11223)
| | primary | danger | primary-alt | stealth |
|----------- |--------- |-------- |----------- |--------- |
| primary | | ❌ | | ❌ |
| secondary | | | | |
| tertiary | | | | |
## primary + danger
https://storybook.posthog.net/?path=/story/lemon-ui-lemon-button--default&args=type:primary;status:danger
`Element has insufficient color contrast of 4.26 (foreground color: #f4f6ff, background color: #db3707, font size: 10.5pt (14px), font weight: normal). Expected contrast ratio of 4.5:1`
## primary + stealth
https://storybook.posthog.net/?path=/story/lemon-ui-lemon-button--default&args=type:primary;status:stealth
`Element has insufficient color contrast of 1.07 (foreground color: #f4f6ff, background color: #ffffff, font size: 10.5pt (14px), font weight: normal). Expected contrast ratio of 4.5:1`
----------
Do the colours need to change? And/or are there combinations that shouldn't be allowed?
| https://github.com/PostHog/posthog/issues/11214 | https://github.com/PostHog/posthog/pull/11362 | 0aa85572629cb7ac623584a8a8deac59c530d88a | ada3f057010a3477d137e04dad1e7852b632fd50 | "2022-08-09T19:18:54Z" | python | "2022-08-18T09:43:28Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 11,167 | ["frontend/src/lib/components/ResizableTable/TableConfig.scss"] | column configurator background disappears when dragging | When dragging to reorder rows in the column configuration modal the background disappears while being dragged
Spotted while reviewing https://github.com/PostHog/posthog/pull/11093 but not introduced in that
## Reproduction steps
* visit the live events page
* click configure columns
* grab a row by its drag handle
* see its background disappear
| https://github.com/PostHog/posthog/issues/11167 | https://github.com/PostHog/posthog/pull/11556 | f40eb21cf45e544b8bdf975f01742fc7a39f1e1b | 84718c7beffa3dcd84c2feab79af5084a60fd9d9 | "2022-08-05T10:49:57Z" | python | "2022-08-31T12:20:38Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 11,131 | ["frontend/src/lib/components/ActivityLog/SentenceList.tsx", "frontend/src/lib/components/ActivityLog/activityLogLogic.feature-flag.test.tsx", "frontend/src/lib/components/PropertyFilters/components/PropertyFilterButton.scss", "frontend/src/scenes/feature-flags/FeatureFlags.tsx", "frontend/src/scenes/feature-flags/activityDescriptions.tsx"] | Property Pills stack vertically in ActivityLog Sentence Lists | ## Bug description
### viewed in feature flag
### viewed in history tab
When a change in the activity log has more than one property pill they stack vertically. They should stack horizontally. Ideally separated by commas using the `SentenceList` component.
## How to reproduce
* change a filter with more than one property in a feature flag
* view the activity log
## Environment
- [x] PostHog Cloud
- [x] self-hosted PostHog, version/commit: please provide
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/11131 | https://github.com/PostHog/posthog/pull/11263 | af1d6439ef8b81c28cf713cae9aad9ea62eaf6ef | d7bc9a5e212eba36ae197a6d6c0be35abb62e491 | "2022-08-04T08:56:10Z" | python | "2022-08-26T08:15:39Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 11,130 | ["posthog/api/insight.py", "posthog/api/test/test_insight.py"] | Favorite insights don't persist the ⭐ indication | ## Bug description
If I mark an insight as a favorite (⭐) and then refresh, the insight is no longer marked as a favorite although it is (can see it in Favorites).
<img width="390" alt="image" src="https://user-images.githubusercontent.com/30181361/182802236-9ecf0531-899c-4f25-ae86-bc233cefdc2f.png">
Note that I'm in the _Favorites_ tab and that _Bug example_ is not starred.
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog, version/commit: please provide
| https://github.com/PostHog/posthog/issues/11130 | https://github.com/PostHog/posthog/pull/11132 | d3e293cab97fb21df01881f204e1df4b4ac77217 | 291f2754cdb011d8db0c26116261ff73529c183a | "2022-08-04T08:34:58Z" | python | "2022-08-04T10:07:05Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 11,036 | ["frontend/src/scenes/persons/MergeSplitPerson.tsx", "frontend/src/scenes/persons/mergeSplitPersonLogic.ts", "posthog/api/person.py", "posthog/api/test/test_person.py"] | Merging persons doesn't work since persons endpoint stopped sending serial person ID | ## Bug description
It appears that merging people doesn't work since #10868, because the shape of a person returned by the persons endpoint turned from `{ ..., "uuid": "00000000-0000-0000-0000-000000000000", "id": 2 }` to `{ ..., "uuid": "00000000-0000-0000-0000-000000000000", "id": "00000000-0000-0000-0000-000000000000" }`. The `/merge` endpoint relies on the serial ID, and now that's not exposed (because this ID isn't even _known_ in ClickHouse).
## How to reproduce
1. Go to a random person.
2. Click "Split or merge IDs"
3. Select some other person(s) to merge into the current person
4. Notice that when you select persons, in the list they appear as some random numbers instead of distinct IDs – that's another symptom of the issue with UUIDs being returned instead of serial IDs.
<img width="198" alt="Screen Shot 2022-07-28 at 22 24 17" src="https://user-images.githubusercontent.com/4550621/181630574-88b4c029-706a-4134-ac62-a1d0001efd3c.png">
5. Click "Merge persons"
6. See success toast, but realize that actually nothing has happened
## Environment
- [x] PostHog Cloud
- [x] self-hosted PostHog (ClickHouse-based), version/commit: 1.38.0
## Additional context
This was reported by a user [on Slack](https://posthogusers.slack.com/archives/C01GLBKHKQT/p1658810378839129).
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/11036 | https://github.com/PostHog/posthog/pull/11038 | 3f62f01d5f19ed271076a655d49a3dd001f169c9 | 08e4489a2685ddcf65785adfe4af38286f3e27c1 | "2022-07-28T20:25:58Z" | python | "2022-07-28T20:59:30Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 10,921 | ["frontend/src/lib/components/TimezoneAware/index.scss", "frontend/src/lib/components/TimezoneAware/index.tsx", "frontend/src/scenes/dashboard/Dashboard.tsx"] | Wrong alignment / placement for dashboard filters | ## Bug description
The dashboard filter button is right aligned, but should be left aligned.
<img width="1021" alt="Screenshot 2022-07-21 at 16 50 54" src="https://user-images.githubusercontent.com/84011561/180258333-477cf996-d015-4d41-a198-6fa1e9cf6dee.png">
## How to reproduce
1. View a dashboard
2. Note the filter button placement
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/10921 | https://github.com/PostHog/posthog/pull/10978 | 859707eacf608b683d6a45c88c617c07d6f23aab | 135504963480ec5ef15d60d4bb94379a44b1d605 | "2022-07-21T15:24:28Z" | python | "2022-07-26T18:52:26Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 10,846 | ["frontend/src/styles/global.scss", "frontend/src/styles/vars.scss", "frontend/src/toolbar/Toolbar.stories.tsx", "frontend/src/toolbar/index.tsx", "frontend/src/toolbar/styles.scss"] | Toast issue in Toolbar | After saving actions, it looks like a toast notification shows up, but it's hard to read. And sometimes doesn't ever go away.
<img width="1511" alt="image" src="https://user-images.githubusercontent.com/154479/179528927-48f3e211-e987-4c35-af2d-7ec658de7eff.png">
## Repro
Define a couple actions in a row using the Inspect tool | https://github.com/PostHog/posthog/issues/10846 | https://github.com/PostHog/posthog/pull/11494 | 24873cc02fa8c7aec748868d6db69cbfc72984c3 | 4f1051512b418400514dd368da99c704aca15aa8 | "2022-07-18T14:04:08Z" | python | "2022-08-25T13:02:25Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 10,840 | ["frontend/src/lib/components/DateFilter/DateFilter.tsx", "frontend/src/scenes/insights/InsightDisplayConfig.tsx", "frontend/src/scenes/saved-insights/SavedInsights.tsx", "frontend/src/scenes/session-recordings/SessionRecordingsTable.tsx", "frontend/src/toolbar/styles.scss"] | PostHog Toolbar: Date dropdown rendering behind modal | ## Bug description
When trying to select the date range for Heatmap using the Toolbar, the data dropdown renders behind the modal. See video:
https://user-images.githubusercontent.com/92976667/179486686-e2379601-6d78-4a7e-b064-b79215f2568c.mov
## How to reproduce
1. Load heatmap
2. Click on number to load modal
3. Atempt to change the date
4. Make sad noises
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
Could be related to: #10829
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/10840 | https://github.com/PostHog/posthog/pull/10843 | 8ff436f6e13c07dc7782709edf0166b6d544ed3d | d5f1d864eb9bbf0618153c212d57ee35070d54d4 | "2022-07-18T09:50:17Z" | python | "2022-07-18T14:40:03Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 10,829 | ["frontend/src/lib/components/DateFilter/DateFilter.tsx", "frontend/src/scenes/insights/InsightDisplayConfig.tsx", "frontend/src/scenes/saved-insights/SavedInsights.tsx", "frontend/src/scenes/session-recordings/SessionRecordingsTable.tsx", "frontend/src/toolbar/styles.scss"] | Component regression for dashboard date controls | ## Bug description
The select component used to specify a time range for a dashboard has regressed such that it no longer has its border. The sizing also suggests that it might be a blend of ant and lemon components.
https://user-images.githubusercontent.com/254612/179269955-483f1d61-6779-4b65-bfca-fe11498a69fa.mov
## How to reproduce
1. Go to a dashboard
2. Observe the date control doesn't look like our other select components
## Environment
- [ ] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
- Likely related to https://github.com/PostHog/posthog/pull/10462
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/10829 | https://github.com/PostHog/posthog/pull/10843 | 8ff436f6e13c07dc7782709edf0166b6d544ed3d | d5f1d864eb9bbf0618153c212d57ee35070d54d4 | "2022-07-15T16:47:23Z" | python | "2022-07-18T14:40:03Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 10,767 | ["frontend/src/lib/utils.test.ts", "frontend/src/lib/utils.tsx", "frontend/src/scenes/toolbar-launch/authorizedUrlsLogic.test.ts", "frontend/src/scenes/toolbar-launch/authorizedUrlsLogic.ts"] | wildcard domain not working for my site (iFrame) | ## Bug description
I am trying to add a wildcard domain https://*.onbookee.com as an authorised URL but I am getting an error of 'invalid domain'.
How to reproduce
1.Add the above URL to authorised URL.
Environment
- PostHog Cloud
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/10767 | https://github.com/PostHog/posthog/pull/10777 | 01bfd4d7936d9eefbd7fd138f9cbb78e47fcaf1b | 2d7f929aa6cdd7fec1165fd6d0ab2202e33efe19 | "2022-07-13T13:21:09Z" | python | "2022-07-13T19:12:34Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 10,701 | ["frontend/src/lib/components/PropertyGroupFilters/PropertyGroupFilters.tsx"] | Filter button sizing seems wrong | Which button is not like the others?
<img width="663" alt="image" src="https://user-images.githubusercontent.com/154479/178038471-2a38454b-0959-46b5-9374-b24de4a23442.png">
| https://github.com/PostHog/posthog/issues/10701 | https://github.com/PostHog/posthog/pull/10973 | 74a383408941fdcf2728ebbd059c3488d03ab4b2 | ddd9fb4be8285ed62c9b7c0f9676bc1ff5640dc4 | "2022-07-08T17:08:23Z" | python | "2022-08-09T17:15:21Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 10,677 | ["frontend/src/scenes/actions/actionEditLogic.tsx", "frontend/src/scenes/insights/insightSceneLogic.tsx", "frontend/src/scenes/session-recordings/playlist/sessionRecordingsPlaylistLogic.ts"] | Add prompt about losing form changes when editing an action | I added a tag to this action:
<img width="1388" alt="image" src="https://user-images.githubusercontent.com/154479/177860361-969bf93d-09d0-4608-8831-259f10d2ec8d.png">
But it's unclear if I need to click the save button - especially since there's no save button visible in the viewport on my 13" MBP.
I decided to click back to Data Management, assuming I'd get a prompt about losing changes if the tag hadn't already been saved automatically. To my horror, no such prompt appeared and I lost my tag. RIP.
This is especially inconsistent since the title/subtitle are both saved _outside_ of the event definition form. I had expected the same behavior with tags.
### Suggestions
- An additional save button (up next to Delete) might be nice, at least appearing when there are changes made to the form
- Figure out a way to move the save button up the page a bit
- Definitely: a JS dialog when trying to leave a form while in a dirty state | https://github.com/PostHog/posthog/issues/10677 | https://github.com/PostHog/posthog/pull/16868 | 3e9d4da1cbb9b488ace44b6c70afa60cc4116a84 | 6c68ba9edd37d5f8ce2d1fb04890c14cbccada1d | "2022-07-07T19:58:31Z" | python | "2023-08-01T15:04:28Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 10,573 | ["frontend/src/scenes/funnels/FunnelCanvasLabel.tsx", "frontend/src/scenes/funnels/useFunnelTooltip.tsx", "frontend/src/scenes/insights/views/Funnels/FunnelStepsTable.tsx"] | Ability to show 2 decimals on percentages | ## Is your feature request related to a problem?
When we are looking at funnels that have a similar conversion rate, it's hard to differentiate between similar values because they are all displayed with 1 decimal.
For example, both 12.58% and 12.63% would be displayed as 12.6%.
Right now, the only way to see it is to divide the 2 numbers (e.g. in a calculator app) to see what the 2-decimal value is.
Thanks for considering this enhancement!
## Describe the solution you'd like
Having the ability to see percentages with 2 decimals of precision. Some possible solutions:
- Show 2 decimals places on hover.
- Have a setting somewhere that allows showing all percentages to either 1 decimal or 2 decimals.
Would be great to see this added precision on both the dashboard view and the detail view.
## Describe alternatives you've considered
- Manually dividing the numbers to see the values to 2 decimals. This is slower and doesn't allow seeing the values at a glance of the dashboard. This is what we currently do.
- CSV export and building an external dashboard. Haven't tried this as we want to keep it simple and have it all in Posthog.
## Additional context
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/10573 | https://github.com/PostHog/posthog/pull/11052 | 29204df7775f38470e2f667ec7d74921832d8328 | bb5e9bf7416db52506c8407274055f01f95fc50a | "2022-06-29T19:22:28Z" | python | "2022-08-01T12:43:11Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 10,384 | ["frontend/src/lib/components/PersonalAPIKeys/PersonalAPIKeys.tsx", "frontend/src/lib/components/TimezoneAware/index.tsx", "frontend/src/lib/utils.tsx", "frontend/src/scenes/session-recordings/SessionRecordingsTable.tsx", "posthog/auth.py"] | personal_api_key.last_updated_at is updated every request | ## Bug description
personal_api_key.last_updated_at is updated every request with API keys.
This is one of the most time-consuming queries we do against postgres: https://metabase.posthog.net/question/344-most-time-consuming-postgres-queries
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
There's a half-hearted attempt at fixing this over at https://github.com/PostHog/posthog/pull/10383, but this was shot down due to UX concerns.
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/10384 | https://github.com/PostHog/posthog/pull/10383 | 14b8309c55e5fe018e0b7180bbe3971016626659 | 226084a18b8c40fc219f5cc91316fcb6a07fddbb | "2022-06-21T11:57:06Z" | python | "2022-06-21T16:51:25Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 10,323 | ["frontend/src/scenes/plugins/plugin/PluginCard.tsx"] | Feature Request: Remove/Change 'Managed by PostHog' tag on apps | ## Is your feature request related to a problem?
I've been at PostHog for over a year now and only last week [learned](https://github.com/PostHog/posthog/issues/10167) that the `🌐 Managed by PostHog` tag we use on apps doesn't mean what I thought it meant.
I _thought_ it meant that these apps were managed by PostHog; that we maintained them, made sure they worked, provided support, etc. What it _actually_ means is 'Available on PostHog Cloud'.
I find this super unclear and also not very valuable. Users on Cloud will _only_ see these apps and users not on Cloud don't need this information.
@tiina303 [raises the point](https://github.com/PostHog/posthog/issues/10167#issuecomment-1148693003) that the tag can help SH users understand which apps they can trust, but I don't think it achieves that. Partly because plenty of these apps have issues, partly because that should be achieved by the `Official` tag, and partly because we should ultimately want users to either trust all apps or to be alerted to the risk that they can't.
## Describe the solution you'd like
I think it's worth removing the tag entirely.
## Describe alternatives you've considered
We could, as @tiina303 suggested, merge `Official` and `🌐 Managed by PostHog` into a new `Verified` tag. However, I think the `Official` tag is worth keeping as-is. I also worry that a `Verified` would imply that apps get continuing support and are verified to work well, [which isn't true](https://github.com/PostHog/posthog/issues/10322).
Alternatively, we could change the wording of this tag to make it's actual meaning clearer: `Available on Cloud`.
## Additional context
This is mostly a labelling and UI issue, so tagging @clarkus and @lottiecoxon
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/10323 | https://github.com/PostHog/posthog/pull/10946 | 6c521a26f08033f828b0faa94899a6b1a70d7d97 | 43c4787cb74f0e83bc449c2e27c0c7460bba671d | "2022-06-16T10:02:09Z" | python | "2022-07-25T12:07:06Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 10,263 | ["frontend/src/mocks/utils.ts", "frontend/src/models/dashboardsModel.tsx", "frontend/src/models/insightsModel.tsx", "frontend/src/scenes/dashboard/dashboardLogic.test.ts", "frontend/src/scenes/dashboard/dashboardLogic.ts", "frontend/src/scenes/insights/insightLogic.test.ts", "frontend/src/scenes/insights/insightLogic.ts", "frontend/src/scenes/insights/utils/dashboardTiles.ts", "frontend/src/scenes/saved-insights/savedInsightsLogic.ts"] | Dashboard insights don't update after changing insight definition | I defined a funnel with the wrong event, so I clicked edit and updated the funnel step. Then I returned to the dashboard where I was viewing it, but it had the old funnel steps. Refreshing the page fixed it, but it should ideally update without me having to refresh.
Repro:
1. View a dashboard
2. Click Edit from the insight on the dashboard
3. Change a funnel step
4. Return to view dashboard and see how the updated insight doesn't update in the dashboard until a browser refresh
| https://github.com/PostHog/posthog/issues/10263 | https://github.com/PostHog/posthog/pull/11690 | 7960ac368bd64a8ffd36356a2497d27685702d65 | f9544426bc24ff58d00616527191570a71daf0b1 | "2022-06-11T16:42:20Z" | python | "2022-09-08T08:39:33Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 10,261 | ["frontend/src/scenes/saved-insights/savedInsightsLogic.ts"] | After duplicating an insight, take me to the edit view | It's super handy to have the option to duplicate an insight!
<img width="623" alt="image" src="https://user-images.githubusercontent.com/154479/173196288-de101910-ee42-49df-ba3b-981bf6ad9404.png">
But currently, you're taken to the saved view of the new insight.
I believe the use case is, _"I want to create a new insight that is a slight variation from the currently-saved insight."_ In this case, it would make more sense to take the user to the edit screen so the user can modify the newly-duplicated insight.
As a user, I'm also not completely sure if I'm now viewing the _duplicated_ insight or the _original_ insight. Changing the name of the newly-duplicated insight would be useful, as well. (Eg: "Copy of _Insight name_" or "_Insight Name_ (2)") | https://github.com/PostHog/posthog/issues/10261 | https://github.com/PostHog/posthog/pull/10975 | 7bd3cac2f56b93ea1b0fa4dc5243a81c2cd33a28 | fb640dae117b5f47a5cc9ce799696b69c2d2c923 | "2022-06-11T16:25:55Z" | python | "2022-08-15T08:26:34Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 10,256 | ["ee/clickhouse/views/test/test_clickhouse_trends.py", "posthog/api/utils.py", "posthog/models/filters/filter.py", "posthog/models/filters/mixins/common.py", "posthog/models/filters/stickiness_filter.py", "posthog/queries/stickiness/stickiness.py", "posthog/queries/trends/total_volume.py"] | Person Modal shows incorrect data when two filters on the same event is used | ## Bug description
When you create a trend with two lines, one of which is say $pageview with a filter of browser = chrome and the other is ALSO $pageview but a different filter.
If you click on any the line you get the same users in the persons modal, even if you switch the trend line toggle in the modal.
## How to reproduce
1. Create a new trend
2. Add a $pageview trendline, and another $pageview trendline with a subfilter
3. Click on any of the lines
4. Open the persons modal and switch between the trend lines in the persons modal
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/10256 | https://github.com/PostHog/posthog/pull/10289 | 8063b69bbd87403e0bdd4b3c91916a145b2a8858 | 2367289918032fd5b3dc452bf1ac230118b150d2 | "2022-06-10T17:40:30Z" | python | "2022-06-23T14:41:23Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 10,228 | ["frontend/src/scenes/cohorts/Cohorts.tsx"] | Incorrect column alignment on cohorts table | ## Bug description
The cohorts table contains a "users in cohort" column that contains numeric values. The column is left-aligned which makes comparing values very difficult.
The column should be right aligned to make it easier to compare numeric values.
## How to reproduce
1. Go to cohorts
2. Note the table column "users in cohort" is left aligned
| https://github.com/PostHog/posthog/issues/10228 | https://github.com/PostHog/posthog/pull/11866 | 1f3fdd90959d97c487b5a5116f71b9c9b958cdd9 | c3969f4f01fd492aececf8e965180aa738a37133 | "2022-06-09T22:30:32Z" | python | "2022-09-19T11:39:35Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 10,226 | ["frontend/src/scenes/funnels/FunnelBarChart.scss", "frontend/src/scenes/funnels/FunnelBarChart.tsx"] | Relative values missing from left-to-right funnel layout | ## Bug description
We're only showing absolute conversion values in the left-to-right funnel layout. These values should align with the top-to-bottom layout where we show absolutes with relative values in secondary positions.
## How to reproduce
1. Create a funnel
2. View it in left-to-right layout
3. Note the relative values are missing.
## Additional context
- [Figma](https://www.figma.com/file/gQBj9YnNgD8YW4nBwCVLZf/PostHog-App?node-id=8161%3A46841)
- [Slack thread](https://posthogusers.slack.com/archives/C01GLBKHKQT/p1654073856765669)
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/10226 | https://github.com/PostHog/posthog/pull/11933 | c629bc9b161421f03e222a6c9c2dab13f6c98a3d | efe92f7dd31a52ad3df4b862fee326d694213023 | "2022-06-09T22:09:23Z" | python | "2022-09-23T10:36:40Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 10,048 | ["frontend/src/lib/components/Cards/InsightCard/InsightCard.scss", "frontend/src/lib/components/Cards/InsightCard/InsightDetails.tsx", "frontend/src/lib/utils.tsx"] | AND/OR property filter groups are shown incorrectly in insight details | ## Bug description
We've added AND/OR filtering recently, which looks like this in the query editor:
<img width="720" alt="insights" src="https://user-images.githubusercontent.com/4550621/170721548-c9c3cc8b-2c8d-4a52-8f60-2d103b08925f.png">
But support for this has not been added to the `QuerySummary` component, which is used in `InsightCard`'s `InsightDetails`. There, the above filters show up like this:
<img width="329" alt="querysum" src="https://user-images.githubusercontent.com/4550621/170721602-13cd4f96-6b1e-48dd-b6f7-942f8fc724db.png">
That gives a wrong image of the query.
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/10048 | https://github.com/PostHog/posthog/pull/12382 | 0a0d3aed171f47d3e8e7dfdbba01c2a16e0c1303 | c79d826033c776c8688c9be76175343c4cf5239b | "2022-05-27T14:40:58Z" | python | "2022-10-21T13:58:19Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 10,023 | ["frontend/src/lib/components/LemonTable/LemonTable.tsx", "frontend/src/scenes/insights/InsightContainer.tsx", "frontend/src/scenes/insights/views/InsightsTable/InsightsTable.tsx"] | Clicking a column header asks me if I want to leave the page | In an unsaved insight, clicking a column header (to sort by that column) asks me if I want to leave the page.
As a user, I want to be able to run a query and manipulate the presentation of the results without having to first save the insight.
| https://github.com/PostHog/posthog/issues/10023 | https://github.com/PostHog/posthog/pull/11456 | aee2aa757268d4dad036165acb1abd372279e4cf | aee716a166bead3f1fc67728b18678b3859a3b6d | "2022-05-26T19:38:20Z" | python | "2022-08-24T10:01:49Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 9,992 | ["frontend/src/scenes/project/Settings/index.tsx"] | Somewhere in the App show the ProjectID for API usage | ## Is your feature request related to a problem?
In the API Docs we refer to `:project_id` for most endpoints but we don't really give people an easy way to know what their project ID is. We mention that you can use the [project api key ](https://posthog.com/docs/api#specifying-a-project-when-using-the-api) and I think falsely state that if omitted we will use the last selected project.
The only ways currently to know are to inspect your network traffic in Posthog or to call the `/projects` endpoint (which is overkill for most teams with one project)
## Describe the solution you'd like
I would propose we add a section to the Project Settings detailing the current Project ID with a link to the API docs about it and then vice versa update the Docs to link to where the person can find their project ID.
## Additional context
Particularly interested if @Twixes or anyone knows of something I am missing which might already exist documentation-wise
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/9992 | https://github.com/PostHog/posthog/pull/10145 | e69a3e4b95a46268a487ea1f671574e295887fec | 0dfb44ebbc466a4f399741e0d7ecef007af70c0d | "2022-05-25T14:56:12Z" | python | "2022-06-06T14:15:03Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 9,906 | ["frontend/src/models/dashboardsModel.tsx", "frontend/src/scenes/dashboard/Dashboards.tsx"] | Bug: My dashboard has gone missing and I didn't delete it | ## Bug description
A dashboard called "Website & SEO" has gone missing. It's not visible in any searches, but I know it's there somewhere...
When I view insights I know are on the dashboard, I get this message but the dashboard isn't visible to select.
## How to reproduce
Honestly not 100% sure, but this happened when I clicked on an insight on the dashboard, edited the insight and saved it. After that, the dashboard has been inaccesible to me.
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
n/a
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/9906 | https://github.com/PostHog/posthog/pull/9910 | 5eaa3c6ca58bf3ba929ec283b075d96be6324589 | a2f44183bf6efdb8897e61a46874aee1a2d2b8cb | "2022-05-23T13:04:45Z" | python | "2022-05-24T09:53:40Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 9,768 | ["frontend/src/lib/components/PropertyFilters/components/PropertyValue.tsx"] | Filtering for some properties results in weirdness | ## Bug description
Discovered in cohort creation, but also reproducible when filtering insights: when filtering using an `equals` operator, it's possible to select multiple values and then to specify the whole selected set as an appended group... this is really hard to describe so I made a video.
## How to reproduce
https://user-images.githubusercontent.com/254612/168126487-9af2008f-1b27-41b6-ac87-b120b1e3dc68.mov
## Environment
- [x] PostHog Cloud
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/9768 | https://github.com/PostHog/posthog/pull/9769 | 3a644acf2bec2ac158bba16d65d92925c4af456e | 8a05b79efb80f1638dfb404bb81f4200aae7d430 | "2022-05-12T16:45:01Z" | python | "2022-05-12T21:40:31Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 9,727 | ["cypress/support/e2e.js", "frontend/src/lib/components/DateFilter/DateFilter.tsx", "frontend/src/lib/components/DateFilter/DateFilterRange.scss", "frontend/src/lib/components/DateFilter/DateFilterRange.tsx", "frontend/src/lib/components/DateFilter/DateFilterRangeExperiment.tsx", "frontend/src/lib/components/DateFilter/dateFilterLogic.test.ts", "frontend/src/lib/components/IntervalFilter/intervalFilterLogic.ts", "frontend/src/lib/constants.tsx", "frontend/src/lib/utils.test.ts", "frontend/src/lib/utils.tsx"] | Updated date range selection workflow | ## Is your feature request related to a problem?
Selecting a date range in PostHog can be pretty tedious depending on what you're trying to accomplish. Select a starting date for a fixed time range requires three clicks / actions just to pick the first range parameter. Our list of preset rolling time ranges use days as the most common time unit, but research shows that users use a broader range of units.
## Describe the solution you'd like
**Prioritize selecting rolling / relative date ranges using a list of preset values.** Reduce the number of options and provide a semi-custom rolling range via a numeric input and a time units. The core change here is to provide a semi-custom rolling time range option. These are always relative to the current date and are formatted as a numeric value and a time unit option. For example, the last [3] [days], the last [1] [quarter], the last [18] [weeks]. A custom option would reduce the need for specific presets. We could also increase user confidence if we translated relative ranges to actual time frames using tooltips.
**Relative dates are represented as relative ranges in the summary state for the picker.** Likewise, fixed / absolute range are more specific and show the actual range selected.
**Separate selecting a fixed / absolute range and provide reasonable defaults to reduce the number of actions it takes to submit a value.** When selecting a custom fixed range, ditch the start and end date inputs and instead directly show the calendar immediately. A user would just need to select a start date to have a valid time range if the end date defaults to the current date.
**Changes to consider based on the research @marcushyett-ph did for https://github.com/PostHog/product-internal/pull/305**
1. Change the default rolling time range to 30 days for insights
2. Automatically adjust time grouping units to the range selected. For example if you select the last 24 hours, today, yesterday, it doesn't make sense to group by any unit larger than a day. Hours would be the most approachable unit for this scenario.
3. When selecting a fixed time range, disallow selection beyond the current date. It doesn't make sense to look at future dates in this scenario. We don't have data for the future as we don't do predictions. Our default end date for a custom time range should be the current date.
4. When selecting fixed ranges, reduce the number of clicks / actions it takes to get to the calendar interface. Right now this takes three clicks just to pick a starting date. We also make users select an end date when we could have a reasonable default of the current date here.
5. Add a quarterly option to the relative range picker
6. Make it more obvious when a fixed range is applied to an insight.
7. Consider expanding our preferences / project settings for time. For example, starting the week on Monday instead of Sunday, time value formatting (12 versus 24 hour clocks), timezones, etc.
## Additional context
- https://github.com/PostHog/product-internal/pull/305
- https://github.com/PostHog/posthog/issues/9664
- https://github.com/PostHog/posthog/issues/9453
- https://github.com/PostHog/posthog/issues/9027
- https://github.com/PostHog/posthog/issues/6619
- https://github.com/PostHog/posthog/issues/8640
- https://github.com/PostHog/posthog/issues/8460
- https://github.com/PostHog/posthog/issues/8059
- https://github.com/PostHog/posthog/issues/7625
- Figma - https://www.figma.com/file/NHPA2hVWwaKp4eTGWdigs9/?node-id=1768%3A6935
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/9727 | https://github.com/PostHog/posthog/pull/10688 | a1c0aafa2961fa6966c3cfdaf4d265184e876c8a | 1dfaf539e583b973480110d8f4ae52850f8c2eec | "2022-05-10T20:58:53Z" | python | "2022-07-08T10:26:02Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 9,665 | ["posthog/api/insight.py", "posthog/api/test/test_insight.py"] | CSV export doesn't include event/action names | When exporting data from [an insight](https://app.posthog.com/insights/oVHjTLUD), the action names weren't exported, making the CSV a little hard to follow.
As a user, I'd expect to see the same data in the export as I see in the table in-app.
<img width="1012" alt="image" src="https://user-images.githubusercontent.com/154479/166958828-9b3add76-633b-4f1d-ad2b-cf1ea2888b95.png">
| https://github.com/PostHog/posthog/issues/9665 | https://github.com/PostHog/posthog/pull/9677 | 392c1e19cee3a64981669166840566038e5d4fbf | 4a1a88b76cd4d2ec5db1655ec3c01d7be2e4af07 | "2022-05-05T15:32:42Z" | python | "2022-05-06T14:37:23Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 9,596 | ["frontend/src/scenes/insights/InsightsTable/InsightsTable.tsx"] | Event propagation for sort actions on dashboard tables is kind of broken | ## Bug description
When multiple tables are included on a dashboard, sorting by one column triggers a sort for all tables on the dashboard. Instead the sort action should only sort the table in which the column exists.
## How to reproduce
1. Create a dashboard with multiple table insights
2. View the dashboard
3. Sort a table and note that all tables are affected
## Environment
- [x] PostHog Cloud
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/9596 | https://github.com/PostHog/posthog/pull/9625 | 272ac3c131a8f51de494a72562aedd41cfdd50cb | 8fe02102777d649474023af73c7e47b08617ba28 | "2022-04-29T20:27:57Z" | python | "2022-05-03T19:22:26Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 9,570 | ["frontend/src/lib/components/LemonTable/LemonTable.tsx", "frontend/src/scenes/insights/InsightContainer.tsx", "frontend/src/scenes/insights/views/InsightsTable/InsightsTable.tsx"] | Bug: Refusing to apply a sort filter on a breakdown table, applies the sort filter anyway | ## Bug description
[So, as I was saying... I was doing this](https://github.com/PostHog/posthog/issues/9568) and I decided to see what would happen if I sort a breakdown table and press _cancel_ when this error shows up...
<img width="1055" alt="Screenshot 2022-04-28 at 11 21 32" src="https://user-images.githubusercontent.com/84011561/165732065-c344f356-015e-486b-b9c7-390712a91e71.png">
And what happens is that...it works! It applies the sort filter in exactly the way I wanted.
<img width="1279" alt="Screenshot 2022-04-28 at 11 09 35" src="https://user-images.githubusercontent.com/84011561/165732088-7f2a59f6-ab5b-45dd-9750-d78e788aa478.png">
So, why is this a bug? Because the error was unclear, potentially not needed and because I was only able to get the result I wanted by _cancelling_ the action I wanted to take.
## How to reproduce
1. Insight, unsaved, with breakdown table
2. Sort a column, press cancel
3. Get what you wanted (but not, as the Stones say, what you need)
## Environment
- [ ] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
Tagging @lottiecoxon and @clarkus because, again, there's a UI issue around error text and, frankly, I've tagged them in so many issues this morning that it's become a habit. Sorry, both!
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/9570 | https://github.com/PostHog/posthog/pull/11456 | aee2aa757268d4dad036165acb1abd372279e4cf | aee716a166bead3f1fc67728b18678b3859a3b6d | "2022-04-28T10:23:31Z" | python | "2022-08-24T10:01:49Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 9,568 | ["frontend/src/lib/components/LemonTable/LemonTable.tsx", "frontend/src/scenes/insights/InsightContainer.tsx", "frontend/src/scenes/insights/views/InsightsTable/InsightsTable.tsx"] | Bug: Sorting a breakdown on an unsaved insight deletes the insight | ## Bug description
I was making an insight to look into the locations of users by timezone (though I've repeated this bug with other insights and it happens there too).
Important to clarify that this was on an unsaved insight because I didn't need to save it (and this bug doesn't effect saved insights). But I did want to sort the breakdown table into a different order. Trying to sort the table prompts this message:
<img width="1279" alt="Screenshot 2022-04-28 at 11 09 35" src="https://user-images.githubusercontent.com/84011561/165730119-1819592e-fb56-4348-8f18-4903972b0963.png">
Now, my _assumption_ was that this was because it needs to reload the insight. As in, I'll press OK and it will reload the insight with the table sorted the way I wanted. So, I press OK.
<img width="1010" alt="Screenshot 2022-04-28 at 11 06 36" src="https://user-images.githubusercontent.com/84011561/165729566-b3e5fcb4-f3a7-45fd-b5ee-4d4501c21a34.png">
Oh shit, that wasn't what I expected! It's not only removed the breakdown on the insight, it's _deleted the entire insight_.
Though, apparently the sort I applied on Apr 22 is still applied? Hmm.
So, I rebuild the insight, sort again, this time I press cancel. [But that gives a different bug!](https://github.com/PostHog/posthog/issues/9570)
## How to reproduce
1. Trends insight, unsaved
2. Add a breakdown
3. Sort the breakdown, press OK
## Environment
- [ ] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
Tagging @lottiecoxon and @clarkus as there's a UI element here possibly in terms of making the error text clearer?
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/9568 | https://github.com/PostHog/posthog/pull/11456 | aee2aa757268d4dad036165acb1abd372279e4cf | aee716a166bead3f1fc67728b18678b3859a3b6d | "2022-04-28T10:12:34Z" | python | "2022-08-24T10:01:49Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 9,505 | ["frontend/src/scenes/instance/SystemStatus/RenderMetricValue.tsx", "posthog/clickhouse/system_status.py"] | Last event ingested in /instance/status is UTC but looks like localtime | ## Bug description
Last event ingested in /instance/status in system overview tab is UTC but looks like local time
Could be confusing to user to see UTC time there with no indication it's UTC.
Would be great if it showed up similar to time in live events https://app.posthog.com/events
## How to reproduce
1. Go to https://app.posthog.com/instance/status system overview tab (being in non UTC timezone) & check the "Last event ingested"
## Environment
- [x] PostHog Cloud
- [x] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/9505 | https://github.com/PostHog/posthog/pull/14888 | cccefc889fbd0ea77c24145e096ac0e58d5d2ac1 | df30c4550c9f2d36f91a5f8678bc9b9214c24e9c | "2022-04-22T17:27:30Z" | python | "2023-03-24T11:02:05Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 9,478 | ["frontend/src/scenes/insights/InsightContainer.tsx"] | Renaming formula series doesn't work | ## Bug description
*Please describe.*
*If this affects the front-end, screenshots would be of great help.*
click, no response
## How to reproduce
1.create insights
2.trends, I have 2 series
3. formula = A+B
4. edit series name
## Environment
- [ ] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/9478 | https://github.com/PostHog/posthog/pull/12987 | e0c887d3d7cfb585bb7eee05f4ec78bd246591e1 | 48bc8ebf9107cb470f3a967a86bb333c7f478658 | "2022-04-21T05:50:13Z" | python | "2022-11-29T09:05:28Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 9,453 | ["cypress/support/e2e.js", "frontend/src/lib/components/DateFilter/DateFilter.tsx", "frontend/src/lib/components/DateFilter/DateFilterRange.scss", "frontend/src/lib/components/DateFilter/DateFilterRange.tsx", "frontend/src/lib/components/DateFilter/DateFilterRangeExperiment.tsx", "frontend/src/lib/components/DateFilter/dateFilterLogic.test.ts", "frontend/src/lib/components/IntervalFilter/intervalFilterLogic.ts", "frontend/src/lib/constants.tsx", "frontend/src/lib/utils.test.ts", "frontend/src/lib/utils.tsx"] | Design: Changes to the date selector for queries, for ease of use and physics | ## Is your feature request related to a problem?
This is a design nit I noticed, so tagging @clarkus
Currently if you select a date range option on a query you're building you see this:
<img width="442" alt="Screenshot 2022-04-19 at 13 40 36" src="https://user-images.githubusercontent.com/84011561/164006191-721b1be4-ad83-4d4a-bab6-95c82ac1c048.png">
And then you have to select 'Start Date' or 'End date' and then it expands to this:
<img width="715" alt="Screenshot 2022-04-19 at 13 38 03" src="https://user-images.githubusercontent.com/84011561/164006285-90199a0e-199c-42d3-a77e-366e4fab90fc.png">
The problems I see are:
1. This adds an extra click to the flow, because you have to select 'Start date' only to probably then click off of it and choose a date from the calendar view.
2. May hasn't happened yet. It's non-sensical to let me choose a date which hasn't happened yet, either as a start date or an end date. We seem to currently default to showing this month and next month.
## Describe the solution you'd like
1. Would seem easier if the calendar view appeared by default and the first click there defaulted to the start date.
2. Don't default to showing dates in future months on the calendar view.
This will mean less clicks and better inputs. Faster, better insights! Woo!
## Describe alternatives you've considered
None because my first ideas are always my best ideas.
## Additional context
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/9453 | https://github.com/PostHog/posthog/pull/10688 | a1c0aafa2961fa6966c3cfdaf4d265184e876c8a | 1dfaf539e583b973480110d8f4ae52850f8c2eec | "2022-04-19T13:00:19Z" | python | "2022-07-08T10:26:02Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 9,438 | ["latest_migrations.manifest", "posthog/migrations/0226_longer_action_slack_message_format.py", "posthog/models/action/__init__.py", "posthog/models/action/action.py"] | Increase character limit of Action message format | ## Is your feature request related to a problem?
Can't define desired message format in an Action.
## Describe the solution you'd like
Increase character limit significantly.
## Describe alternatives you've considered
none
## Additional context
200 characters are way too little, especially if you have lots of variables with long names.
A single placeholder can easily take 50 characters, esp. with the overly long `[event.properties.…]` syntax.
<img width="427" alt="image" src="https://user-images.githubusercontent.com/85242/163712432-7e153e72-4385-453d-9184-287238862a8b.png">
| https://github.com/PostHog/posthog/issues/9438 | https://github.com/PostHog/posthog/pull/9464 | 57ccb0dc66edfe8cdc5186cce60f68ca6b0b554d | 56da1759ffbb49bf47657b902fea855dbedb63b0 | "2022-04-17T11:30:43Z" | python | "2022-04-20T12:46:29Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 9,392 | ["frontend/src/scenes/insights/Insight.tsx", "frontend/src/scenes/insights/insightLogic.ts"] | When saving an insight I get a warning asking if I should discard it | ## Bug description
<img width="1183" alt="image" src="https://user-images.githubusercontent.com/85295485/162939840-8d48e786-85ad-41c1-bf71-a31b4123e9e7.png">
## How to reproduce
1. Create a new insight
2. Click Save
3. You see the warning above asking if you'd like to discard it
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/9392 | https://github.com/PostHog/posthog/pull/9397 | ccecef2344075769b8daa2c413aa7056a841b53b | d8adc89b7943b6cd0ad941e479f0e5c894153164 | "2022-04-12T10:26:54Z" | python | "2022-04-12T17:01:55Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 9,378 | ["frontend/src/lib/components/ActivityLog/activityLogLogic.person.test.tsx", "frontend/src/lib/constants.tsx", "frontend/src/lib/utils.test.ts", "frontend/src/lib/utils.tsx", "frontend/src/scenes/persons/PersonHeader.test.ts", "frontend/src/scenes/persons/PersonHeader.tsx", "frontend/src/scenes/session-recordings/player/metaLogic.ts", "frontend/src/types.ts"] | Person Name/Email are case sensitive | ## Bug description
When Identifying the `name` and `email` user attributes, I've used `Start Case` to make it easier for less technical users to read. eg `posthog.identify('id', { Name: 'Full Name', Email: '[email protected]' })`.
In the posthog UI this shows up as `User XY38` or similar rather than detecting the name/email.
Could this be changed so that `name` and `email` detection are
## How to reproduce
1. Send an identify command with capitalised name/email. `posthog.identify('id', { Name: 'Full Name', Email: '[email protected]' })`
2. In posthog UI find the person, note that the values are recorded but the name is still the auto-generated name and not the name or email fields.
## Environment
- PostHog Cloud | https://github.com/PostHog/posthog/issues/9378 | https://github.com/PostHog/posthog/pull/11112 | 18ec67072305d793d3e5bfcb374bf453e4cef961 | d0752b0155c2f4b2dc231c1d8b9a1780d974fb40 | "2022-04-11T02:15:48Z" | python | "2022-08-04T18:53:09Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 9,269 | ["frontend/src/lib/components/PropertiesTable.tsx", "frontend/src/scenes/events/EventDetails.tsx"] | $set field is detected as a boolean whereas it's sent as a string | ## Bug description
When we `identify` a user, we use `$set` to set a person email address. It lets us create cohorts based on email domains.
This `email` field is detected as a boolean, whereas we send a string. This means that we cannot use "includes" when creating a cohort
Example of identify event from Live Events view:
## Expected behavior
The field should be detected as a `string` type
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
| https://github.com/PostHog/posthog/issues/9269 | https://github.com/PostHog/posthog/pull/9278 | a85cbcb747de1f9e1c1379454afe21abc528e083 | b88c4d1e3739efe350e74059ad9a7d0d9a49d10f | "2022-03-28T16:36:59Z" | python | "2022-03-29T09:28:43Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 9,239 | ["frontend/src/scenes/dashboard/Dashboard.scss", "frontend/src/scenes/dashboard/DashboardCollaborators.tsx"] | Incorrect icon used to remove collaborators from a dashboard | ## Bug description
To remove a user from a shared dashboard, you click on a red x icon. This doesn't really align with any other interface in the product. The action is non-destructive as we're just removing a reference, not destroying data.
Secondarily, these actions are shown to all users. We shouldn't expose remove actions to users who don't have permission to use those actions.
The [original concept](https://www.figma.com/file/gQBj9YnNgD8YW4nBwCVLZf/PostHog-App?node-id=8573%3A53107) allowed for changing permission types along with removing the user via the same component.
<img width="478" alt="Screen Shot 2022-03-24 at 9 05 33 AM" src="https://user-images.githubusercontent.com/254612/159959870-705bc698-605e-4278-b971-c911afa872f6.png">
## Expected behavior
Use the icon we use in other similar scenarios and use a non-destructive palette option. Only show removal actions to the users who have permission to manage sharing for the dashboard. Until we allow for more granular control of collaborators, let's revisit this to use the same remove icons we use in other list views. We can also describe the icon with a tooltip to make it clear what the action does.
<img width="403" alt="Screen Shot 2022-03-24 at 9 13 55 AM" src="https://user-images.githubusercontent.com/254612/159961415-e37a7d0d-9363-478c-a370-8144bbe3d3be.png">
## How to reproduce
1. Go to a dashboard with multiple collaborators
2. Click share
3. View the list of users
| https://github.com/PostHog/posthog/issues/9239 | https://github.com/PostHog/posthog/pull/11457 | 49cb9a9c0bb0a951c467d1881246b6a93fec147a | 6ea255a5c0e4893541fe9cd62475ebdf8023e15c | "2022-03-24T16:14:45Z" | python | "2022-08-24T17:03:22Z" |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.