Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2002
Regrading to **max call stack size** what @DmytroShkvyra mentioned in above
comment (for other people)
- https://github.com/npm/npm/issues/9953
- https://github.com/npm/npm/issues/10776#issuecomment-208791872
> Symlinks are only supported in POSIX filesystem i.e. ext3 or ext4, not on
Windows filesytems i.e. NTFS, FAT. This is a serious bug while using docker.
Just switch to ext4 filesystem and everything will run as expected. So I think
that is why on windows it recursively tries to suppress the creation of
symlinks using the flag, whose result is unidentified by the (windows)
filesystem, results in stackoverflow (Maximum call stack size exceeded).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
