hydra/src/root/eval-error.tt

[% PROCESS common.tt %]
<!DOCTYPE html>

<html lang="en">

  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <meta http-equiv="X-UA-Compatible" content="IE=Edge" />
    [% INCLUDE style.tt %]
  </head>

  <body>

    <div class="tab-content tab-pane">
        <div id="tabs-errors" class="">
          [% IF eval %]
              <p>Errors occurred at [% INCLUDE renderDateTime timestamp=(eval.evaluationerror.errortime || eval.timestamp) %].</p>
              <div class="card bg-light"><div class="card-body"><pre>[% HTML.escape(eval.evaluationerror.errormsg) %]</pre></div></div>
          [% ELSIF jobset %]
              <p>Errors occurred at [% INCLUDE renderDateTime timestamp=(jobset.errortime || jobset.lastcheckedtime) %].</p>
              <div class="card bg-light"><div class="card-body"><pre>[% HTML.escape(jobset.fetcherrormsg || jobset.errormsg) %]</pre></div></div>
          [% END %]
        </div>
    </div>
  </body>
</html>
lazy-load evaluation errors Closes #1362 2024-02-16 16:50:33 +01:00			`[% PROCESS common.tt %]`
			`<!DOCTYPE html>`

			`<html lang="en">`

			`<head>`
			`<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />`
			`<meta http-equiv="X-UA-Compatible" content="IE=Edge" />`
			`[% INCLUDE style.tt %]`
			`</head>`

			`<body>`

			`<div class="tab-content tab-pane">`
			`<div id="tabs-errors" class="">`
Fix displaying eval errors in jobset eval view Quickfix for something that annoyed me once too often. Specifically, I'm talking about `/eval/1#tabs-errors`. To not fetch long errors on each request, this is only done on-demand. I.e., when the tab is opened, an iframe is requested with the errors. This iframe uses a template for both the jobset view and the jobset-eval view. It is differentiated by checking if `jobset` or `eval` is defined. However, the jobset-eval view also has a `jobset` variable in its stash which means that in both cases the `if` path was used. Since `jobset.fetcherrormsg` isn't defined in the eval case though, you always got an empty error. The band-aid fix is relatively simple: swap if and else: the `eval` variable is not defined in the stash of the jobset view, so now this is a useful condition to decide which view we're in. (cherry picked from commit https://git.lix.systems/lix-project/hydra/commit/70c3d75f739b184b36908a2c898332444482d1a1) 2025-04-03 10:33:57 +02:00			`[% IF eval %]`
lazy-load evaluation errors Closes #1362 2024-02-16 16:50:33 +01:00			`<p>Errors occurred at [% INCLUDE renderDateTime timestamp=(eval.evaluationerror.errortime \|\| eval.timestamp) %].</p>`
			`<div class="card bg-light"><div class="card-body"><pre>[% HTML.escape(eval.evaluationerror.errormsg) %]</pre></div></div>`
Fix displaying eval errors in jobset eval view Quickfix for something that annoyed me once too often. Specifically, I'm talking about `/eval/1#tabs-errors`. To not fetch long errors on each request, this is only done on-demand. I.e., when the tab is opened, an iframe is requested with the errors. This iframe uses a template for both the jobset view and the jobset-eval view. It is differentiated by checking if `jobset` or `eval` is defined. However, the jobset-eval view also has a `jobset` variable in its stash which means that in both cases the `if` path was used. Since `jobset.fetcherrormsg` isn't defined in the eval case though, you always got an empty error. The band-aid fix is relatively simple: swap if and else: the `eval` variable is not defined in the stash of the jobset view, so now this is a useful condition to decide which view we're in. (cherry picked from commit https://git.lix.systems/lix-project/hydra/commit/70c3d75f739b184b36908a2c898332444482d1a1) 2025-04-03 10:33:57 +02:00			`[% ELSIF jobset %]`
			`<p>Errors occurred at [% INCLUDE renderDateTime timestamp=(jobset.errortime \|\| jobset.lastcheckedtime) %].</p>`
			`<div class="card bg-light"><div class="card-body"><pre>[% HTML.escape(jobset.fetcherrormsg \|\| jobset.errormsg) %]</pre></div></div>`
lazy-load evaluation errors Closes #1362 2024-02-16 16:50:33 +01:00			`[% END %]`
			`</div>`
			`</div>`
			`</body>`
			`</html>`