Skip to content
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

Redirect ember build errors to error file #245

Merged
merged 1 commit into from
Nov 5, 2015

Conversation

seanpdoyle
Copy link
Contributor

Initial steps toward closing #240.

Pipe ember build errors from $STDERR to ember-cli-rails's build
error file.

Depends on ember-cli/ember-cli#5038

@@ -282,7 +282,11 @@ def command(watch: false)
end
end

"#{ember_path} build #{watch_flag} --environment #{environment} --output-path #{dist_path} #{log_pipe}"
"#{ember_path} build #{watch_flag} --environment #{environment} --output-path #{dist_path} #{redirect_errors} #{log_pipe}"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Line is too long. [128/80]

Initial steps toward closing [#240].

Pipe `ember build` errors from `$STDERR` to `ember-cli-rails`'s build
error file.

Depends on [ember-cli/ember-cli#5038]

[#240]: #240
[ember-cli/ember-cli#5038]: ember-cli/ember-cli#5038
@seanpdoyle seanpdoyle merged commit 3703693 into master Nov 5, 2015
seanpdoyle added a commit that referenced this pull request Nov 12, 2015
The future use cases of this project expect that the build will complete
before serving the Ember applications.

Additionally, build timeouts used to act as a workaround for when
the EmberCLI build had errors that weren't being communicated to the
Rails process. Now that [EmberCLI writes errors to STDERR][stderr],
which EmberCLI-Rails [pipes STDERR to a file][pipe] for monitoring,
EmberCLI build errors will be raised by the Rails process.

For Users who care about timeouts, [rack-timeout] serves as a great
alternative.

[stderr]: ember-cli/ember-cli#5039
[pipe]: #245
[rack-timeout]: https://github.com/heroku/rack-timeout
seanpdoyle added a commit that referenced this pull request Nov 12, 2015
The future use cases of this project expect that the build will complete
before serving the Ember applications.

Additionally, build timeouts used to act as a workaround for when
the EmberCLI build had errors that weren't being communicated to the
Rails process. Now that [EmberCLI writes errors to STDERR][stderr],
which EmberCLI-Rails [pipes STDERR to a file][pipe] for monitoring,
EmberCLI build errors will be raised by the Rails process.

For Users who care about timeouts, [rack-timeout] serves as a great
alternative.

[stderr]: ember-cli/ember-cli#5039
[pipe]: #245
[rack-timeout]: https://github.com/heroku/rack-timeout
seanpdoyle added a commit that referenced this pull request Nov 14, 2015
Closes [#262].

Managing user dependencies within app code is more trouble than it's
worth. Being explicit about our EmberCLI support in our `README.md` and
keeping the addon version in lock-step with the gem will be a better
solution long term.

Since EmberCLI now [writes to STDERR][stderr], which EmberCLI-Rails
[pipes to a file and monitors][error-file], front-end failures will
communicated to users through normal Error-raising means.

[#262]: #262
[stderr]: ember-cli/ember-cli#5039
[error-file]: #245
seanpdoyle added a commit that referenced this pull request Nov 14, 2015
Closes [#262].

Managing user dependencies within app code is more trouble than it's
worth. Being explicit about our EmberCLI support in our `README.md` and
keeping the addon version in lock-step with the gem will be a better
solution long term.

Since EmberCLI now [writes to STDERR][stderr], which EmberCLI-Rails
[pipes to a file and monitors][error-file], front-end failures will
communicated to users through normal Error-raising means.

[#262]: #262
[stderr]: ember-cli/ember-cli#5039
[error-file]: #245
seanpdoyle added a commit that referenced this pull request Nov 14, 2015
Closes [#262].

Managing user dependencies within app code is more trouble than it's
worth. Being explicit about our EmberCLI support in our `README.md` and
keeping the addon version in lock-step with the gem will be a better
solution long term.

Since EmberCLI now [writes to STDERR][stderr], which EmberCLI-Rails
[pipes to a file and monitors][error-file], front-end failures will
communicated to users through normal Error-raising means.

[#262]: #262
[stderr]: ember-cli/ember-cli#5039
[error-file]: #245
seanpdoyle added a commit that referenced this pull request Nov 14, 2015
Closes [#262].

Managing user dependencies within app code is more trouble than it's
worth. Being explicit about our EmberCLI support in our `README.md` and
keeping the addon version in lock-step with the gem will be a better
solution long term.

Since EmberCLI now [writes to STDERR][stderr], which EmberCLI-Rails
[pipes to a file and monitors][error-file], front-end failures will
communicated to users through normal Error-raising means.

[#262]: #262
[stderr]: ember-cli/ember-cli#5039
[error-file]: #245
seanpdoyle added a commit that referenced this pull request Nov 14, 2015
Closes [#262].

Managing user dependencies within app code is more trouble than it's
worth. Being explicit about our EmberCLI support in our `README.md` and
keeping the addon version in lock-step with the gem will be a better
solution long term.

Since EmberCLI now [writes to STDERR][stderr], which EmberCLI-Rails
[pipes to a file and monitors][error-file], front-end failures will
communicated to users through normal Error-raising means.

[#262]: #262
[stderr]: ember-cli/ember-cli#5039
[error-file]: #245
@seanpdoyle seanpdoyle mentioned this pull request Nov 14, 2015
@seanpdoyle seanpdoyle deleted the sd-pipe-stderr-to-error-file branch November 19, 2015 17:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants