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

functional tests

In T368543#9926759, @Lucas_Werkmeister_WMDE wrote:

I’m not really sure how this code could ever have worked:

includes/JsonSchemaContent.php

	public function objectRow( $key, $val ) {
		if ( $key === '$ref' ) {
			$valParts = explode( '/', $val, 2 );
			if ( !isset( $valParts[1] ) ) {
				// Don't store or inject service objects in Content objects
				// as that breaks serialization (T286610).
				$services = MediaWikiServices::getInstance();
				$revId = (int)$valParts[1];
				$revRecord = $services->getRevisionLookup()->getRevisionById( $revId );
				$title = $revRecord->getPageAsLinkTarget();

We’ve already checked that $valParts[1] isn’t set, but then we still cast it to an int, and try to load a revision record from that ID? Is the if condition just flipped from what it should be?

I also don’t see any recent changes to the code, which is confusing.

The problem appears to have been highlighted by this edit to the Schema schema.

In T355055#9976963, @Agamyasamuel wrote:

@phuedx Could you please elaborate the issue little more. would love to work on it.
~ Thanks.

In T365839#9969612, @BTullis wrote:

I suggest that we evaluate FerretDB with a PostgreSQL backend for this project. We can create a PostgreSQL database on our existing bare-metal PostgreSQL servers (an-db100[1-2]) for now, although we could actually leverage our work on the cloudnativepg operator in the near future, if we wish. If there are any issues, we could even use SQLite within a persistent volume for this initial setup period, although I would prefer to use PostgreSQL if possible.

No need for a RegEx. A little DOMDocument magic in BannerRenderer should do:

In T353817#9961942, @Ottomata wrote:

@Joe, to not squat w/beacon.php, in case there are other usages of /beacon that we'd want to route, would this perhaps be better at w/beacon/event.php ?

In T363685#9956753, @ngkountas wrote:

I'm moving this task to "Waiting for deployment" column. @KCVelaga_WMF do you think you could QA this task once the PR is merged and deployed?

In T366627#9950681, @Ottomata wrote:

It would be nice to generate some fake data and run some test queries on it to get an idea for latency added on by filtering on discriminator. I have not had time to do this yet.

The Number of mediawiki_product_metrics_wikilambda_api Events Featuring the Loopback Address

To confirm:

Being bold and closing this as Invalid as we are deploying a functional system to the Beta Cluster/deployment-prep in T366234: Deploy the Metrics Platform extension.

In T369006#9943911, @KCVelaga_WMF wrote:

There are some other peculiarities, related to the Metrics Platform's attributes:

• 5 events have their dt recorded as before the stream configuration was deployed (i.e. before 27 June).

Yeah. This is unfortunate. The internet largely agrees with your results, @Jdlrobson.

The config patch looks fine.

In T368326#9930952, @phuedx wrote:

To your question to @MNeisler and @nettrom_WMF: Should we include both names here – the machine- and human-readable ones?

Being bold.

One thought I did have was that EventBus's way of determining the client IP is different from other codebases. EventBus fetches the value of the X-Client-IP header directly. This is the only instance of this in all codebases indexed by Codesearch.

Also from Slack:

In T368326#9924054, @mpopov wrote:

@phuedx: I see in the Figma designs that instruments/experiments will have user-provided unique names with machine-readable versions auto-generated. Will those instruments/experiments have numeric IDs in the database that also uniquely identify them?

Maybe:

• For MPIC-managed experiments we can record numeric ID and the unique name (to avoid joining against MPIC's table of experiments to get the name from ID)
• For non-MPIC-managed experiments (e.g. the A/B test that Android team is planning) we would omit the numeric ID (there is none) and have the client fill in the experiment name

In T366460#9927866, @Ottomata wrote:

We are going to host a MediaWiki instance, an EventGate instance, and an MPIC instance in Toolforge

Cool! Where will the EventGate instance produce to?

From Slack:

What if the user is enrolled in multiple, non-overlapping (hopefully) experiments that are running on the same page? Should we rather add an experiments property, which is an array of experiment objects? If so, how would that impact querying the data?

In T367860#9906404, @phuedx wrote:

This provided difficult to impossible. I discussed this briefly with @WDoranWMF and we decided to:

• Configure EventLogging to submit events to the event ingestion service running on the Beta Cluster; and

In T366949#9914737, @cjming wrote:

One dependency of this task is that the monotable + base stream configs need to be in prod before we can properly populate the stream name for app base and web base radio button options.

In T366807#9914244, @mpopov wrote:

Oh cool! Yeah I'd love to squeeze that into scope. Should I make a separate task?

In T366807#9914020, @VirginiaPoundstone wrote:

@phuedx are there additional tasks we can/should include as part of this work based on this slack conversation and this other thread with @mpopov?

• The MediaWiki instance submits events to an EventGate instance running in the same cluster
• The MediaWiki instance requests stream configs from an MPIC instance running in the same cluster

An important note:

The MediaWiki instance is up and running, pulling instrument configs from the staging MPIC instance running on dse-k8s and generating stream configs.

Alright. @WDoranWMF and @cjming have also being doing some work on this recently.

☝️ We moved this back to In Progress so that we could fold in detail from a discussion between Ben Tullis and Andrew Otto about what is possible with the Event Platform deployment on the Beta Cluster.