{% extends "cacsremoteservice/views/layouts/project-view.html" %}


{% block secondary-nav %}
{% include "cacsremoteservice/views/projects/project-header.html" with project=item tabs=tabs %}
{% endblock %}

{% block main %}
<div id="page-body">
  <div class="projects-analysis-errors-view">   
    {% if system-warnings|not-empty %}
    <div class="text-content">
      <h1>Analysis Failed</h2>
      <p class="lead text-muted">
        {% comment %}Deliberately does not say the analysis produced nothing: some of the failures
        classified below leave the results usable, and their own text says so. Whether anything
        survived is the interpretation's business, not this heading's.{% endcomment %}
        The last analysis did not finish successfully. CodeScene's interpretation of
        the failure is below -- <strong><a target="_blank" href="{{view-context}}/docs/getting-started/troubleshooting-diagnostics-errors-and-logs.html#where-can-i-find-the-logs">inspect the logs</a></strong>
        for more details.
      </p>
    </div>

    {% for warning in system-warnings %}
    <div class="text-content">
      {% comment %}Don't show the category to the user because it's not relevant to them? {% endcomment %}
      <!-- <p><span class="label label-default">{{warning.category}}</span></p> -->
      <h2 class="text-danger"><i class="fa fa-warning text-danger"></i> {{warning.summary}}</h3>

      {% comment %}When the failure was recorded, not when this page was rendered -- the time is
      persisted with the warning. Guarded because it is absent for warnings stored before CodeScene
      began keeping it: an empty `datetime` would have the script below print "Invalid Date". The
      literal "UTC" is what a reader without JavaScript sees, and is accurate -- the instant
      serializes with its `Z` -- while `date-time-formatting-script.html`, included at the end of
      this page, replaces it with the reader's own time zone.{% endcomment %}
      {% if warning.timestamp %}
      <p class="text-muted">
        <i class="fa fa-clock-o"></i>
        <time data-time-type="datetime" datetime="{{warning.timestamp}}">{{warning.timestamp}} UTC</time>
      </p>
      {% endif %}

      <h3>Error message</h4>
      {% comment %} Always shown, never folded away: it is the one part of this page that is
      certainly accurate, and it is what our support will ask for. Note this is the classified
      message rather than the completely raw one -- secrets are masked and git's progress
      chatter is stripped out.
      {% endcomment %}
      {% comment %}The one field on this page that CodeScene did not write -- it carries
      repository paths, branch names and whatever the Git host chose to send back. Never mark
      it `safe`.{% endcomment %}
      <p class="alert alert-danger">
        {{warning.message}}
      </p>
      <!-- Alternatively, we could show it as preformatted text -->
      <!-- <pre class="pre-wrap">{{warning.message}}</pre> -->

      {% comment %}`description` and every `remedy` step arrive as HTML fragments, already
      escaped and with their documentation links turned into anchors by
      `views.rendering.error-text` -- which is what makes `safe` sound here. Do not put markup
      in the rule table itself: the sentences are full of placeholders like `<host>` that a
      browser would swallow as unknown elements.{% endcomment %}
      <h3>What it means</h4>
      <p class="alert alert-warning">{{warning.description|safe}}</p>

      <h3>Suggested fix</h4>
      {% comment %}A remedy is an ordered vector of steps. One step is a sentence, not a list of
      one, so it renders as a paragraph; several render as a list, which is what makes the long
      remedies scannable rather than a wall of prose. Bullets rather than numbers: the steps are
      ordered most-likely-cause first, but they are alternatives to try, not a procedure where
      step 4 depends on step 3 -- numbering them would promise a sequence that isn't there.
      {% endcomment %}
      {% if warning.remedy|length-is:1 %}
      <p class="alert alert-success">{{warning.remedy|first|safe}}</p>
      {% else %}
      <ul class="alert alert-success remedy-steps">
        {% for step in warning.remedy %}
        <li>{{step|safe}}</li>
        {% endfor %}
      </ul>
      {% endif %}
    </div>
    {% endfor %}
    {% else %}
    {% if errors.details|empty? %}
    <div class="text-content">
      <h1>No Analysis Errors</h2>
      <p class="lead text-muted">
        Your latest analysis was successful -- all good!
      </p>
    </div>
    {% else %}
    <div class="text-content">
      <h1>Analysis Failed</h2>
      <p class="lead text-muted">
        The following table specifies the warnings and errors during the last analysis.
        Please download the diagnostics file below and attach it when contacting our support.
      </p>
    </div>

    <div class="col-xs-6 text-right">

      <a class="default-button"
         href="{{ view-context }}/projects/{{ item.id }}/errors/error-details.json" download >
        <i class="fa fa-download"></i>
        Download detailed diagnostics
      </a>
    </div>

    <table class="table table-striped project-analysis-errors">
      <thead>
      <tr>
        <th class="column-error">Category</th>
        <th class="column-error">Description</th>
        <th class="column-error">Any known remedy?</th>
      </tr>
      </thead>
      <tbody>
      {% for d in errors.details %}
      <tr role="row">
        <td class="column-error">{{d.category}}</td>
        <td class="column-error">{{d.description}}</td>
        <td class="column-error">{{d.remedy}}</td>
      </tr>
      {% endfor %}
      </tbody>
    </table>
    {% endif %}
    {% endif %}
  </div>
</div>

{% comment %} Present <time> elements in browser's locale and TZ. {% endcomment %}
{% include "cacsremoteservice/views/partials/date-time-formatting-script.html" %}

{% endblock %}