Skip to content

🎨 Palette: Improve telemetry status badge rendering in dashboard - #524

Merged
timerloggedout-spec merged 2 commits into
masterfrom
jules-10582546551670970524-a175f9fc
Sep 16, 2026
Merged

timerloggedout-spec merged 2 commits into
masterfrom
jules-10582546551670970524-a175f9fc

Conversation

@google-labs-jules

Copy link
Copy Markdown
Contributor

💡 What: Standardized status badge rendering and uppercase normalization in termux-multi-agent/dashboard.py.
🎯 Why: Prevents ERROR, FAILED, or WARNING events from defaulting to blue PROCESSING tags, improving visual clarity and accessibility.
♿ Accessibility: Proper color contrast and clear text feedback for screen readers and terminal users.


PR created automatically by Jules for task 10582546551670970524 started by @timerloggedout-spec

Map telemetry log level strings (ERROR, FAILED, CRITICAL, WARNING, WARN, RETRY, SUCCESS, INFO) to distinct color-coded status badges with uppercase string normalization in termux-multi-agent/dashboard.py.
This prevents error and warning telemetry events from misclassifying as active blue processing status tags.

Unit test coverage added in tests/test_telemetry_optimized.py.
@google-labs-jules

Copy link
Copy Markdown
Contributor Author

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@blocksorg

blocksorg Bot commented Sep 15, 2026

Copy link
Copy Markdown

Mention Blocks like a regular teammate with your question or request:

@blocks review this pull request
@blocks make the following changes ...
@blocks create an issue from what was mentioned in the following comment ...
@blocks explain the following code ...
@blocks are there any security or performance concerns?

Run @blocks /help for more information.

Workspace settings | Disable this message

@vercel

vercel Bot commented Sep 15, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
mcp-hub Ready Ready Preview Sep 15, 2026 7:34am UTC

@ecc-tools

ecc-tools Bot commented Sep 15, 2026

Copy link
Copy Markdown

ECC Tools / Security Evidence

Commit: ff52c1d91c7a54c4f9939287e387174efc3b3f17

Security evidence gate passed (success)

No security-sensitive scanner-evidence gap detected.

Mode: enforce

Scanned 2 changed file(s). No missing scanner-evidence signal was detected.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@ecc-tools

ecc-tools Bot commented Sep 15, 2026

Copy link
Copy Markdown

ECC Tools / PR Risk Taxonomy

Commit: ff52c1d91c7a54c4f9939287e387174efc3b3f17

PR taxonomy clear (success)

Scanned 2 changed file(s). No taxonomy bucket signals were detected.

Scanned 2 changed file(s).

No PR taxonomy bucket signals were detected.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@vercel

vercel Bot commented Sep 15, 2026

Copy link
Copy Markdown

Deployment failed for project termux-monorepo with the following error:

Resource is limited - try again in 24 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/timerloggedout-5184s-projects?upgradeToPro=build-rate-limit

@ecc-tools

ecc-tools Bot commented Sep 15, 2026

Copy link
Copy Markdown

ECC Tools / Reference Set Readiness

Commit: ff52c1d91c7a54c4f9939287e387174efc3b3f17

Reference set readiness gaps detected (neutral)

Reference evidence present for 0/7 areas (0%) across 2 changed file(s).

This check is based on files changed in this PR. Repository-level readiness is still reported by /ecc-tools analyze comments and generated manifests.

Area Status Evidence / Next Step
Deep analyzer corpus Missing Add analyzer fixture, golden, benchmark, or reference-set files that can catch analyzer regressions.
RAG/evaluator comparison Missing Add retrieval or evaluator reference-set comparison fixtures with expected ranking behavior.
PR salvage/review corpus Missing Add stale-PR, review-thread, reopen-flow, or salvage reference cases for queue cleanup automation.
Discussion triage corpus Missing Add public discussion triage fixtures, golden cases, or reference sets for informational, answered, and no-response classifications.
Harness compatibility Missing Add cross-harness, adapter-compliance, or harness-audit evidence for Claude, Codex, OpenCode, Zed, dmux, and agent surfaces.
Security evidence Missing Attach security evidence such as SBOMs, SARIF, audit reports, or AgentShield evidence packs.
CI failure-mode evidence Missing Add captured CI failure logs, dry-run fixtures, or troubleshooting docs for common workflow failure modes.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@ecc-tools

ecc-tools Bot commented Sep 15, 2026

Copy link
Copy Markdown

ECC Tools / Hosted Promotion Readiness

Commit: ff52c1d91c7a54c4f9939287e387174efc3b3f17

Hosted promotion readiness passed (success)

No hosted promotion evidence gaps detected across 2 changed file(s); 0 corpus scenarios had matching evidence.

This check compares PR file changes against the evaluator/RAG promotion corpus in src/analyzers/fixtures/evaluator-rag-corpus.ts.
Hosted output scoring inspected 0 completed cached hosted job results.

No evaluator corpus scenarios matched this PR.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@timerloggedout-spec

Copy link
Copy Markdown
Owner

