ionide / ionide/FsAutoComplete
Since 0.84.0, cannot pass test stage anymore
- Dominant language
- F#
- Stars
- 486
- Forks
- 169
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 5
Description
### Version
v0.84.0
### Dotnet Info
```
.NET SDK:
Version: 10.0.111
Commit: e2f47b0110
Workload version: 10.0.100-manifests.330ea142
MSBuild version: 18.0.11
Runtime Environment:
OS Name: arch
OS Version:
OS Platform: Linux
RID: arch-x64
Base Path: /usr/share/dotnet/sdk/10.0.111/
.NET workloads installed:
There are no installed workloads to display.
Configured to use workload sets when installing new manifests.
No workload sets are installed. Run "dotnet workload restore" to install a workload set.
Host:
Version: 10.0.11
Architecture: x64
Commit: e2f47b0110
.NET SDKs installed:
10.0.111 [/usr/share/dotnet/sdk]
.NET runtimes installed:
Microsoft.AspNetCore.App 10.0.11 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 10.0.11 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
Other architectures found:
None
Environment variables:
DOTNET_CLI_TELEMETRY_OPTOUT [1]
global.json file:
Not found
```
### Steps to reproduce
I am the maintainer of the `fsautocomplete` AUR package. The below is what I do to build + test (i.e., in my `PKGBUILD` [here](https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=fsautocomplete)), and which worked with 0.83.0:
```bash
export DOTNET_CLI_TELEMETRY_OPTOUT=1
export DOTNET_NOLOGO=1
export DOTNET_SKIP_FIRST_TIME_EXPERIENCE=1
export DOTNET_ROLL_FORWARD_TO_PRERELEASE=1
export BuildNet10=true
export DOTNET_CLI_HOME="${srcdir}/.dotnet-home"
export NUGET_PACKAGES="${srcdir}/.nuget"
export PATH="${DOTNET_CLI_HOME}/.dotnet/tools:${PATH}"
dotnet tool restore
dotnet publish src/${_name}/${_name}.fsproj \
--configuration Release \
--framework "net${_sdk}" \
--output "${srcdir}/publish"
dotnet test test/${_name}.Tests.Lsp/${_name}.Tests.Lsp.fsproj \
--configuration Release \
--framework "net${_sdk}" \
--logger "console;verbosity=normal"
```
### Details
- Expected: 0.84.0 to build
- Actual: build failure
### Logs
I snipped all the prior-to-first-error part of the log, it was very long. Still 3k lines, so I attached it as a file.
[console.log](https://github.com/user-attachments/files/31605510/console.log)
### Checklist
- [x] I have looked through existing issues to make sure that this bug has not been reported before
- [x] I have provided a descriptive title for this issue
- [x] I have made sure that that this bug is reproducible on the latest version of the package
- [x] I have provided all the information needed to reproduce this bug as efficiently as possible
- [x] I or my company would be willing to contribute this fix
Contributor guide
Research direction
Start with the attached console.log and identify the first build error, then reproduce it with the dotnet publish and dotnet test commands shown. Inspect src/${_name}/${_name}.fsproj and test/${_name}.Tests.Lsp/${_name}.Tests.Lsp.fsproj for the failing configuration. Done means the 0.84.0 package builds and its test stage passes under the reported .NET environment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- build-system, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 63/100