acoustic-actor-75733
04/11/2025, 5:20 PMquick-greece-27695
04/19/2025, 2:20 AMlate-ambulance-66508
04/24/2025, 1:43 PMlate-ambulance-66508
04/25/2025, 9:41 AMfaint-cat-56200
05/07/2025, 6:08 PMhelpful-glass-76730
05/12/2025, 8:11 AMambitious-apartment-58735
05/16/2025, 6:05 PMWe can write both as follows, where V is the number of tests that are statistically significant but are false positives and R are the number of tests that are statistically significant.
False Discovery Rate=FDR=E[V/(V+R)]
Should be V/R?creamy-magazine-78898
05/26/2025, 7:36 AMlate-ambulance-66508
05/27/2025, 8:31 AMincalculable-ram-43980
06/10/2025, 9:12 PMsalmon-fall-61851
06/11/2025, 8:34 AMm.timestamp >= d.timestamp + INTERVAL '1 hour'
), the conversion_window (e.g. + AND m.timestamp <= d.timestamp + INTERVAL '24 hours'
) is consistently missing, even when clearly configured in the UI and stored in the metric’s JSON (inspected via Web UI).
I’ve tested:
• Updating existing metrics → conversion_window is ignored.
• Creating new metrics via the UI → still ignored.
• Metrics (self-labeled) “in 90d”, “in 48h”, etc. → do not apply a user-relative time cap in the SQL, and we’ve therefore been consistently misreporting these numbers under the assumption that the window was respected.
• Burn-in does work reliably, so this appears to be a partial implementation.
Interestingly, I found one older metric that does apply the conversion window correctly, so it might be related to how/when the metric was created.
Let me know if you’d like reproduction steps or example SQL — happy to share more.
We're using GrowthBook Cloud w/ Build: 3.6.0+2d22835 (2025-06-10)
Thanks in advance!blue-dinner-94596
06/27/2025, 4:54 PMwide-beard-81045
07/07/2025, 11:44 PMglamorous-insurance-64799
07/14/2025, 2:26 AMPORT
environment variable, causing a conflict if it is set
The platform I'm trying to deploy GrowthBook on, Railway, always sets this variable
// packages/back-end/src/app.ts
app.set("port", process.env.PORT || 3100);
to something like
app.set("port", process.env.BACKEND_PORT || process.env.PORT || 3100);
Made a pull request: https://github.com/growthbook/growthbook/pull/4284bland-gigabyte-13713
07/25/2025, 10:28 AMbreezy-raincoat-53118
07/27/2025, 3:09 AMmicroscopic-honey-15884
08/15/2025, 11:17 AMpolite-summer-30867
08/19/2025, 6:37 AMnice-animal-35979
08/19/2025, 8:34 AMuser.targetingKey
, user.email
, etc. Using dev tools we figured out that if we pass an object like { user: { targetingKey: "1234", email: "<mailto:joe@example.com|joe@example.com>" } }
, our experiments are always skipped for all users with message "Skip because missing hashAttribute" (hashAttribute being set as user.targetingKey
) even though user.targetingKey
is (sort of?) specified.
Problem
In order to fix this, we tried to pass literal keys with dots e.g. { "user.targetingKey": "1234", "user.email": "<mailto:joe@example.com|joe@example.com>" }
& it fixed experimentation but broke feature flag conditions (e.g. IF user.targetingKey = "3456"
lines in GB settings) which worked correctly with nested objects.
This seem to work as described in any SDK, but, as a matter of fact, we use SDKs for React & .NET.
Extra
Additionally to the bug itself, dev tools make it feel like nested objects aren't supported at all which doesn't quite correlate with SDK setup instructions shown in GB itself (see screenshots attached)wide-cartoon-5349
08/27/2025, 7:40 PMnice-petabyte-75753
08/28/2025, 6:50 PMnice-petabyte-75753
08/28/2025, 6:51 PMnice-petabyte-75753
08/28/2025, 6:55 PM"growthbook": {
"command": "cmd",
"args": [
"/c",
"npx",
"-y",
"@growthbook/mcp@latest"
],
"env": {
"GB_API_KEY": "secret_MI_SECRET_KEY",
"GB_API_URL": "DDD",
"GB_APP_ORIGIN": "CCC",
"GB_EMAIL": "BBB",
"GB_USER": "AAA"
}
},
wide-cartoon-5349
09/03/2025, 5:05 PMbillowy-pizza-30300
09/04/2025, 4:25 AMstocky-zoo-87795
09/04/2025, 12:44 PMdisplayAsPercentage: true
.
On the Display Thresholds section, the numerator thresholds are also being shown as percentage, when it should be considered as an integer.fresh-stone-24633
09/09/2025, 6:02 AMdamp-knife-97320
09/15/2025, 11:57 PMLicense server errored with: Unable to create new subscription. Existing active subscription:
we were on enterprise trial, support downgraded us so we could upgrade to pro, but we are still unable to upgrade.lively-electrician-90916
09/18/2025, 12:29 PMfresh-stone-24633
09/21/2025, 7:37 PM