Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14231
Let's close this in favor of https://github.com/apache/spark/pull/14508
---
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
Github user zasdfgbnm commented on the issue:
https://github.com/apache/spark/pull/14231
Yes this patch looks clearer
---
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
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/14231
I think the change is a little confusing and doesn't really explain what's
going on. I ran some tests ("ulimit -v" is your friend), and this patch covers
what's wrong here.
```
diff
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14231
Can one of the admins verify this patch?
---
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
