Got the same issue. In my case it was because I was overwriting Array.prototype.flat.
Even though it says it's using node8 and flat was introduced in v11, it still a had problem with that somehow. So avoid overwriting any build-in objects.

I've fixed the input mutation vulnerability myself, in spite of not knowing the first thiong about Ruby,

Would you please make require unavailable?

Please see the recent issue by @Blind. Can you address those concerns?

It's explained in the posts below like the one from omiceron.

!?

I second it, lol :) | Let's build a library let's go!

var converter = require('number-to-words');

Fixed.

And reverse logic confirms when I checked the attribute against the instance variable in my sample tests:

dog = GenericEntity.new(:barks=>"obnoxiously", :bites=>"mildly", :color=>"black")

Test.assert_equals(dog.color, "black")
Test.assert_equals(dog.bites, "mildly")
Test.assert_equals(dog.barks, "obnoxiously")
Test.assert_equals(dog.barks, @barks)




Test Passed: Value == "black"
Test Passed: Value == "mildly"
Test Passed: Value == "obnoxiously"
Expected: nil, instead got: "obnoxiously"

Are you 100% sure @barks is available as an instance variable of dog and not just an attribute?

Any resolution? Yeah when I write my own sample test with same params: dog = GenericEntity.new(:barks=>"obnoxiously", :bites=>"mildly", :color=>"black")

Two strings may have more than one longest common subsequence. When this occurs, return any of them.

I don't think you are accounting for this.

Please read the tests from another language and note how testing is done. It's not a simple assertEquals.

ALso, I don't see any language customisation of the Description. I'd appreciate relevant language-specific notes.

Didn't do all of it myself .. I solved JS first and saw some solutions.

But thanks. :]

The answer is the literally one comment down from yours.