view build/messages/templates/error.html @ 215:a47580a0955b

bake: Better error handling for the processing pipeline. Pipeline jobs now keep track of whether they've seen any errors. This is aggregated into an overall "success" flag for the processing record. Also, jobs keep going as long as there's no critical (i.e. internal) failure happening. Errors raised by processors are also better tracked: the actual processor that failed, along with the input file, are tracks in the processing record. The `bake` command returns a failure exit code if processing saw any error.
author Ludovic Chabant <ludovic@chabant.com>
date Sat, 31 Jan 2015 17:08:02 -0800
parents 67a1c082d89d
children a951cd4ef361
line wrap: on
line source

{% extends "default.html" %}

{% block content %}
{{content|safe}}

{% raw %}
{% if details %}
<div class="error-details">
    {{ details|safe }}
</div>
{% endif %}
{% endraw %}
{% endblock %}

{% block footer %}
{% pcformat 'textile' %}
p(note). You're seeing this because something wrong happend. To see detailed errors with callstacks, run chef with the @--debug@ parameter, append @?!debug@ to the URL, or initialize the @PieCrust@ object with @{'debug': true}@. On the other hand, to see you custom error pages, set the @site/display_errors@ setting  to @false@.
{% endpcformat %}
{% endblock %}