ECC App activity — dual-gate merges; review skills/hooks before merge.

@github-actions

github-actions Bot commented Sep 15, 2026 •

Copy link
Copy Markdown
Contributor

PR Change Effectiveness Ledger

Measured head: bd57cc9fd0194c01a6c4b59055d0457927f49595
Measured base: 7d10d33d154eada1184c1826000eaad5fa52b23f
Merge base: 7d10d33d154eada1184c1826000eaad5fa52b23f

Signal Value
commits in PR range 2
commits with no file delta 1
commits with file delta 1
no-op commit rate 50%
gross additions across commits 32
gross deletions across commits 4
final additions vs base 32
final deletions vs base 4
final changed files 2
churn → retained final diff 100%
ahead / behind base 2 / 0

Interpretation: commit count is context, not quality. Empty commits are explicitly measured, not silently treated as productive work. Gross churn describes work performed across history; the final base→head diff describes what remains. Review/comment/check evidence must be evaluated separately and tied to this measured head SHA.

State: 🟢 EFFECTIVE_DIFF_PRESENT; ⚠️ 1 empty/no-op commit(s) observed.

Generated: 2026-09-15T07:36:18Z

@google-labs-jules

Copy link
Copy Markdown
Contributor Author

ECC App activity — dual-gate merges; review skills/hooks before merge.

Acknowledged.

Map telemetry log level strings (ERROR, FAILED, CRITICAL, WARNING, WARN, RETRY, SUCCESS, INFO) to distinct color-coded status badges with uppercase string normalization in termux-multi-agent/dashboard.py.
This prevents error and warning telemetry events from misclassifying as active blue processing status tags.

Unit test coverage added in tests/test_telemetry_optimized.py.
@vercel

vercel Bot commented Sep 15, 2026

Copy link
Copy Markdown

Deployment failed for project mcp-hub with the following error:

Resource is limited - try again in 24 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/timerloggedout-5184s-projects?upgradeToPro=build-rate-limit

@ecc-tools

ecc-tools Bot commented Sep 15, 2026

Copy link
Copy Markdown

ECC Tools / Security Evidence

Commit: bd57cc9fd0194c01a6c4b59055d0457927f49595

Security evidence gate passed (success)

No security-sensitive scanner-evidence gap detected.

Mode: enforce

Scanned 2 changed file(s). No missing scanner-evidence signal was detected.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@vercel

vercel Bot commented Sep 15, 2026

Copy link
Copy Markdown

Deployment failed for project termux-monorepo with the following error:

Resource is limited - try again in 1 day (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/timerloggedout-5184s-projects?upgradeToPro=build-rate-limit

@ecc-tools

ecc-tools Bot commented Sep 15, 2026

Copy link
Copy Markdown

ECC Tools / PR Risk Taxonomy

Commit: bd57cc9fd0194c01a6c4b59055d0457927f49595

PR taxonomy clear (success)

Scanned 2 changed file(s). No taxonomy bucket signals were detected.

Scanned 2 changed file(s).

No PR taxonomy bucket signals were detected.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@ecc-tools

ecc-tools Bot commented Sep 15, 2026

Copy link
Copy Markdown

ECC Tools / Reference Set Readiness

Commit: bd57cc9fd0194c01a6c4b59055d0457927f49595

Reference set readiness gaps detected (neutral)

Reference evidence present for 0/7 areas (0%) across 2 changed file(s).

This check is based on files changed in this PR. Repository-level readiness is still reported by /ecc-tools analyze comments and generated manifests.

Area Status Evidence / Next Step
Deep analyzer corpus Missing Add analyzer fixture, golden, benchmark, or reference-set files that can catch analyzer regressions.
RAG/evaluator comparison Missing Add retrieval or evaluator reference-set comparison fixtures with expected ranking behavior.
PR salvage/review corpus Missing Add stale-PR, review-thread, reopen-flow, or salvage reference cases for queue cleanup automation.
Discussion triage corpus Missing Add public discussion triage fixtures, golden cases, or reference sets for informational, answered, and no-response classifications.
Harness compatibility Missing Add cross-harness, adapter-compliance, or harness-audit evidence for Claude, Codex, OpenCode, Zed, dmux, and agent surfaces.
Security evidence Missing Attach security evidence such as SBOMs, SARIF, audit reports, or AgentShield evidence packs.
CI failure-mode evidence Missing Add captured CI failure logs, dry-run fixtures, or troubleshooting docs for common workflow failure modes.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@ecc-tools

ecc-tools Bot commented Sep 15, 2026

Copy link
Copy Markdown

ECC Tools / Hosted Promotion Readiness

Commit: bd57cc9fd0194c01a6c4b59055d0457927f49595

Hosted promotion readiness passed (success)

No hosted promotion evidence gaps detected across 2 changed file(s); 0 corpus scenarios had matching evidence.

This check compares PR file changes against the evaluator/RAG promotion corpus in src/analyzers/fixtures/evaluator-rag-corpus.ts.
Hosted output scoring inspected 0 completed cached hosted job results.

No evaluator corpus scenarios matched this PR.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant