It does look like Translations is currently broken in Nightly, unfortunately.
I investigated this a bit, and it appears to be the use of `setTimeout()` for the TranslationsEngine cache timers.
```
Translations: The engine failed to load for translating "es -> en". Removing it from the cache. ReferenceError: setTimeout is not defined
keepAlive chrome://global/content/translations/translations-engine.sys.mjs:332
isReady** chrome://global/content/translations/translations-engine.sys.mjs:396
TranslationsEngine** chrome://global/content/translations/translations-engine.sys.mjs:375
create chrome://global/content/translations/translations-engine.sys.mjs:260
```
This didn't fail our integration or end-to-end tests in CI because we manually manage the lifetimes of the engines in the test cleanup, but in production they are managed by a keep-alive timeout [here](https://searchfox.org/mozilla-central/rev/2097b2f70189bffff5e19d2a14ec113f7af4f2f3/toolkit/components/translations/content/translations-engine.sys.mjs#293-305).
---
:nika, I am leaving your NI open because I am not sure how you patch affected this behavior, and I'm still interested to hear your input.
Bug 1946964 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
It does look like Translations is currently broken in Nightly, unfortunately.
I investigated this a bit, and it appears to be the use of `setTimeout()` for the TranslationsEngine cache timers.
```
Translations: The engine failed to load for translating "es -> en". Removing it from the cache. ReferenceError: setTimeout is not defined
keepAlive chrome://global/content/translations/translations-engine.sys.mjs:332
isReady chrome://global/content/translations/translations-engine.sys.mjs:396
TranslationsEngine** chrome://global/content/translations/translations-engine.sys.mjs:375
create chrome://global/content/translations/translations-engine.sys.mjs:260
```
This didn't fail our integration or end-to-end tests in CI because we manually manage the lifetimes of the engines in the test cleanup, but in production they are managed by a keep-alive timeout [here](https://searchfox.org/mozilla-central/rev/2097b2f70189bffff5e19d2a14ec113f7af4f2f3/toolkit/components/translations/content/translations-engine.sys.mjs#293-305).
---
:nika, I am leaving your NI open because I am not sure how you patch affected this behavior, and I'm still interested to hear your input.
It does look like Translations is currently broken in Nightly, unfortunately.
I investigated this a bit, and it appears to be the use of `setTimeout()` for the TranslationsEngine cache timers.
```
Translations: The engine failed to load for translating "es -> en". Removing it from the cache.
ReferenceError: setTimeout is not defined
keepAlive chrome://global/content/translations/translations-engine.sys.mjs:332
isReady chrome://global/content/translations/translations-engine.sys.mjs:396
TranslationsEngine** chrome://global/content/translations/translations-engine.sys.mjs:375
create chrome://global/content/translations/translations-engine.sys.mjs:260
```
This didn't fail our integration or end-to-end tests in CI because we manually manage the lifetimes of the engines in the test cleanup, but in production they are managed by a keep-alive timeout [here](https://searchfox.org/mozilla-central/rev/2097b2f70189bffff5e19d2a14ec113f7af4f2f3/toolkit/components/translations/content/translations-engine.sys.mjs#293-305).
---
:nika, I am leaving your NI open because I am not sure how you patch affected this behavior, and I'm still interested to hear your input.
It does look like Translations is currently broken in Nightly, unfortunately.
I investigated this a bit, and it appears to be the use of `setTimeout()` for the TranslationsEngine cache timers.
```
Translations: The engine failed to load for translating "es -> en". Removing it from the cache.
ReferenceError: setTimeout is not defined
keepAlive chrome://global/content/translations/translations-engine.sys.mjs:332
isReady chrome://global/content/translations/translations-engine.sys.mjs:396
TranslationsEngine** chrome://global/content/translations/translations-engine.sys.mjs:375
create chrome://global/content/translations/translations-engine.sys.mjs:260
```
This didn't fail our integration or end-to-end tests in CI because we manually manage the lifetimes of the engines in the test cleanup, to ensure deterministic and consistent stability between test cases, but in production they are managed by a keep-alive timeout [here](https://searchfox.org/mozilla-central/rev/2097b2f70189bffff5e19d2a14ec113f7af4f2f3/toolkit/components/translations/content/translations-engine.sys.mjs#293-305).
---
:nika, I am leaving your NI open because I am not sure how you patch affected this behavior, and I'm still interested to hear your input.
It does look like Translations is currently broken in Nightly, unfortunately.
I investigated this a bit, and it appears to be the use of `setTimeout()` for the TranslationsEngine cache timers.
```
Translations: The engine failed to load for translating "es -> en". Removing it from the cache.
ReferenceError: setTimeout is not defined
keepAlive chrome://global/content/translations/translations-engine.sys.mjs:332
isReady chrome://global/content/translations/translations-engine.sys.mjs:396
TranslationsEngine** chrome://global/content/translations/translations-engine.sys.mjs:375
create chrome://global/content/translations/translations-engine.sys.mjs:260
```
This didn't fail our integration or end-to-end tests in CI because we manually manage the lifetimes of the engines in the test cleanup in order toto ensure deterministic and consistent stability between test cases, but in production they are managed by a keep-alive timeout [here](https://searchfox.org/mozilla-central/rev/2097b2f70189bffff5e19d2a14ec113f7af4f2f3/toolkit/components/translations/content/translations-engine.sys.mjs#293-305).
---
:nika, I am leaving your NI open because I am not sure how you patch affected this behavior, and I'm still interested to hear your input.
It does look like Translations is currently broken in Nightly, unfortunately.
I investigated this a bit, and it appears to be the use of `setTimeout()` for the TranslationsEngine cache timers.
```
Translations: The engine failed to load for translating "es -> en". Removing it from the cache.
ReferenceError: setTimeout is not defined
keepAlive chrome://global/content/translations/translations-engine.sys.mjs:332
isReady chrome://global/content/translations/translations-engine.sys.mjs:396
TranslationsEngine** chrome://global/content/translations/translations-engine.sys.mjs:375
create chrome://global/content/translations/translations-engine.sys.mjs:260
```
This didn't fail our integration or end-to-end tests in CI because we manually manage the lifetimes of the engines in the test cleanup in order to ensure deterministic and consistent stability between test cases, but in production they are managed by a keep-alive timeout [here](https://searchfox.org/mozilla-central/rev/2097b2f70189bffff5e19d2a14ec113f7af4f2f3/toolkit/components/translations/content/translations-engine.sys.mjs#293-305).
---
:nika, I am leaving your NI open because I am not sure how you patch affected this behavior, and I'm still interested to hear your input.
It does look like Translations is currently broken in Nightly, unfortunately.
I investigated this a bit, and it appears to be the use of `setTimeout()` for the TranslationsEngine cache timers.
```
Translations: The engine failed to load for translating "es -> en". Removing it from the cache.
ReferenceError: setTimeout is not defined
keepAlive chrome://global/content/translations/translations-engine.sys.mjs:332
isReady chrome://global/content/translations/translations-engine.sys.mjs:396
TranslationsEngine** chrome://global/content/translations/translations-engine.sys.mjs:375
create chrome://global/content/translations/translations-engine.sys.mjs:260
```
This didn't fail our integration or end-to-end tests in CI because we manually manage the lifetimes of the engines in the test cleanup in order to ensure deterministic and consistent state between test cases, but in production they are managed by a keep-alive timeout [here](https://searchfox.org/mozilla-central/rev/2097b2f70189bffff5e19d2a14ec113f7af4f2f3/toolkit/components/translations/content/translations-engine.sys.mjs#293-305).
---
:nika, I am leaving your NI open because I am not sure how you patch affected this behavior, and I'm still interested to hear your input.
It does look like Translations is currently broken in Nightly, unfortunately.
I investigated this a bit, and it appears to be the use of `setTimeout()` for the TranslationsEngine cache timers.
**Error Log**
```
Translations: The engine failed to load for translating "es -> en". Removing it from the cache.
ReferenceError: setTimeout is not defined
keepAlive chrome://global/content/translations/translations-engine.sys.mjs:332
isReady chrome://global/content/translations/translations-engine.sys.mjs:396
TranslationsEngine** chrome://global/content/translations/translations-engine.sys.mjs:375
create chrome://global/content/translations/translations-engine.sys.mjs:260
```
**Note**
This didn't fail our integration or end-to-end tests in CI because we manually manage the lifetimes of the engines in the test cleanup in order to ensure deterministic and consistent state between test cases, but in production they are managed by a keep-alive timeout [here](https://searchfox.org/mozilla-central/rev/2097b2f70189bffff5e19d2a14ec113f7af4f2f3/toolkit/components/translations/content/translations-engine.sys.mjs#293-305).
---
:nika, I am leaving your NI open because I am not sure how you patch affected this behavior, and I'm still interested to hear your input.
It does look like Translations is currently broken in Nightly, unfortunately.
I investigated this a bit, and it appears to be the use of `setTimeout()` for the TranslationsEngine cache timers.
**Error Log**
```
Translations: The engine failed to load for translating "es -> en". Removing it from the cache.
ReferenceError: setTimeout is not defined
keepAlive chrome://global/content/translations/translations-engine.sys.mjs:332
isReady chrome://global/content/translations/translations-engine.sys.mjs:396
TranslationsEngine** chrome://global/content/translations/translations-engine.sys.mjs:375
create chrome://global/content/translations/translations-engine.sys.mjs:260
```
**Note**
This didn't fail our integration or end-to-end tests in CI because we manually manage the lifetimes of the engines in the test cleanup functions to ensure the state of the engine cache is deterministic and consistent between test cases, but in production they are managed by a keep-alive timeout [here](https://searchfox.org/mozilla-central/rev/2097b2f70189bffff5e19d2a14ec113f7af4f2f3/toolkit/components/translations/content/translations-engine.sys.mjs#293-305).
---
:nika, I am leaving your NI open because I am not sure how you patch affected this behavior, and I'm still interested to hear your input.
It does look like Translations is currently broken in Nightly, unfortunately.
I investigated this a bit, and it appears to be the use of `setTimeout()` for the TranslationsEngine cache timers.
**Error Log**
```
Translations: The engine failed to load for translating "es -> en". Removing it from the cache.
ReferenceError: setTimeout is not defined
keepAlive chrome://global/content/translations/translations-engine.sys.mjs:332
isReady chrome://global/content/translations/translations-engine.sys.mjs:396
TranslationsEngine** chrome://global/content/translations/translations-engine.sys.mjs:375
create chrome://global/content/translations/translations-engine.sys.mjs:260
```
**Note**
This didn't fail our integration or end-to-end tests in CI because we manually manage the lifetimes of the engines in the test cleanup functions to ensure the state of the engine cache is deterministic and consistent between test cases, but in production they are managed by a keep-alive timeout [here](https://searchfox.org/mozilla-central/rev/2097b2f70189bffff5e19d2a14ec113f7af4f2f3/toolkit/components/translations/content/translations-engine.sys.mjs#293-305).
---
I'm marking this as S2 P1, matching the following description:
> **S2**: (Serious) Major functionality/product severely impaired or a high impact issue and a satisfactory workaround does not exist
This is only in Nightly right now, but we should get this fixed ASAP, since it appears to be broken on all platforms.
---
:nika, I am leaving your NI open because I am not sure how you patch affected this behavior, or if it is intended that `setTimeout()` should no longer be available. I'm interested to hear your input.
It does look like Translations is currently broken in Nightly, unfortunately.
I investigated this a bit, and it appears to be the use of `setTimeout()` for the TranslationsEngine cache timers.
**Error Log**
```
Translations: The engine failed to load for translating "es -> en". Removing it from the cache.
ReferenceError: setTimeout is not defined
keepAlive chrome://global/content/translations/translations-engine.sys.mjs:332
isReady chrome://global/content/translations/translations-engine.sys.mjs:396
TranslationsEngine** chrome://global/content/translations/translations-engine.sys.mjs:375
create chrome://global/content/translations/translations-engine.sys.mjs:260
```
**Note**
This didn't fail our integration or end-to-end tests in CI because we manually manage the lifetimes of the engines in the test cleanup functions to ensure the state of the engine cache is deterministic and consistent between test cases, but in production they are managed by a keep-alive timeout [here](https://searchfox.org/mozilla-central/rev/2097b2f70189bffff5e19d2a14ec113f7af4f2f3/toolkit/components/translations/content/translations-engine.sys.mjs#293-305).
---
I'm marking this as S2 P1, matching the following [description](https://wiki.mozilla.org/BMO/UserGuide/BugFields#bug_severity):
> **S2**: (Serious) Major functionality/product severely impaired or a high impact issue and a satisfactory workaround does not exist
This is only in Nightly right now, but we should get this fixed ASAP, since it appears to be broken on all platforms.
---
:nika, I am leaving your NI open because I am not sure how you patch affected this behavior, or if it is intended that `setTimeout()` should no longer be available. I'm interested to hear your input.
It does look like Translations is currently broken in Nightly, unfortunately.
I investigated this a bit, and it appears to be the use of `setTimeout()` for the TranslationsEngine cache timers.
**Error Log**
```
Translations: The engine failed to load for translating "es -> en". Removing it from the cache.
ReferenceError: setTimeout is not defined
keepAlive chrome://global/content/translations/translations-engine.sys.mjs:332
isReady chrome://global/content/translations/translations-engine.sys.mjs:396
TranslationsEngine** chrome://global/content/translations/translations-engine.sys.mjs:375
create chrome://global/content/translations/translations-engine.sys.mjs:260
```
**Note**
This didn't fail our integration or end-to-end tests in CI because we manually manage the lifetimes of the engines in the test cleanup functions to ensure the state of the engine cache is deterministic and consistent between test cases, but in production they are managed by a keep-alive timeout [here](https://searchfox.org/mozilla-central/rev/2097b2f70189bffff5e19d2a14ec113f7af4f2f3/toolkit/components/translations/content/translations-engine.sys.mjs#293-305).
---
I'm marking this as S2 P1, matching the following [description](https://wiki.mozilla.org/BMO/UserGuide/BugFields#bug_severity):
> **S2**: (Serious) Major functionality/product severely impaired or a high impact issue and a satisfactory workaround does not exist
This is only in Nightly right now, but we should get this fixed ASAP, since it appears to be broken on all platforms.
---
:nika, I am leaving your NI open because I am not sure how you patch affected this behavior, or if it is intended that `setTimeout()` should no longer be available within the inference process. I'm interested to hear your input.