Tim Caswell comments

Results 341 comments of


                                            Tim Caswell

Switch luvit to use luvit-loader instead of luvit/require package

You're right that require alone can't do lit style path resolving exactly because of the problem with the cache you found. We have to resolve the relative path to a...

Switch luvit to use luvit-loader instead of luvit/require package

> test.lua calling require('json') resolves to deps/json.lua while deps/foo/bar.lua calling require('json') resolves to deps/foo/bar/deps/json.lua). Is that sort of thing what you have in mind? Yes. Though lit doesn't support automatically...

Switch luvit to use luvit-loader instead of luvit/require package

@aiverson sounds interesting, I'm not sure I quite understand your proposal.

Implement luvit's require as a normal luv searcher/loader

See https://github.com/luvit/lit/pull/155

http.createServer():on("request", ...):listen(0) - Uncaught Error: [string "bundle:deps/http.lua"]:308: attempt to call upvalue 'onRequest' (a nil value)

> Is this a fundamental misunderstanding on my side... No, this is just a place where we havn't reached parity with the node docs. They did change significantly over the...

deep-equal is duplicated in utils

Thanks, we should use the one in utils I think.

Find and fix segfaults in luvit

Ryan added travis hooks to help next time we see it there. https://github.com/luvit/luvit/commit/f78bebe52bed75b63623c867821aebeb664ef8a6

Find and fix segfaults in luvit

Here is another one. https://travis-ci.org/virgo-agent-toolkit/rackspace-monitoring-agent/builds/73088318 But the travis hook doesn't give stacktraces :(

Find and fix segfaults in luvit

@rphillips fixed one, but I don't think it's the one I was seeing the other day. I wasn't using uv.spawn. https://github.com/luvit/luv/pull/169

Find and fix segfaults in luvit

@Stepets I fixed lit.luvit.io. It went down while I was on vacation and my auto scripts didn't detect the issue.