These are chat archives for systemjs/systemjs
warn Timed out on lookup for github:systemjs/systemjs, retrying(from
jspm dl-loader, in this case), is that indicative of local network problems, github network problems, bad setup on my end, or what?
jspm dl-loaderis giving me:
Looking up loader files..., (long pause), the "timed out on lookup, retrying" message, then actually downloads systemjs, says traceur is up to date, then
Loader files downloaded successfully, then (even longer pause - perhaps stuck forever)
~/.jspm/config; I had rate limiting problems until I gave jspm credentials for github)
jspm dl-loaderhas any additional work to do after it prints "Loader files downloaded successfully". So it's done, but nodejs is just not exiting because it's still got callbacks registered in the event loop, possibly due to whatever network request initially failed and caused the earlier retry?
> jspm dl-loader Looking up loader files... warn Timed out on lookup for github:systemjs/systemjs, retrying (1). system.js system.src.js system.js.map system-csp-production.js system-csp-production.src.js system-csp-production.js.map system-polyfills.js system-polyfills.src.js system-polyfills.js.map Using loader versions: firstname.lastname@example.org Looking up github:jmcriffey/bower-traceur-runtime Looking up github:jmcriffey/bower-traceur Updating registry cache... ok Up to date - traceur as github:email@example.com (0.0.90) ok Up to date - traceur-runtime as github:firstname.lastname@example.org (0.0.90) ok Loader files downloaded successfully ^Cfish: Job 6, “jspm dl-loader” terminated by signal SIGINT (Quit request from job control (^C))
Uncaught Module null not present.Stepping through and inspecting the process I can see that there's a null in the
depslist for that module.