-
Notifications
You must be signed in to change notification settings - Fork 61
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
Worried about the Diamond dependency problem #187
Comments
I'm currently struggling with the following error, might that be caused by exactly what you're describing here?
|
Possibly? Might need more context. Could also be missing the DLL in the directory of where ever you are running. |
Well, I’m still investigating. It happens with However, same solution on one system succeeds, in CI it succeeds, but not on mine, not on one other. All systems had the Ply error, but only some have the above. Even after cleaning/clearing caches etc. Still investigating. Will let you know, but may be hard to make a small repo. Oh, also surprising, some functions that do use TaskResult, succeed. Some others fail. |
It may be a dependency that itself uses F# task, and somehow this conflicts. But still, why it’s differently behaving per system is weird. |
Meanwhile sorted it out. The problem was caused by some functions using helpers from our own Nuget package store that in turn used a 2.x FsToolkit. Upgrading that package to use the newer FsToolkit solved the issue. My guess is that a conflict arose with these functions defaulting to Ply tasks, which ultimately caused a runtime error. Why it wasn't caught as a compile time error, I don't know. I tried to create a minimal repro, but each time I dumbed it down, it "just worked". |
I got the same issue: After updating from the 2.3.1 version, I see this runtime error. |
Is your feature request related to a problem? Please describe.
I'm worried about diamond dependencies with this project. As it grows more popular, more things will start relying on it and start causing conflicts with consumers.
For example, seeing packages constraining the upper limit can possibly slow adoption.
Describe the solution you'd like
Since this is just a pile of functions without much in the way of dependencies usually, it might want to explore this Source package approach.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: