search

excubo-ag / WebCompiler

Apache License 2.0
148 stars 29 forks source link

Web compiler exited with 133 #69

Closed mikes-gh closed 1 year ago

mikes-gh commented 1 year ago

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

stefanloerwald commented 1 year ago

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.

mikes-gh commented 1 year ago

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

stefanloerwald commented 1 year ago

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

mikes-gh commented 1 year ago

Yes I have net SDK 6 and 7 on my machine

mikes-gh commented 1 year ago

I'll have a look at the dependencies

mikes-gh commented 1 year ago

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.

stefanloerwald commented 1 year ago

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 commented 1 year ago

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

stefanloerwald commented 1 year ago

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 commented 1 year ago

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.

mikes-gh commented 1 year ago

@stefanloerwald I can report I am using

3.5.44 on

Apple Intel Apple ARM Linux x64 GitHubCodeSpaces

net6 and net7

All without error

So I am going to close this.