-
Notifications
You must be signed in to change notification settings - Fork 198
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
Dict memoization sorting before normalizing keys is unsafe #3157
Open
MundiaNderi
wants to merge
6
commits into
Parsl:master
Choose a base branch
from
MundiaNderi:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
11ff829
Fixing Dict memoization sorting before normalizing keys is unsafe'
MundiaNderi 6fd93a9
Remove accidentally committed runinfo files
MundiaNderi 37e10c9
Remove parsl/dataflow/dflow.py from PR
MundiaNderi b22efe5
Fixing files
MundiaNderi ed743e4
Joining dflow lines
MundiaNderi 92b99ca
Fixing memoization test file
MundiaNderi File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,29 @@ | ||
import pytest | ||
import enum | ||
|
||
# Define an enum - collection of related consonants | ||
|
||
|
||
class Foo(enum.Enum): | ||
x = enum.auto() | ||
y = enum.auto() | ||
|
||
|
||
# Test function demonstrating the issue with unstable sorting when keys | ||
# are hashable but not comparable. | ||
|
||
|
||
def test_unstable_sorting(): | ||
# Functions | ||
def foo(): | ||
return 1 | ||
|
||
def bar(): | ||
return 2 | ||
|
||
# Dictionary with problematic keys | ||
d = {foo: 1, bar: 2} | ||
|
||
# Sort the dictionary, it should raise a TypeError | ||
with pytest.raises(TypeError): | ||
sorted(d) |
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, I think this is right thing to be doing - but I don't think your test case that you added really tests that something was broken before, and is now fixed by this change.
I will try to add some comments on the test case if I can figure out a stronger test case.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you , I've also realised that and was trying to think though it. Where I fell short was I corrected the implementation first, then created the test case later. I should have done vice versa.