Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Non deterministic base dir in stack traces #8883

Closed
NinoFloris opened this issue Apr 6, 2020 · 5 comments · Fixed by #9874
Closed

Non deterministic base dir in stack traces #8883

NinoFloris opened this issue Apr 6, 2020 · 5 comments · Fixed by #9874
Labels

Comments

@NinoFloris
Copy link
Contributor

SDK: 3.1.102

System.InvalidOperationException: ValueOption.Value
   at Microsoft.FSharp.Core.FSharpValueOption`1.get_Value() in E:\A\_work\130\s\src\fsharp\FSharp.Core\prim-types.fs:line 2934

It seems something broke in this area which caused non deterministic paths to be shipped.

@cartermp
Copy link
Contributor

cartermp commented Apr 9, 2020

@NinoFloris can you share a repro? I assume you're using PathMap?

@NinoFloris
Copy link
Contributor Author

NinoFloris commented Apr 9, 2020

Ha yes there were clues in the trace but, ValueOption<int>.ValueNone.Value does the trick 😃 (probably any exception from Fsharp.core)

@NinoFloris
Copy link
Contributor Author

Any luck here @cartermp ?

@cartermp
Copy link
Contributor

Sorry, I initially misunderstood the bug here. Yes, there's no PathMap getting applied to FSharp.Core and it's just including the path of the CI machine it was built and shipped on. cc @brettfo @jonsequitur

@baronfel
Copy link
Member

baronfel commented Aug 3, 2020

@KevinRansom per the discussion on #9379 (and the deeper issue linked in dotnet/msbuild#5398), would it make sense to copy/paste or translate the existing MapSourceRoot task + target file changes into here, including tests? If so, I can have those changes ready to go shortly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants