[Bug]: "[error] Translation namespaces" #212

Jipem · 2025-01-18T19:09:00Z

Extension Version

0.1.18

PHP Binary

Local PHP

Operating System

Windows

What happened?

On start of Visual Studio Code :

2025-01-18 20:03:35.974 [info] Checking herd PHP installation: herd which-php
2025-01-18 20:03:35.975 [info] Checking valet PHP installation: valet which-php
2025-01-18 20:03:35.975 [info] Checking local PHP installation: php -r 'echo PHP_BINARY;'
2025-01-18 20:03:35.975 [info] Checking sail PHP installation: ./vendor/bin/sail ps
2025-01-18 20:03:35.975 [info] Falling back to system PHP installation
2025-01-18 20:03:35.975 [error] Translation namespaces

Error: __VSCODE_LARAVEL_START_OUTPUT__
   BadMethodCallException 

  Method Illuminate\Filesystem\Filesystem::json does not exist.

  at D:\jipem\Sites\laragon\www\laravel\vendor\laravel\framework\src\Illuminate\Macroable\Traits\Macroable.php:113
    109▕      */
    110▕     public function __call($method, $parameters)
    111▕     {
    112▕         if (! static::hasMacro($method)) {
  ➜ 113▕             throw new BadMethodCallException(sprintf(
    114▕                 'Method %s::%s does not exist.', static::class, $method
    115▕             ));
    116▕         }
    117▕

  i   Bad Method Call: Did you mean Illuminate\Filesystem\Filesystem::extension() ? 

  1   D:\jipem\Sites\laragon\www\laravel\vendor\laravel\framework\src\Illuminate\Support\Facades\Facade.php:338
      Illuminate\Filesystem\Filesystem::__call("json")

  2   D:\jipem\Sites\laragon\www\laravel\vendor\_laravel_ide\discover-9bf70685f88c341f6dfa31892eff8be2.php:94
      Illuminate\Support\Facades\Facade::__callStatic("json")

2025-01-18 20:03:35.978 [info] Activating Laravel Extension...
2025-01-18 20:03:35.978 [info] Started

Mimimal Code Sample

The text was updated successfully, but these errors were encountered:

HassanZahirnia · 2025-01-22T11:43:47Z

I'm also getting a similar error on WSL2 (Ubuntu)

Version number is 0.1.18

patimio66 · 2025-01-22T12:20:52Z

Got similar error, Windows 11, latest.

Version number is 0.1.18

geraistec · 2025-01-22T13:29:34Z

Same error!

Debian 12.

LukaszJaro · 2025-01-22T16:28:20Z

Same error as @patimio66 running on windows 10. Just installed the extension today.

slaanish · 2025-01-24T18:42:00Z

Same issue as the others, Windows 11 WSL, Right clicking the extension and selecting 1.17 no longer errors.

slaanish · 2025-01-24T18:49:08Z

Taking a look between 1.17 and 1.18, I do see there was a merge that did target language. I do not even pretend to know what is going on, but it does touch language processing and happened between working version and now. All of us appear to be on Windows... A pathing issue? \ vs /

d0f299c

otavio-araujo · 2025-01-27T21:18:37Z

Yep, it works!

andreg · 2025-01-28T16:30:59Z

I'm getting the same error as @patimio66, running on MacOS. Downgrading to 1.17 does apparently fix the issue though.

Braunson · 2025-01-28T20:20:24Z

Same issue on Windows (Sail via WSL) in version 0.1.18

daronspence · 2025-02-10T14:56:27Z

Can confirm this is still an issue on 0.1.18 on macOS. I tried running the generated vendor file directly with some more dd() statements and try/catch for good measure, but I couldn't trace it down.

Downgrading to version 0.1.17 at least stopped the extension from crashing. I was hoping that disabling the Translation options in the extension settings would skip the initialisation, but that seems to not be the case.

The JSON files are valid, though some strings do include HTML. Idk if that may be throwing off a parser somewhere?

joetannenbaum · 2025-02-11T20:26:27Z

I removed the File::json call from the translations repo in v0.1.19, just released. Does that solve this issue or is it still present in the latest version?

Braunson · 2025-02-11T20:40:11Z

@joetannenbaum Same issue (not the same error as OP but translation related) on 0.1.19. Errors out after [info] Started and the error (at least the start of the very long string) is Translation namespaces __VSCODE_LARAVEL_START_OUTPUT__ followed by an output of the en translation JSON.

chosten · 2025-02-11T20:48:50Z

Still present: Error: __VSCODE_LARAVEL_START_OUTPUT__{"default":"en","translations"...

mmuqiitf · 2025-02-12T01:29:27Z

I hope this patch anytime soon because it's really annoying, i always click don't show again

mokhosh · 2025-02-12T11:20:55Z

Still getting it on .19

otavio-araujo · 2025-02-12T11:25:37Z

Yep. The "safe" release is .17 for now... Atenciosamente, Otávio Araújo

…

________________________________ De: Mo Khosh ***@***.***> Enviado: Wednesday, February 12, 2025 8:21:22 AM Para: laravel/vs-code-extension ***@***.***> Cc: Otávio Araújo ***@***.***>; Comment ***@***.***> Assunto: Re: [laravel/vs-code-extension] [Bug]: "[error] Translation namespaces" (Issue #212) Still getting it on .19 — Reply to this email directly, view it on GitHub<#212 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AHIXSG375IRQBDRULCBVBQT2PMVDFAVCNFSM6AAAAABVN4KVT2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJTGQZDEMJTGA>. You are receiving this because you commented.Message ID: ***@***.***>

joetannenbaum · 2025-02-12T14:09:14Z

Would love to get to the bottom of this, I find it strange that you're getting JSON back but it's still erroring. Does anyone have a public repo I can pull down that replicates this?

patimio66 · 2025-02-12T14:15:48Z

@joetannenbaum maybe it's related to VS Code locale? Like to the settings of VS code?

priithansen · 2025-02-12T14:16:03Z

My preliminary testing seems to suggest it's not a particular line or language file causing this error but the amount of translation strings. Seemed that there was a certain amount of lines needed (tested with validation translations) to cause this error to appear. Didn't seem matter which particular lines where present.

joetannenbaum · 2025-02-12T14:17:49Z

My preliminary testing seems to suggest it's not a particular line or language file causing this error but the amount of translation strings. Seemed that there was a certain amount of lines needed (tested with validation translations) to cause this error to appear. Didn't seem matter which particular lines where present.

Yeah this is what I suspected. I'm tempted to add a setting to omit vendor translations, although I'd love to also have a solution to have them properly included as well. I'll continue investigating.

duncanmcclean · 2025-02-12T14:32:16Z

Does anyone have a public repo I can pull down that replicates this?

We have a lot of translation strings in our app/package (Statamic). I can see the error on any Statamic site I touch.

joetannenbaum · 2025-02-12T15:01:21Z

Does anyone have a public repo I can pull down that replicates this?

We have a lot of translation strings in our app/package (Statamic). I can see the error on any Statamic site I touch.

Yup, seeing that too with a fresh install just now. Good place to start, thanks @duncanmcclean 👍

joetannenbaum · 2025-02-13T19:49:49Z

Just released v0.1.20 that should greatly improve (if not fix) this issue. I completely overhauled the translations collection process and the performance + memory usage is much better now.

Let me know how it looks on your end!

patimio66 · 2025-02-13T19:53:29Z

@joetannenbaum looks good on my side! Tried installing the extension from scratch, again, works fine on v0.1.20.

slaanish · 2025-02-13T20:00:44Z

Issues resolved for me as well, thanks!

ghabriel25 · 2025-02-14T01:30:48Z

@joetannenbaum New error. I tried reinstall have the same error

mokhosh · 2025-02-14T11:13:37Z

Resolved for me too. Thanks!

Jipem added the bug label Jan 18, 2025

Jipem assigned joetannenbaum Jan 18, 2025

AnouarTouati linked a pull request Jan 29, 2025 that will close this issue

Fix invalid translation files crashing the extension. #223

Open

victore13 mentioned this issue Feb 4, 2025

[Bug]: Failed to download binary for Laravel extension: php-parser-v0.1.37-x64-linux #230

Open

joetannenbaum mentioned this issue Feb 11, 2025

Stop using File::json for JSON translations #249

Merged

daronspence mentioned this issue Feb 12, 2025

[5.x] Update Dutch translation statamic/cms#11448

Merged

ghabriel25 mentioned this issue Feb 13, 2025

These credentials do not match our records. #242

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Bug]: "[error] Translation namespaces" #212

[Bug]: "[error] Translation namespaces" #212

Jipem commented Jan 18, 2025

HassanZahirnia commented Jan 22, 2025

patimio66 commented Jan 22, 2025

geraistec commented Jan 22, 2025

LukaszJaro commented Jan 22, 2025

slaanish commented Jan 24, 2025

slaanish commented Jan 24, 2025

otavio-araujo commented Jan 27, 2025

andreg commented Jan 28, 2025

Braunson commented Jan 28, 2025 •

edited

Loading

daronspence commented Feb 10, 2025

joetannenbaum commented Feb 11, 2025

Braunson commented Feb 11, 2025 •

edited

Loading

chosten commented Feb 11, 2025

mmuqiitf commented Feb 12, 2025

mokhosh commented Feb 12, 2025

otavio-araujo commented Feb 12, 2025 via email

joetannenbaum commented Feb 12, 2025

patimio66 commented Feb 12, 2025

priithansen commented Feb 12, 2025

joetannenbaum commented Feb 12, 2025

duncanmcclean commented Feb 12, 2025

joetannenbaum commented Feb 12, 2025

joetannenbaum commented Feb 13, 2025

patimio66 commented Feb 13, 2025

slaanish commented Feb 13, 2025

ghabriel25 commented Feb 14, 2025

mokhosh commented Feb 14, 2025 •

edited

Loading

[Bug]: "[error] Translation namespaces" #212

[Bug]: "[error] Translation namespaces" #212

Comments

Jipem commented Jan 18, 2025

Extension Version

PHP Binary

Operating System

What happened?

Mimimal Code Sample

HassanZahirnia commented Jan 22, 2025

patimio66 commented Jan 22, 2025

geraistec commented Jan 22, 2025

LukaszJaro commented Jan 22, 2025

slaanish commented Jan 24, 2025

slaanish commented Jan 24, 2025

otavio-araujo commented Jan 27, 2025

andreg commented Jan 28, 2025

Braunson commented Jan 28, 2025 • edited Loading

daronspence commented Feb 10, 2025

joetannenbaum commented Feb 11, 2025

Braunson commented Feb 11, 2025 • edited Loading

chosten commented Feb 11, 2025

mmuqiitf commented Feb 12, 2025

mokhosh commented Feb 12, 2025

otavio-araujo commented Feb 12, 2025 via email

joetannenbaum commented Feb 12, 2025

patimio66 commented Feb 12, 2025

priithansen commented Feb 12, 2025

joetannenbaum commented Feb 12, 2025

duncanmcclean commented Feb 12, 2025

joetannenbaum commented Feb 12, 2025

joetannenbaum commented Feb 13, 2025

patimio66 commented Feb 13, 2025

slaanish commented Feb 13, 2025

ghabriel25 commented Feb 14, 2025

mokhosh commented Feb 14, 2025 • edited Loading

Braunson commented Jan 28, 2025 •

edited

Loading

Braunson commented Feb 11, 2025 •

edited

Loading

mokhosh commented Feb 14, 2025 •

edited

Loading