“Cannot coerce NaN to an Int” in benchable
Open
Nobody has claimed this yet.
benchable
- Dominant language
- Raku
- Stars
- 19
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
See https://irclog.perlgeek.de/perl6/2017-06-27#i_14794509
Cannot coerce NaN to an Int in method y-ticks at /home/bisectable/.rakudobrew/moar-nom/install/share/perl6/site/sources/F589ED5005168E0E2A09F070DB83A3AB0EAA38BC (SVG::Plot) line 436
in method plot at /home/bisectable/.rakudobrew/moar-nom/install/share/perl6/site/sources/F589ED5005168E0E2A09F070DB83A3AB0EAA38BC (SVG::Plot) line 413
in method process at ./Benchable.p6 line 194
in method irc-to-me at ./Benchable.p6 line 94
in block at /home/bisectable/.rakudobrew/moar-nom/install/share/perl6/site/sources/DFC5BCCD6AED9D84DA8A1F88FF8F423073F81CA9 (IRC::Client) line 285
in method handle-event at /home/bisectable/git/whateverable/.precomp/4C2451ED63DDF52CF77EF3DEF1D47FCC8F88A283.1494783481.51462/DF/DFC5BCCD6AED9D84DA8A1F88FF8F423073F81CA9 line 1
in block at /home/bisectable/.rakudobrew/moar-nom/install/share/perl6/site/sources/DFC5BCCD6AED9D84DA8A1F88FF8F423073F81CA9 (IRC::Client) line 112
in block at /home/bisectable/.rakudobrew/moar-nom/install/share/perl6/site/sources/DFC5BCCD6AED9D84DA8A1F88FF8F423073F81CA9 (IRC::Client) line 110
in block at /home/bisectable/.rakudobrew/moar-nom/install/share/perl6/site/sources/DFC5BCCD6AED9D84DA8A1F88FF8F423073F81CA9 (IRC::Client) line 301
Contributor guide
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
Start with Benchable.p6 around lines 94 and 194, then inspect the SVG::Plot y-ticks and plot frames at lines 436 and 413. Reproduce the IRC-triggered failure from the stack trace and trace the NaN input; completion should prevent the reported coercion error and verify the affected processing path.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend, data-visualization, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100