RangeError with correct solution on Waypoint: Passing Values to Functions with Arguments

[BKinahan]

Challenge Waypoint: Passing Values to Functions with Arguments has an issue.
User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.106 Safari/537.36.

Running tests outputs RangeError: Maximum call stack size exceeded and no tests pass.

My code:

// Example
function ourFunction(a, b) {
  console.log(a - b);
}
ourFunction(10, 5); // Outputs 5

// Only change code below this line.

function myFunction(c, d){
  console.log(c + d);
}
myFunction(2, 3);

[ltegman]

Huh, I'm unable to repro this using the exact same code. Anyone else seeing this error?

[BKinahan]

Just noticed it's mentioned in #5499 so it's not just me.. However I just reopened the waypoint page now and the tests were passed before running the tests, and running the tests was successful. Not sure what's going on there.

[nicolefffe]

I am having this problem too.

// Example
function ourFunction(a, b) {
  console.log(a - b);
}
ourFunction(10, 5); // Outputs 5

// Only change code below this line.
function myFunction(arg1, arg2) {
  console.log(arg1 + arg2);
}

myFunction(5, 4);

No test cases pass and I get the error: RangeError: Maximum call stack size exceeded

[nicolefffe]

I also re-entered the waypoint from the map and the same code passed the tests, so it is a mystery :)

[lucabarbetti]

Test successfully passed after reloading the page.

[masondz]

Reloading the page also worked for me.

[harwluk]

having same issue. reloaded the page worked for me, too.

[ngorton91]

Getting this same error

[danjm75]

same problem. Is there an actual fix, or did I miss it?

[abhisekp]

Works for me now. Was getting range stack error previously.

[danjm75]

man I wish I would have refreshed like 15 minutes ago. that was a waste of time. oh well, I'll just subtract that time from my retirement!

[atan77]

I got the same error initially and then with a reload from the map it validated ok with no change to solution

[SaintPeter]

@BerkeleyTrue I have periodically been able to reproduce this, but refreshing the browser makes it go away. Any ideas what might be going on here? I'm presuming it's related to the test architecture.

[BerkeleyTrue]

Does it only happen on page initial page load (with default code) then on refresh with completed code it is fixed?

[SaintPeter]

It appears to happen on initial page load, then after refreshing it is fixed . . . but if you load the page, paste in the solution and try to run it, it fails.

[AkiraLaine]

Same problem here. With @SaintPeter's solution, it passed.

[KrisVos130]

I can reproduce this by being in an anonymous tab on Chrome, going to the challenge from the map and then just clicking submit. After that, when you clear your Local Storage and do the same thing, then the error happens again. You don't need to modify any code for the error to happen either.

[DDaems]

You can just do a reset, change something in the challenge field. adding a random space or whatever. And hit refresh ;-). Still i think the reset button should reset the localstorage item too. Wich it atm doesn't seem to do.

Anyway i created a PR to fix this issue and will create a issue for clearing localstorage on reset

[teal18aa9f]

Refresh the page.It worked for me!

[bssatya]

Same here. Page refresh worked...

[onetallorder]

Reloading the page resolved this issue for me.

[ArielLeslie]

I ran into this a couple days ago as well. Sometimes I had to refresh several times before it would work.

[denmch]

I had this happen with several of the new JS Waypoints over the last few days. In each case a hard refresh cleared it up.

[SimpliiD]

I just reproduced this error after initially loading using the 'learn' button, but refreshing fixed it. Also running in Chrome.

[ViktorDimitrievski]

reloading page work for me.

[shahh]

Refreshing the page worked for me too.

[estraneoDev]

Page refresh solve the problem