-
-
Notifications
You must be signed in to change notification settings - Fork 71
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
Fix Proposal for Issue 199 #200
Conversation
Codecov ReportAttention: Patch coverage is
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## develop #200 +/- ##
===========================================
- Coverage 88.63% 86.92% -1.71%
===========================================
Files 56 56
Lines 1830 1851 +21
Branches 252 252
===========================================
- Hits 1622 1609 -13
- Misses 150 184 +34
Partials 58 58 ☔ View full report in Codecov by Sentry. |
Pull Request Test Coverage Report for Build 9571608010Details
💛 - Coveralls |
The code is exactly what I was planning to do. For tests, I wanted to suggest this but it's failing even with the fix. Not sure why. [Fact]
public void ListValuesDoubleNullable()
{
ListValuesInternal("Double", faker => faker.Random.Double().OrNull(faker));
} |
Thanks for pointing me towards those tests. I took a quick look but it isn't apparent to me either :/ I think it may be memory related? At least on my machine the test either fails with:
or
If I change the |
I have noticed that the test runners report a wrong message when Access Violation or some other low-level error causes the failure. You'll actually need to debug the test to see what error is thrown and where. I'm also not sure why changing the row number helps. Probably it's generating some edge case data when the number of rows is higher. |
Agree... not a change you want to leave/keep. I just added it to illustrate. I need to take a break for a while. I may poke at it a bit more later to try and figure out what is going wrong. |
Pull Request Test Coverage Report for Build 9572221321Details
💛 - Coveralls |
Found the issue! |
Fixes #199
Maybe a more elegant way?
Not sure the test I added fits your standards, but gives some idea of what is going on.