Web compiler exited with 133

Question

Web compiler exited with 133

mikes-gh opened this issue 2 years ago · comments

Is there anyway to get more information from the failure.

  Tool 'excubo.webcompiler' (version '3.4.0-preview.1') was restored. Available commands: webcompiler
  
  Restore was successful.
/Users/mikes/Documents/Repos/MudBlazor/src/MudBlazor/MudBlazor.csproj(83,5): error MSB3073: The command "dotnet webcompiler ./Styles/MudBlazor.scss -c excubowebcompiler.json" exited with code 133.

I have changed the OutputStyle from Nested to Expanded and removed the Precision parameter

Stefan Lörwald · Answer 1 · Sat Oct 22 2022 22:24:03 GMT+0800 (China Standard Time)

That would be nice, but it seems like one of those situations where this tool doesn't propagate the error message correctly. It would be very helpful if you could debug this and see which command fails.

Mike Surcouf · Answer 2 · Sat Oct 22 2022 23:04:38 GMT+0800 (China Standard Time)

Debug gives expected results and exit code 0.
Perhaps its a packaging thing?
I am doing a
dotnet tool restore
Tool 'excubo.webcompiler' (version '3.4.0-preview.1') was restored
in my csprog

Stefan Lörwald · Answer 3 · Sat Oct 22 2022 23:53:38 GMT+0800 (China Standard Time)

Some of the package dependencies might not be compatible with net7.0 yet? It might just work in debug because of an older SDK.

Mike Surcouf · Answer 4 · Sat Oct 22 2022 23:59:50 GMT+0800 (China Standard Time)

Yes I have net SDK 6 and 7 on my machine

Mike Surcouf · Answer 5 · Sun Oct 23 2022 00:01:21 GMT+0800 (China Standard Time)

I'll have a look at the dependencies

Mike Surcouf · Answer 6 · Sun Oct 23 2022 01:26:35 GMT+0800 (China Standard Time)

The only dependency that looks like it might need updating
Microsoft.Extensions.FileSystemGlobbing
Version 6.0.0 to. 7.0.0-rc.2.22472.3

However I tried updating that on a private package and it didn't seem to make any difference.
It does fail locally on build though with SDK 6 and 7 installed.

Stefan Lörwald · Answer 7 · Sun Oct 30 2022 21:47:20 GMT+0800 (China Standard Time)

I don't think this is something we can solve here. Most likely, it's an incompatibility between net7 and the js runtime and we'll have to wait for that to be updated.

koma-tompit · Answer 8 · Mon Dec 19 2022 22:30:04 GMT+0800 (China Standard Time)

Hi, has there been any changes around this? I've encountered the same error today. The build works fine on a Windows PC, but displays the following error on MacOS:

Fatal error in , line 0
Check failed: 12 == (*__error()).

FailureMessage Object: 0x7ff7b43fd220

Stefan Lörwald · Answer 9 · Mon Dec 19 2022 22:48:34 GMT+0800 (China Standard Time)

Hi @koma-tompit,

I'm not working with net7.0 and therefore can't meaningfully contribute to identifying the root cause of this. It's unlikely that this is an issue with this project, as previous similar issues have all been around the js runtime.

Cheers
Stefan

koma-tompit · Answer 10 · Tue Dec 20 2022 00:22:20 GMT+0800 (China Standard Time)

Hi @koma-tompit,

I'm not working with net7.0 and therefore can't meaningfully contribute to identifying the root cause of this. It's unlikely that this is an issue with this project, as previous similar issues have all been around the js runtime.

Cheers Stefan

It does indeed smell of a js runtime issue. Would you kindly point me in the direction of the code where it plugs into the compiler? I'll try and poke at it myself, but am quite pressed for time these days.