Avatar by Buch.
User Details
- User Since
- Nov 14 2014, 10:42 AM (511 w, 3 h)
- Availability
- Available
- IRC Nick
- phuedx
- LDAP User
- Unknown
- MediaWiki User
- Phuedx (WMF) [ Global Accounts ]
Wed, Aug 28
Tue, Aug 27
Fri, Aug 23
Thu, Aug 22
Moving to Code Review / Tech Input for code review of MR 42.
While I originally settled on contextual attributes, my preferences are: 1) context fields; and 2) context values. I have a slight preference for 1 because it matches the verbiage when talking about events and event schemas (events have fields, event schemas have fields).
Are they still called contextual attributes in the current version of Metrics Platform?
Wed, Aug 21
- plus performance, and scalability evaluation to the best of our ability.
MR 39 is blocked on MR 42, which is now ready for review (thanks for the ping @Sfaci!). I'll update the task description…
Mon, Aug 19
So the only way that we ensure consistency of assignment output sans backend store is by locking all the inputs.
Fri, Aug 16
- Can we successfully bucket users based on traffic?
Thu, Aug 15
Usecases examined
After a little more thought, we can combine the initial approach (fetching and caching the config in a per-DC cache on a loop) with the above approach to ensure that we don't contact Statsig whilst serving the page.
Wed, Aug 14
@cjming: I've added a bunch of comments and taken the liberty of updating the example CTR instrument. Would it be helpful to pull out all of the open questions into a separate section so that they can be addressed (or converted into Phab tasks, emails, etc)?
I think that this could be moved to done and any further deployment/responding to points in the Application Security Review can be done in other tasks /cc @VirginiaPoundstone @WDoranWMF
Tue, Aug 13
Mon, Aug 12
Up until now, I've assumed that minimize requests to the server is paramount. If I relax that assumption a little, I can see an alternative that's more flexible (it uses the remote-evaluation SDK, which has fewer cons) with the same control over what gets sent where and the same separation from Statsig:
Wed, Aug 7
☝️ I've hit some snags (plural).
Tue, Aug 6
I've reviewed the doc 👍 The note about GrowthBook Proxy was great.
Jul 26 2024
Jul 25 2024
Jul 24 2024
Jul 23 2024
@mpopov: I'm currently thinking about how to wire up the Statsig SDK and a general mechanism for T368326: Update Metrics Platform Client Libraries to accept experiment membership and would appreciate your input.
- I've had to use the maintenance version of the JavaScript SDK because:
- It allows you to inject the Statsig config fetched by the PHP SDKs directly rather than fetching it itself. During testing I found that this wasn't the case for the newer SDK
- The new SDK requires that you use a specific build to do local on-device evaluation. Per https://docs.statsig.com/client/js-on-device-eval-client, you require a Enterprise or Pro license to do on-device evaluation with this SDK
- A RESTful API is up and running that receive events and proxies these to a Statsig instance
Jul 22 2024
Jul 19 2024
A search for Next.js download SWC (from download-swc.js in that stacktrace you provided yielded: https://nextjs.org/docs/messages/failed-loading-swc
Jul 18 2024
Jul 16 2024
functional tests
The problem appears to have been highlighted by this edit to the Schema schema.
Jul 15 2024
Jul 12 2024
Jul 11 2024
Jul 9 2024
No need for a RegEx. A little DOMDocument magic in BannerRenderer should do: