error MSB6006: "wsfsc.sh" exited with code 134. #1044
Labels
Comments
|
Hard to say with just this. Can you change the call to MSBuild in your FAKE script to increase verbosity? That should give us a stack trace. |
|
Hi Loïc, Thanks for your quick reply. I tried again with MSBuild logging level Normal, Detailed and above are truncated by the buildserver. Even this log level seems quite verbose and there is no exception logged. I fear that this is because there is a bash script in between and the stdout is not captured by MSBuild... I'll post the whole thing anyways below. Do you have an idea how to get the log output of that forked Process? |
|
Fixed it by downgrading one version of websharper: Maybe it has something to do with 325ad2c |
|
That's a likely cause indeed. If so, then it may be the same issue as #1045. |
|
@ajuch Hello, assembly redirect issues should be resolved by latest release https://github.com/dotnet-websharper/core/releases/tag/4.5.9.330 |
|
@Jand42 Sorry, just tried building again with the new WebSharper 4.5.330 packages but without success :-( It still fails with the same exception. So my problem seems to be unrelated to the assembly redirect issues... I looked at |
|
I created a minimal example that fails on my computer: https://github.com/ajuch/ws-1044 A simple |
|
Thanks! I've been able to reproduce the issue on a Linux VPS I have, but the docker setup should be more convenient to investigate. |
|
Based on my investigations, the issue seems to have appeared when we upgraded FSharp.Compiler.Service from 25.0 to 26.0. This means that downgrading WebSharper (and more importantly WebSharper.FSharp) to version 4.5.7.322 should be good as a temporary workaround while the core issue gets fixed. |
|
Ok, that's what I'm doing now :-) |
|
Anonymous records in WebSharper do depend on the FSharp.Compiler.Service 27.0, so downgrading will make you lose that unfortunately. |
|
These 'bad' versions are coded into the templates provided by the current |
|
@lmortimer Hi, there is a new Fsharp.Compiler.Service, I will test updating and will get back to you. Also, as a workatound, you can install an older template with an earlier FCS with |
|
@lmortimer https://github.com/dotnet-websharper/core/releases/tag/4.5.11.334 contains a newer FCS and a fix for an underlying issue on netcore sdk 2.1.600+ |
I was wrong. The build works, but in the runtime docker image all the WebSharper translated code is missing... |
|
@ajuch Thanks for the details, I guess you have this default {
"$schema": "https://websharper.com/wsconfig.schema.json",
"project": "site",
"outputDir": "wwwroot"
}Or equivalent settings in <WebSharperProject>Website</WebSharperProject>
<WebProjectOutputDir>$(MSBuildThisFileDirectory)/wwwroot</WebProjectOutputDir>(The values in Also, do you have issue with Docker only? I am testing that soon. Thanks! |
|
@Jand42 Yes, I have exactly that wsconfig.json file in the Website Project. I have this issue with docker only, but I don't have a linux workstation to test, so I cannot say if it's linux or docker related... |
|
@ajuch I have tested in Docker since, and found that the issue is caused by the WebSharper.UI templating type provider during reading by FCS. (WebSharper goes through non-JavaScript code too to search for |
|
@Jand42 Thank you, that's great news! I tried changing the call inside wsfsc.sh to redirect stdout and stderr to a file to get a stacktrace, but didn't succeed. Maybe if done right, it could provide a stacktrace... |
|
Hello! I'm also hitting this -- and I'm using both Linux (local dev) and Docker. If there's any additional info I can help provide, please let me know? (I can reproduce this issue by installing the latest WebSharper template and trying to build it, but it also affects my other WebSharper projects.) |
|
Hi, I found something... WebSharper uses FSharp.Compiler.Service in Version 28.0. In this commit fsharp/fsharp-compiler-docs@1257ce8#diff-a5449c600acbdb1ab940f4621d4b985b (Exprs.fsi) the namespace was changed from |
|
@ajuch Sorry for replying late but this is not an issue: Workaround is still to revert to WS 4.5.7.322 for having FCS 25.0. I had an idea to install Mono in the Docker instance too, and use |
|
@Jand42 do you already have any idea how to solve this issue? |
|
@ajuch And using a verbosity flag |
|
Hi @Jand42, I updated my minimal example at https://github.com/ajuch/ws-1044 and still get the error, even with |
|
Hi all -- I'm running hard in to this trying to update to dotnet 3.0. I'd love to help get this fixed. Unfortunately, I can't get this repo to build on my (linux) machine, so I might require a little guidance on what the most productive thing to do is. One thing worth noting: my new error status is 150, not 134. |
|
Okay. At least for my own case, I've figured enough out to get myself fixed. I dunno how much this'll help the other folk on this thread, but just in case: here's what I've got. The problem is coming from I'm still... not great at reasoning about the broad matrix of which-SDK-supports-which-standard-is-compatible-with-which-other-thing in .NET land; this doesn't sound to me like it would fix anyone else's problem, but it might help diagnose it. If anyone wants instructions for |
|
@Gastove I'll go ahead and investigate the build issue with dotnet 3.0 and get back to you with my findings. Thank you for looking into the logs of the Docker image with |
|
@Jooseppi12 Any progress on that? |
|
After upgrading my whole solution to .net Core 3.0 I can confirm that the new error code is 150 @Jooseppi12 do you have any idea what causes this? |
|
Seems I am now at the point where Gastove is. The wsfsc call outputs: |
|
@ajuch that looks very familiar to me! I was able to solve it for myself by installing the 2.0 SDK in my docker image: https://gitlab.com/gastove/containers/blob/master/Dockerfile.DotnetBuilder#L19 slightly clunky, but it works. |
|
This also happens for me and I'm not using docker. On a fresh machine (Pop!_OS 19.10), I followed the instructions to install .NET Core. Then I installed the WebSharper templates: Then I created a new Web project: Then I tried to build it: Here is the output: The output of |
|
Like @Gastove said, if I also install v2 SDK, it builds just fine. |
|
Just seconding this. One solution is to edit |
|
@granicz and @Tarmil, this blocked the-benchmarker/web-frameworks#2874 from building successfully. All the frameworks in that comparison use .NET Core 3.1, and as it's running on docker, I don't have a good way to change the runtime config above. Any suggestions? I temporarily removed WebSharper from the framework comparison, but I'm happy to fix it once I know how. |
|
@panesofglass Thanks for the notice. I have a pending experiment for having both .NETCore 2.0 and 3.1 compilers (latter used for netcoreapp3.0+ and netstandard2.1+ automatically, otherwise using 2.0 one). I had ran into nuget packaging problems, it grew too big maybe and paket have created some disfunctional packages. At this point I think it is better to just require .NET Core 3.1 runtime installed for the WebSharper.FSharp/CSharp compilers when running on DNC, having the back-compatibility for non up-to-date build boxes does not worth the package size bloat. |
3 tasks
|
@Jand42 any news on this? I can't get past this error at all on local any more, even with all the SDKs installed. Bumping any versions -- especially dotnet -- seems to avail me nothing. Can I help push on this somewhere? I've got no intuition at all about which part of WebSharper is causing the problems, but I'd be happy to go help with a bit of guidance. |
|
Ah, sorry, just saw all the .NET5.0 tickets. I bet those will help. |
|
@Jand42 what's your status on this? |
|
@granicz @Gastove Since WebSharper 4.6.4.404, compiler runs on netcore3.1, so it should resolve hard assembly redirect fails on .NET Core 3.1. I think I remember Docker build passing but have not commented about it here... will retest soon. Maybe it needs a |
|
Hello, Excuse me, I am re-launching this issue probably a little late. I got the error that was raised, but unfortunately, nothing that was discussed here allowed me to correct the problem... I'm running Pop_OS! and I followed the conventional .net and websharper installation steps: The error displayed then is the following: I tested the same thing on a Windows, but there everything worked fine. I also tried to downgrade the version of websharper, as suggested earlier in the issue, but the problem remains the same. An F# project without template also works well for me.
Is there any news about this problem, which might not have been published in this issue? |
|
I am curious about what @Gastove reported earlier: "The chain of invocations that lead to wsfsc.sh starting up seems to have the effect of totally swallowing its output." Has anyone checked into how to fix that? |
|
I had the same issue today. To find the cause you need to
After installing the .NET SDK 3.1, everything worked. |
|
@Jand42 We should really upgrade everything to net5+, including the template deps for ASP.NET Core apps. Can you quote the ticket for that work so we can track? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since switching to a FAKE-based buildscript I have trouble building a WebSharper project. I have no idea where the SIGABRT (134) is coming from. Same build script works fine on my windows desktop, but on the linux buildserver with docker it fails...
I'd be glad for any advice to debug that issue!
br, Andreas
The text was updated successfully, but these errors were encountered: