New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
node/npm needs SSE #90
Comments
Node is on the list. https://github.com/tbodt/ish/projects/7 |
If someone (me) wanted to push this forward. Is there a recommended place to start debugging what’s needed here? |
You can try to run the program with strace logging enabled (on by default in Xcode, |
Spent some time looking into this... it’s just a little too much outside my current ability I’m sad to say 😞 |
Wish I could help anyhow; however, my expertise is limited to software design (iXD, UI, UX, PM, ...) Sent with GitHawk |
No longer a bad system call:
|
what's the next for this? |
SSE2 instructions. If you want to work on it, feel free. |
is it a priority? it would be amazing to be able to run node so I can build my project and run it |
Any update on this? |
no |
Lurker here. To all of the folks replying with "Any update? What's next? What's the priority?", please don't. It's disrespectful to the community and the owner of this project to hammer issues with rhetorical questions. This is an open source project and the issue is clearly up for grabs (see "No one assigned" on the assignees space). If you're interested in seeing node support added, subscribe to the issue and either (a) do it yourself or (b) wait for someone else to do it. |
A. No one means any disrespect, if anything we cared enough to search for the repo and look for bugs... Please see it as a plea to push it up the priority ladder instead of a disrespectful comment. |
What's the poll I made on the main page? |
Got it mixed with another page sorry... |
I'm sorry if i was disrespectful, it wasn't my intention. |
to get node to work, don't we need to implement SSE2 which is pretty big? |
Yeah |
Would it make sense to abuse JavaScriptCore somehow (not that I know how) to add node support for those who wants it? I see how this can be problematic for those who doesn't care about nodes at all in iOS (such as myself) |
No, JavaScriptCore isn't a good substitute for Node. They're completely different programs, with different supported features. |
btw Rescript (free on Apple's App Store) has a full and working environment in NodeJS |
That's pretty cool, I haven't seen it before. I bet it's really slow though. |
i tried it one time on my iPad (6th) it was pretty good, don't know if it's what he wants |
Their sample project is super fast! |
This comment has been minimized.
This comment has been minimized.
Sorry didn't see you were a sponsor. But not in this case, my sponsor page is just a way for you to express your appreciation. |
Could SpiderNode be a workaround to this issue? SpiderNode is basically Node.js decoupled from V8 to SpiderMonkey. Edit: Just realized that SpiderNode is dead, and also compiling from source is not easy on iSH. |
mfence, ucomisd, comisd, movmskpd, andpd, punpckldq, psubq, comiss, andps, andnps, maxsd, cmpsd. Enough for a node repl. #90
That's for the same reason as #472 AFAICT |
Fixes ctrl-c sometimes sending Node's signal handler into an infinite loop. #90
Node seems to use these archaic phrasings of CLOEXEC. This fixes the Node inspector immediately closing any connections it gets. #90
This was causing the random node segfaults. Node does manual ASLR, so it would randomly pick an address for a memory mapping near the brk region, then later something would raise the brk and clobber that mapping, replacing it with zeroes. Shortly afterward something would crash on a null pointer. Took a lot of digging around in rr to find this. The crash is never directly connected to the brk call, of course. I set a watchpoint on the pointer that got clobbered and saw it had been zero since the page was mapped, but it took setting a watchpoint on the pointer to that pointer to find that when it was mapped before that and was valid at that point. At this point I'm ready to say node is fixed! #90
I think this is pretty much done now. |
Do you get the bounty? |
I think so |
what are you going to do with your newfound wealth |
@tbodt if so, I missed there was a bounty. Happy to contribute to the windfall from this |
@mattapperson You may do so at https://www.bountysource.com/issues/66159647-node-npm-needs-sse (except maybe not now since the issue is closed, I have no idea how bountysource works) |
Yea it's closed now, won't let me add to the bounty. Before you claim the next one let me know? ill just back that one |
mfence, ucomisd, comisd, movmskpd, andpd, punpckldq, psubq, comiss, andps, andnps, maxsd, cmpsd. Enough for a node repl. ish-app#90
Fixes ish-app#472 and node hanging on exit (ish-app#90)
Fixes ctrl-c sometimes sending Node's signal handler into an infinite loop. ish-app#90
Node seems to use these archaic phrasings of CLOEXEC. This fixes the Node inspector immediately closing any connections it gets. ish-app#90
Fixes 3 / 2 returning 0 in node ish-app#90
This was causing the random node segfaults. Node does manual ASLR, so it would randomly pick an address for a memory mapping near the brk region, then later something would raise the brk and clobber that mapping, replacing it with zeroes. Shortly afterward something would crash on a null pointer. Took a lot of digging around in rr to find this. The crash is never directly connected to the brk call, of course. I set a watchpoint on the pointer that got clobbered and saw it had been zero since the page was mapped, but it took setting a watchpoint on the pointer to that pointer to find that when it was mapped before that and was valid at that point. At this point I'm ready to say node is fixed! ish-app#90
Running npm or node returns 'Bad system call'
The text was updated successfully, but these errors were encountered: