I submitted two solutions:
The former is not showing the number of matching solutions, and the latter is stuck in “Processing”.
I submitted two solutions:
The former is not showing the number of matching solutions, and the latter is stuck in “Processing”.
It’s still broken. Is anyone looking into this?
I hadn’t submit Pythagorean Triplet yet since the tests still say “Processing”. I went ahead and marked it as complete and published it. The solution runs in under a second on my PC, including the test that was marked as skipped, so I don’t think my solution is too slow.
As for Grains, it just shows the number of lines but not how many times that solution has been submitted, nor do I see it anywhere in the list of Community Solutions.
> jest ./*
PASS ./pythagorean-triplet.spec.js
Triplet
✓ triplets whose sum is 12 (6 ms)
✓ triplets whose sum is 108
✓ triplets whose sum is 1000 (1 ms)
✓ no matching triplets for 1001
✓ returns all matching triplets (1 ms)
✓ several matching triplets
✓ returns triplets with no factor smaller than minimum factor (1 ms)
✓ returns triplets with no factor larger than maximum factor
✓ returns triplets with factors in range (1 ms)
✓ triplets for large number
Test Suites: 1 passed, 1 total
Tests: 10 passed, 10 total
Snapshots: 0 total
Time: 0.946 s
Ran all test suites matching /.\/HELP.md|.\/LICENSE|.\/README.md|.\/babel.config.js|.\/node_modules|.\/package.json|.\/pnpm-lock.yaml|.\/pythagorean-triplet.js|.\/pythagorean-triplet.spec.js/i.
Thank you for submitting the solution. Now @iHiD can check the state of why it keeps processing.
The solution itself looks fast enough and matches the structure of my proof solution (which is also about a second to run). Do note that it running fast locally doesn’t necessarily mean it runs fast on the online test runner, but that’s besides the point.
As for grains, I don’t know why it’s not grouping it, but it could be that you are the first with this exact solution. It could also be that in that case we don’t show the block at all.
I will test this for you by submitting your exact solution and then see if it appears on mine and yours.
It did not immediately work and I also saw a long-running process during my submission. The next step is to inspect GitHub - exercism/javascript-representer in order to see if there is an issue representing this solution.
I will do so, this may take some time as I am a volunteer, but once I have some results I will let you know. My current guess is that my representer doesn’t yet support BigInt
, and so it should be updated.
My current guess is that my representer doesn’t yet support
BigInt
, and so it should be updated.
I’m wondering if it has anything to do with the fact that I’m using the n
notation to represent BigInt
constants. When I have some time, maybe I’ll submit a new solution that doesn’t use that notation.
I updated grains to not use n
, and now I’m seeing that my solution has been uploaded 2 times. That issue seems to be fixed. Now, all that needs to happen is to figure out why Pythagorean Triplets is still in the processing state.
Good to know. Then it is as i expected. I’ll work on updating the représenter so that both solutions work.
Any word on this? Pythagorean Triplets is still in “Processing”