Repository navigation
[Ready] Fix/refactor/improve framework restriction system, add performance metrics and pre-load requests - #2336
Merged
Merged
Conversation
Member
|
You should be able to release this yourself with the release script that I
gave you for fake.
Am 13.05.2017 5:55 nachm. schrieb "Matthias Dittrich" <
notifications@github.com>:
… start fixing #2317 <#2317>
because #2333 <#2333> shows
that its relevant.
------------------------------
You can view, comment on, or merge this pull request online at:
#2336
Commit Summary
- start fixing #2317 because #2333 shows that its relevant.
File Changes
- *M* src/Paket.Core/Dependencies/PackageResolver.fs
<https://github.com/fsprojects/Paket/pull/2336/files#diff-0> (1)
- *M* src/Paket.Core/PaketConfigFiles/ProjectFile.fs
<https://github.com/fsprojects/Paket/pull/2336/files#diff-1> (4)
- *M* src/Paket.Core/Versioning/FrameworkHandling.fs
<https://github.com/fsprojects/Paket/pull/2336/files#diff-2> (91)
- *M* src/Paket.Core/Versioning/Requirements.fs
<https://github.com/fsprojects/Paket/pull/2336/files#diff-3> (64)
- *M* tests/Paket.Tests/InstallModel/Xml/System.Security.Cryptography.
Algorithms.fs
<https://github.com/fsprojects/Paket/pull/2336/files#diff-4> (3)
- *M* tests/Paket.Tests/Versioning/FrameworkCompatibilitySpecs.fs
<https://github.com/fsprojects/Paket/pull/2336/files#diff-5> (8)
Patch Links:
- https://github.com/fsprojects/Paket/pull/2336.patch
- https://github.com/fsprojects/Paket/pull/2336.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#2336>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AADgNOv409IYpY6QOkZ4vg7MijqXSEJuks5r5dJ9gaJpZM4NaHEa>
.
|
Member
Author
|
I don't think I can finish this in the next days, it will be quite invasive in the code base (and remove so many hacks that it might hurt). These changes just show the direction it's going.... For now, I just demonstrate how the low-level code is currently broken (and quite a lot of code sits on top of this) |
…eed to detect the group restrictions in a future compatible way.
…fier easier and only generated 'simple' formulas).
…ed to solve it for all version). Remove magic strings (not finished jet)
Member
Author
|
I think this is ready for review. Note that integration-tests probably need to be adapted, but I need some days break from this. If one of you wants to finish this let me know (like I said I think its just fixing the tests). Unittest-suite is green already. See my edited first post for more info. |
Member
|
files changed: 80 +2,601 −1,895 |
…nts. Push Async down into the resolver to make the resolver aware that these are costly.
… combination with resolverstrategy.
Parallel requests
Member
Author
|
I can try to merge and release tomorrow. |
This was referenced May 26, 2017
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
start fixing #2317 because #2333 shows that its relevant.
Changes:
V4_Client-> if complains come up we need to find a general solution as-clientand-fullexists for all framework versionsTODO:
Example:
The general syntax is
OP (operand1) (operand2) ...for||,NOTand&&andOP tfmfor==,>=and<.operandNitself can be a operator again, for example|| (&& (>= net3) (< net4)) (== sl4)Future Work:
I'm not doing that as part of this PR
-> I'd suggest rewriting that "penalty" part from scratch