ekatek
c67de0830a
merging from sqllite
2014-09-30 16:29:41 -07:00
Justin SB
f0a12fd37d
Don't run the npm downloads in parallel
...
Seems to break. We should fix this properly in future, for a better dev UX
2014-09-30 11:45:58 -07:00
Sashko Stubailo
8bd7a14993
Merge branch 'release-0.9.4' into isopack
2014-09-29 17:57:15 -07:00
Sashko Stubailo
7cd12072ea
Rename unipackage to isopack in almost all cases
2014-09-29 16:01:08 -07:00
Justin SB
e9a88b00b9
Fix some fibers vs SQLite issues
2014-09-29 07:57:51 -07:00
Justin SB
46a81c489d
Print debug timings from enterJob, even if not in message capture
2014-09-24 15:53:05 -07:00
Justin SB
db10e231a4
Support asymptotic progress bar for constraint solver
...
Until we either can estimate progress or have a spinner...
2014-09-24 15:53:04 -07:00
Justin SB
98ffa7d6d3
Add missing return to enterJob
...
I removed it accidentally in 9963a8bc
2014-09-19 17:22:59 -07:00
Justin SB
9963a8bcf3
Progress bars and output formatting
2014-09-19 16:56:25 -07:00
David Glasser
a3e1ed79ff
Print something better than [Object object]
...
If we ever load javascript (uniload load or package.js parse) outside of
a buildmessage job and there's a syntax error, FancySyntaxError gets
thrown instead of properly processed. Now, we shouldn't do that (we
should only load JS inside a buildmessage job!) but our codebase isn't
currently up to that standard, so at least ensure that there's some
level of useful syntax error (albeit with an ugly internal stack trace
attached) in this case.
2014-08-08 10:30:22 -07:00
David Glasser
7d05640ea0
Make buildmessage fiber-aware
...
Port a simplified version of Meteor.EnvironmentVariable and
Meteor.bindEnvironment to fiber-helpers.js to deal with this.
Identify uses of fiberHelpers.inFiber and switch them to either
fiberHelpers.bindEnvironment (if the callback they are wrapping is
semantically "part of" the context that creates the callback) or
fiberHelpers.inBareFiber (otherwise).
Without this, concurrency was causing the wrong buildmessage message
sets and jobs to be active when builds yielded.
2014-08-04 19:03:05 -07:00
David Glasser
43b04a12b2
add some buildmessage.assertInJob to PackageClient
2014-07-29 18:57:59 -07:00
David Glasser
46482f51fb
typo fix
2014-01-30 16:47:00 -08:00
Geoff Schmidt
1bf1c094ce
First pass on new test harness for command-line tool
2014-01-09 02:47:17 -08:00
Geoff Schmidt
b940e06006
make getSettings report problems cleanly
...
(using buildmessages rather exceptions)
2014-01-08 17:18:32 -08:00
Geoff Schmidt
95e3959165
The period goes outside the parens (like this).
...
(Except when the parenthetical is a complete sentence.)
2013-12-30 06:20:49 -08:00
David Glasser
8aa63bcb3a
Cleanups for PR 1263:
...
- Display proper caller location (requires extending useMyCaller to take a
number)
- Recover by only returning valid 'where's so we don't crash later.
2013-08-01 00:29:14 -07:00
David Glasser
62626bf33d
Set $METEOR_DEBUG_BUILD to see what jobs are run.
2013-07-30 11:15:15 -07:00
Geoff Schmidt
096a6efddd
Improve stack parsing
2013-07-15 18:23:54 -07:00
David Glasser
3205e33537
using source maps in JSImage.load now probably works
2013-07-12 10:11:31 -07:00
David Glasser
177a5684c9
checkpoint for using source maps in jsimage.load
...
syntax error parsing is broken, will fix
2013-07-12 10:11:31 -07:00
David Glasser
12a93615cf
Make buildmessage parseStack more robust to multi-line errors.
...
This makes Handlebars parse errors not crash.
2013-07-02 19:50:38 -07:00
Geoff Schmidt
0b2d536e38
Clean up error reporting in HTML template scanner
2013-05-13 11:56:51 -07:00
Geoff Schmidt
27b617ce92
correctly report error messages when exceptions occur that could be handled by buildmessage but are not
2013-05-13 11:55:12 -07:00
Geoff Schmidt
ed18c6ffb5
Comprehensive build-time error reporting system. In particular: if an error occurs, the build will try to continue to identify any other potential problems so that they can be flagged too. Syntax errors are captured and dealt with programmatically, rather than just being echoed to stderr by node. Stack traces are parsed to pull out file and line information, and a distinction is made between the 'user' and 'internal' portions of the stack. All of this is at build time only -- it has not been extended to (run-time) server or browser yet. Also, no source maps yet, though line numbers are computed correctly for units within the linker.
2013-05-13 11:52:43 -07:00
