all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Danny Milosavljevic" <dannym@scratchpost.org>
To: 72601@debbugs.gnu.org
Subject: [bug#72601] cuirass: Color the failures that are because of a dependency light red (differently from red)
Date: Tue, 13 Aug 2024 10:18:36 +0200 (CEST)	[thread overview]
Message-ID: <20240813081836.7C08A1120E5C@dd30410.kasserver.com> (raw)

[-- Attachment #1: Type: text/html, Size: 643 bytes --]

[-- Attachment #2: 0001-js-Color-failures-where-a-dependency-has-failed-alre.patch --]
[-- Type: text/x-diff, Size: 1081 bytes --]

From 2e1ddf5bc553ee2218489fd9ef2467bd1e5cf7c0 Mon Sep 17 00:00:00 2001
Message-ID: <2e1ddf5bc553ee2218489fd9ef2467bd1e5cf7c0.1723458264.git.dannym@scratchpost.org>
From: Danny Milosavljevic <dannym@scratchpost.org>
Date: Mon, 12 Aug 2024 12:16:12 +0200
Subject: [PATCH] js: Color failures where a dependency has failed already
 light red.

* src/static/js/cuirass.js (color): Modify.
---
 src/static/js/cuirass.js | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/src/static/js/cuirass.js b/src/static/js/cuirass.js
index 42f28f1..b09fab2 100644
--- a/src/static/js/cuirass.js
+++ b/src/static/js/cuirass.js
@@ -150,7 +150,9 @@ ready(() => {
                 case 0:
                     return '#9f9';	/* high contrast with others */
                 case 1:
-                case 2:
+                    return 'red';
+                case 2: // failed-dependency
+                    return 'lightcoral';
                 case 3:
                 case 4:
                     return 'red';

base-commit: 19c09d53395bf50810fce679e07187304b9f9a8c
-- 
2.45.2


             reply	other threads:[~2024-08-13  8:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-13  8:18 Danny Milosavljevic [this message]
2024-08-20 13:13 ` bug#72601: cuirass: Color the failures that are because of a dependency light red (differently from red) Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240813081836.7C08A1120E5C@dd30410.kasserver.com \
    --to=dannym@scratchpost.org \
    --cc=72601@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.