Inifinite resolution of Azure Function Host (v2) dependencies
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Description
There is a famous issue with binding redirects in Azure Functions. So I've tried to create a .lock file for Azure Function Host to help everyone check their packages against all the restrictions.
(Added: this is for runtime v2)
I took Host dependencices from here
Binding redirects lies here
Repro steps
-
Clone this repo
-
Paket Install
Expected behavior
Appearance of paket.lock eventually
Actual behavior
Infinite cycle of two resolutions
Conflict detected:
- Microsoft.CodeAnalysis.CSharp.Scripting 2.4.0 requested package Microsoft.CodeAnalysis.CSharp: 2.4
- Microsoft.CodeAnalysis.CSharp.Workspaces 2.6.0 requested package Microsoft.CodeAnalysis.CSharp: 2.6
Conflict detected:
- NuGet.LibraryModel 4.4.0 requested package NuGet.Common: >= 4.4
- NuGet.Configuration 4.6.2 requested package NuGet.Common: >= 4.6.2
Known workarounds
None
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Clone the linked azure-func-paket repository and run Paket Install to reproduce the resolution cycle. Compare the dependencies in WebJobs.Script.csproj with the binding redirects in app.config, focusing on the conflicting Microsoft.CodeAnalysis and NuGet packages. Done means Paket completes and produces paket.lock without looping.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100