Describe the bug
With Deedle and Bristlecone libraries (that use RProvider), we found that a 'Permission Denied' error arises from the type provider constructor when using RProvider 2.0.1-beta3+. This appears to relate to a chmod command being run in RProvider to set execute permissions on the executables in the nuget package cache.
I found through testing that a workaround is to run a small F# script using dotnet fsi before running the setup-dotnet action. For some reason, this stops the 'Permission Denied' error happening later on during solution build.
See error: FS3053 : The type provider 'RProvider.RProvider' reported an error : The type provider constructor has thrown an exception: Permission denied [/home/runner/work/Deedle/Deedle/src/Deedle.RProvider.Plugin/Deedle.RProvider.Plugin.fsproj]
Expected behavior
Build should run and pass correctly. A workaround identified is to add a F# script into the build process as follows:
citest.fsx:
#r "nuget:RProvider,2.0.2"
open RProvider
open RProvider.``base``
open RProvider.zoo
R.c(1.,2.,3)
R.as_zoo(R.c(1,2,3))
Describe the bug With Deedle and Bristlecone libraries (that use RProvider), we found that a 'Permission Denied' error arises from the type provider constructor when using RProvider 2.0.1-beta3+. This appears to relate to a chmod command being run in RProvider to set execute permissions on the executables in the nuget package cache.
I found through testing that a workaround is to run a small F# script using dotnet fsi before running the setup-dotnet action. For some reason, this stops the 'Permission Denied' error happening later on during solution build.
To Reproduce Steps to reproduce the behavior:
Expected behavior Build should run and pass correctly. A workaround identified is to add a F# script into the build process as follows:
citest.fsx:
build:
Environment (please complete the following information):
Additional context Add any other context about the problem here.