[PP-1] Race condition with locale javascript translation generation

Created on 30 April 2018, about 6 years ago

Updated 28 August 2023, 10 months ago

When we run our behat tests suite we run into a notice being shown on test pages from time to time:

User Notice: Warning: file_get_contents(public://languages/de_k6dYjbIG0GfEJl3YPQE4ZRnL5Rg9BPdBO3slQkKDHL0.js): failed to open stream: "Drupal\Core\StreamWrapper\PublicStream::stream_open" call failed in Drupal\Core\Asset\JsOptimizer->optimize() (line 25 of /srv/default/vcs/web/core/lib/Drupal/Core/Asset/JsOptimizer.php) #0 /srv/default/vcs/web/core/includes/bootstrap.inc(582): _drupal_error_handler_real(2, 'file_get_conten...', '/srv/default/vc...', 25,

However, with further debugging the error is not reproducible in any way during regular site operation (with any kind of state of caches and state). I think it's caused by a race condition when the behat + drupal driver process and a request trigger both the generation of the same file, as in watchdog the notice of locale translation being triggered can be found twice in the "error" case.

🐛 Bug report

Status

Postponed

Version

11.0 🔥

Component

Locale →

Last updated 3 days ago

Maintained by
🇭🇺Hungary @Gábor Hojtsy

Created by

🇦🇹Austria fago Vienna

Live updates comments and jobs are added and updated live.

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment 10 months ago →
🇬🇧United Kingdom catch
🐛 Stampedes and cold cache performance issues with css/js aggregation Fixed is committed now, but I don't really see how it affect this. I still think this is is a duplicate of 📌 Remove on-demand JavaScript translation parsing and do everything on rebuild Needs work , moving to 'postponed' and to the locale module.
Comment 10 months ago →
🇷🇴Romania alex.stanciu
Just wanted to say that we experienced this on a (quite high-traffic) production site today. We saw hundreds of occurences in the logs. With no alternative, we disabled JS aggregation until we have an official solution.

contrib.social Blog FAQ Discussions

Production build 0.69.0 2024