Lucio Lelii
408bcb9309
The tree fetched a container's iterations once, when the step was first expanded, and kept that list until the root run id changed. Polling refreshed the run but never that list - and it is the only source both for which children exist and for what state each one is in. So a three-iteration run displayed "Iteration 1, RUNNING" from start to finish. A run that was working looked stuck, and then looked as though it had done one iteration and produced nothing, while the container was in fact on iteration 3 with two results already accumulated. The list now refreshes on each poll tick while the run is live, and once more on the tick that reports it finished - that tick carries the final status and with it the last child's real state. Nothing is fetched for a step nobody opened, a refresh already in flight is not duplicated, and a failed refresh leaves what is on screen alone rather than replacing valid iterations with an error. 493 frontend tests green. Both new assertions fail with the refresh disabled. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .vscode | ||
| docker | ||
| docs | ||
| public | ||
| src | ||
| .dockerignore | ||
| .editorconfig | ||
| .gitignore | ||
| .postcssrc.json | ||
| Dockerfile | ||
| README.md | ||
| angular.json | ||
| components.json | ||
| nginx.conf | ||
| package-lock.json | ||
| package.json | ||
| tsconfig.app.json | ||
| tsconfig.json | ||
| tsconfig.spec.json | ||
README.md
HumAInFlow
This project was generated using Angular CLI version 21.0.3.
Development server
To start a local development server, run:
ng serveOnce the server is running, open your browser and navigate to
http://localhost:4200/. The application will automatically
reload whenever you modify any of the source files.
Code scaffolding
Angular CLI includes powerful code scaffolding tools. To generate a new component, run:
ng generate component component-nameFor a complete list of available schematics (such as
components, directives, or
pipes), run:
ng generate --helpBuilding
To build the project run:
ng buildThis will compile your project and store the build artifacts in the
dist/ directory. By default, the production build optimizes
your application for performance and speed.
Running unit tests
To execute unit tests with the Vitest test runner, use the following command:
ng testRunning end-to-end tests
For end-to-end (e2e) testing, run:
ng e2eAngular CLI does not come with an end-to-end testing framework by default. You can choose one that suits your needs.
Additional Resources
For more information on using the Angular CLI, including detailed command references, visit the Angular CLI Overview and Command Reference page.