Maximum call stack size exceeded in columnify
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 606
- Forks
- 157
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 3
Description
- Node Version: 6.12.3
- CitGM Version: 3.1.1
- Platform: x64 Linux
Columnify issue raised: https://github.com/timoxley/columnify/issues/52
When you run citgm -J -v verbose it blows the stack. Looks like it failed before in https://github.com/nodejs/citgm/issues/44, not sure if the same cause.
error: error: | The canary is dead:
/dev/shm/usenode.jenkins0/node-v6.12.3-linux-x64/lib/node_modules/citgm/node_modules/columnify/utils.js:13
return Array.apply(null, {length: len + 1}).join(str).slice(0, len)
^
RangeError: Maximum call stack size exceeded
at repeatString (/dev/shm/usenode.jenkins0/node-v6.12.3-linux-x64/lib/node_modules/citgm/node_modules/columnify/utils.js:13:16)
at padRight (/dev/shm/usenode.jenkins0/node-v6.12.3-linux-x64/lib/node_modules/citgm/node_modules/columnify/utils.js:31:16)
at /dev/shm/usenode.jenkins0/node-v6.12.3-linux-x64/lib/node_modules/citgm/node_modules/columnify/columnify.js:229:227
at Array.forEach (native)
at _loop (/dev/shm/usenode.jenkins0/node-v6.12.3-linux-x64/lib/node_modules/citgm/node_modules/columnify/columnify.js:226:19)
at /dev/shm/usenode.jenkins0/node-v6.12.3-linux-x64/lib/node_modules/citgm/node_modules/columnify/columnify.js:234:7
at Array.map (native)
at createRows (/dev/shm/usenode.jenkins0/node-v6.12.3-linux-x64/lib/node_modules/citgm/node_modules/columnify/columnify.js:216:16)
at module.exports (/dev/shm/usenode.jenkins0/node-v6.12.3-linux-x64/lib/node_modules/citgm/node_modules/columnify/columnify.js:195:14)
at output (/dev/shm/usenode.jenkins0/node-v6.12.3-linux-x64/lib/node_modules/citgm/lib/out.js:19:15)
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 by reproducing citgm -J -v verbose on the reported Node 6.12.3 environment and read lib/out.js at the output call. Follow the stack into columnify/utils.js and columnify/columnify.js, then verify that verbose JSON output completes without the reported maximum call stack error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100