Once in place it would be great to have some dashboards to look at and an experience report with how useful it was. I think it is a case of lack of resources (human and hardware both) and no one is opposed to it in principle, so with time we should get there.

Another issue I've found with /page/summary: https://en.wikipedia.org/api/rest_v1/#!/Page_content/get_page_summary_title

Nice. I've been talking to Gergo and I've put the sentry topic and client side error logging into the platform evolution feedback we are giving, so hopefully we can raise global awareness and resourcing to finally get proper infrastructure for client side error monitoring in the future. It is still ways off, so I think this would be a great stopgap measure specially now that you are refactoring different pieces.

Should we connect the test servers to a dashboard like the production one where we could see stats for tile generation rates, etc? (excuse me if it is already somewhere, couldn't find it). Seems like it could be a good idea to check on the servers before rolling to production when we make changes.

Cool, thanks for checking!

Do the apps bundle that module @bearND?

FTR all the reading lists post parameters that have "in": "body" have a name, the only one that doesn't is the /transform/section-changes/to/wikitext/{title}/{revision} one.

I'll keep it as stalled while we discuss, declined may have been to strong.

Hi @Kelson, I'm using priorities as stated on mediawiki. Low is not a bad thing, it means:

Maybe it makes sense for this to be in pagelib CSS instead of the base endpoint.

Hi @Kaartic, thanks for the reports!

This may be the case of just adding the meta viewport tag on the header of popup.html

@Mholloway Could you look into reproducing please? If you get some steps please move this to the backlog.

Needs reproduction.

Will do at some point.

I've checked those urls and they seem to behave well now. 👍

Lowering to Normal, we can revisit this once we are further along the integration with apps.

@Mholloway let's keep it open until we're sure it is stable and not broken. Feel free to move it back to doing when you work on it.

FTR I've added this to the Apps PMs sync because this came out of the blue for RI, and it shouldn't have.

@RHo signoff and resolve please.

Some questions to understand better what is up:

Product requirements from Olga and Lydia have been posted into parent task T111231: Page previews for Wikidata in case you want to have a look.

We'll reopen if there is a need for this. We're not planning on working on it right now.

We need to find out how often this error is happening and if it has any serious impact to prioritize.

👍 We can also patch the JSON file with a name and see if we get anything else interesting out of it.

Moving to kartotherian, if it should be on tilerator or maps-style move it.

Can't seem to reproduce now.

We don't have the resources right now to work on this, and it is probably solved on the new maps styles.

We don't have the resources right now to work on this, and it is probably solved on the new maps styles.

This involves:

Merged into the other task that has some more information on the comments and description. Thanks for keeping track of this.

Update: Design is going to be looking into the reqs and discussing a bit more before going for implementation.

Thanks for the improvements @bearND.

Cool, good for now. We will revisit the collapse table transforms in the future.

Nice! Verified on https://en.wikipedia.org/api/rest_v1/page/mobile-html/Banana

So beta cluster is now using the labs instance? Or is there more to do.

There is information about the android format in the task that @Dbrant mentioned T152160: Add beta announcement capabilities to apps

Cool! Declining for now then 😄

@RHo If that is the case then the work can be done by the apps teams directly 😄, so that's great!

This is what I'm doing @bearND

Moved it back to backlog as we're not doing anything with this right now, but having a discussion