Hi @kevinbazira , would you be able to update rec-api in production to include the patch above? This is a bit time sensitive. Thanks!

Still seeing a lot of failures here where the rec-api fails quickly because it gets 503 from cx server. The client side app is set to retry several times so I see a lot of those failures quickly and then one calls takes some time and comes back successfully. Can it be that cx server doesn't have the capacity to serve the traffic from rec-api? How would we identify/troubleshoot that?

Not sure it accounts for all the errors we're seeing since some are intermittent but from the log above, it looks like some article title encoding is insufficient when it contains a forward slash (9/11 conspiracy theories). When the slash is intact, it results in a URL path that CX server doesn't recognize, hence the 404. I tested it locally successfully. Patch incoming.

This URL failed many many times for me just now before finally succeeding. Wondering if there's something that can be found in the log, or if there's a way I can look for it myself. Is it in logstash?

I set up a complete local stack with the app calling a local recommendation API, which is calling a local CX server. After many many tries I got it to fail twice. Both were only reported by python as "ConnectError" from the recommendation API to the MW search API.

In T374387#10141256, @klausman wrote:

What is the User Agent you use? Do you have exact timestamps when the errors occurred?

This will help us find the error in our own logs.

In T374387#10141237, @klausman wrote:

When you say failed, what is the exact error/code/message?

In T357252#10136367, @KCVelaga_WMF wrote:

[...] It will be triggered immediately after user clicks the button, followed by either success or failure event.

I'm a little unclear about the "publish_attempt" event. Do I understand correctly that it will be logged when the editor tries to publish their translation (when they click the publish button) and it will be immediately followed by a "publish_success" or "publish_failure" (when the publish API call returns)?

In T374387#10132682, @Aklapper wrote:

How is this ticket a LPL Hypothesis? Sounds like Recommendation-API or SectionTranslation instead?

In T368422#10102283, @Pginer-WMF wrote:

[...]
One of the aspects that I was curious about whether that has been included is the grouping. Looking at the current taxonomy Literature is shown under the "Culture" group. Are those groups encoded in the system in a way different tools can use them consistently?
[...]

@Isaac is the article country model a distinct model with it's own search index tag and query syntax (i.e. "articlecountry:Ghana") or is it a bunch of new values for the article topic tag (i.e. "articletopic:country-ghana")?

In T373481#10098593, @Krinkle wrote:

Pinging @hueitan and @eamedina for code review

One challenge of this feature is getting the ORES topics and their localized labels.

Not necessarily. We were looking for a coding style with many small components and a central store, similar to a typical vue app. We thought about writing our own store and virtual dom renderer but found exactly that in reefjs so we gave it a try. It staled because the library is the pet project of a single person and is is practice unmaintained so it doesn't make sense for us to depend on it. I would say with the new team structure this work is still relevant but all options are still on the table. I would love to see what a web-components based implementation with a central store would look like. You can check the storybook to get an overview of all the states and features we have to consider.

This ticket aims to put together a PoC that can do the following:
-> Have a service that parses the topical/campaign lists to the mobile translation tool; so that there's a way of exposing these lists beyond the current campaign pages/wiki projects.

@GMikesell-WMF this was just merged. It won't be deployed on the diff blog for another month or so. In the meantime, you can test on the demo site, which is always up to date with the main branch.

The edit mode issue was a bit more tricky but here's a fix: https://github.com/wikimedia/wikipediapreview-wordpress/pull/123

Here's a fix for the view mode issue: https://github.com/wikimedia/wikipedia-preview/pull/214

.mf-font-size-clientpref-small .mw-body p, .mf-font-size-clientpref-small .content p {
font-size: 1rem;
}

❌AC2: the marker is not present in the reader's view- The marker is in the reader's view but there's a fainted line in it compared to the edit view

Reader	Edit

https://github.com/wikimedia/wikipedia-preview/pull/213

@SGautam_WMF could you prioritize this? It looks like it could be a quick one.

@sbassett, @mmartorana any idea when this will be looked at? Thanks

@sbassett the Inuka team is considering using floating-ui for Wikipedia-Preview. We would be using @floating-ui/dom, which @floating-ui/vue is based on. Is the review done here sufficient or do we need to go through another round? thanks

On it soon

https://github.com/wikimedia/wikipedia-preview/pull/211

In T362687#9797419, @cchen wrote:

Charts for Usage of the Wikipedia Preview Option on the Editing Tool Bar were added to the Wikipedia Preview dashboard.

New user report about this: https://wordpress.org/support/topic/does-not-work-on-hover/

Removing Diff-blog here. This is mostly about scrollbar differences between browsers.

Hi, I see that this task has been assigned for about a month. Do we have any estimate about when it's going to be done? Thanks

@Jdlrobson would you know how to write a linear-gradient that goes from @background-color-base to transparent? This is what we currently have: background: linear-gradient( to bottom, rgba( 255, 255, 255, 0 ) 0%, #fff 100% ); I would like it to be implemented with variables so it inverts correctly.

In T361626#9761389, @CKoerner_WMF wrote:

Diff CSP has been updated to allow loading of media from *.wikipedia.org (wikimedia.org was already in the list). Images from Wikipedia Preview are now working on Diff.

In T361910#9760410, @SGautam_WMF wrote:

@GMikesell-WMF I am wondering if we have to test it for short URLs too? e.g. https://w.wiki/Wz6 or URLs formed using the page id such as this - https://en.wikipedia.org/?curid=6678