ClusterCockpit/cc-backend
1
0
Fork 0
mirror of https://github.com/ClusterCockpit/cc-backend synced 2026-06-26 12:20:36 +02:00
Code Issues Packages Releases Activity

Checkpoint: 27516ce259fd

Browse Source 
Entire-Session: 73cc565e-9a24-445c-bc6b-6bb813087897
Entire-Strategy: manual-commit
Entire-Agent: Claude Code
Ephemeral-branch: entire/d89f526-e3b0c4
This commit is contained in:
Jan Eitzinger
2026-06-18 10:29:16 +02:00
parent 9bb2652b3c
commit d58aa98853
5 changed files with 451 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
27/516ce259fd/0/prompt.txt
+23
View File
@@ -0,0 +1,23 @@
Analyse what resampling options are available for metric data and how they can be configured
---
With the current branch the frontend does not show any jobs in the job list. There is a comsole error: Uncaught TypeError: t.resampleConfig.resolutions is not iterable (cannot read property undefined)
at jobs.js:65:121
at Wn (jobs.js:1:26455)
at gt (jobs.js:1:16991)
at bt (jobs.js:1:17041)
at Un (jobs.js:1:28557)
at jobs.js:65:278
at Wn (jobs.js:1:26455)
at gt (jobs.js:1:16991)
at bt (jobs.js:1:17041)
at Un (jobs.js:1:28557). Fix the problem.
---
I do not see a difference in the frontend for long jobs with spiky metric data. It seems the average resampling has no effect. I tried to change resampling by config file and from the web frontend. Can you check why there is no effect. I tried for job db id: 409
---
Commit the changes in 3 commits: One with the toplevel config warning, one with the frontend fixes, and one about the dependency updates