Skip to content

Develop#172

Open
atriaybagur wants to merge 98 commits intomainfrom
develop
Open

Develop#172
atriaybagur wants to merge 98 commits intomainfrom
develop

Conversation

@atriaybagur
Copy link
Member

Description

Linked Issues

Fixes #

Checklist

  • Follows the project's coding conventions and style guide
  • Updates documentation
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published

Type of Change

  • Non-breaking change (fix or new feature that would not break existing functionality).
  • Breaking change (fix or new feature that would cause existing functionality to change).
  • New tests added to cover the changes.
  • In-line docstrings updated.
  • Documentation updated, tested make -C docs/ docs.

Testing

I did the following tests to verify my changes:

  • Quick tests passed locally by running make unit-test.
  • Integration tests pass (if applicable) by running make integration-test.

Additional Notes

virginiafdez and others added 30 commits February 22, 2026 22:20
…hanc-github-action-is-not-triggering-builds-correctly

146 bug wrong path in orthanc GitHub action is not triggering builds correctly
Adds ignore rules for generated certificates to keep private keys
and cert files out of version control.
Rename CI workflow files to reflect services and adjust trigger paths. This improves CI trigger accuracy on pull requests.

Signed-off-by: R. Garcia-Dias <rafaelagd@gmail.com>
Adds each workflow's own YAML file to the watched paths so CI runs on configuration updates.
Adjusts test workflows to reference the correct test configuration files.
Removes unused comment and adds OIDC permissions for token issuance.
Adds a codecov.yml at the repo root that enables carryforward flags for all five sub-projects (flip-api, flip-ui, imaging-api, trust-api, data-access-api). This prevents Codecov from marking reports as incomplete when only a subset of workflows run due to path-filtered push triggers. Also fixes stale self-referencing workflow filenames in the push paths filter of test_flip_api.yml and test_flip_ui.yml. Closes #144

Signed-off-by: R. Garcia-Dias <rafaelagd@gmail.com>
Rename GitHub Actions workflow names to align with updated component naming conventions, improving clarity and consistency across the repository.
…ve unused FL_API_PORT variable, and adjust S3 paths for service directories
…e-reports

Solves [Bug]: codecov incomplete reports #144
…dthedocs

145 bug fix images in readthedocs
Streamline README files across the repository by removing duplicate boilerplate and updating licensing headers.
Reorganize sections for clarity, ensuring consistent documentation structure.
Removes obsolete secret entries to keep baseline tidy.
Add per-service CONTRIBUTING.md files for flip-api, flip-ui, and trust services, documenting setup, testing, linting, signing, and PR workflow. These guides complement the root CONTRIBUTING.md and streamline onboarding of contributors.
Adds *.crt pattern to ignore and creates the trust/certs directory for certificates.
All API entrypoints hard-coded 'fastapi dev --reload' regardless of
environment, which enables file-watching and hot-reload in production.

Branch on the ENV variable (defaulting to 'development'):
- ENV=production or ENV=staging → fastapi run (no --reload)
- otherwise → fastapi dev --reload (preserves local dev behaviour)

Fixes #154
The trust services used a boolean PROD variable (0/1) to derive the
environment name, inconsistent with flip-api which uses a string ENV
variable (development/production).

Replace PROD with ENV=os.getenv("ENV", "development") across all three
trust config.py files to standardise environment detection.
The three trust services (imaging-api, data-access-api, trust-api) were
missing an explicit ENV variable in their Docker Compose environment
blocks. Without it the entrypoints defaulted to 'development' in every
deployment.

Set ENV=development in compose_trust.development.yml and
ENV=production in compose_trust.production.yml for all three services.
travellingsoldier85 and others added 3 commits March 16, 2026 17:40
When training was stopped, the 'Model Prepared' step incorrectly
showed the stopped indicator (🚫) instead of staying completed (✅).

This happened because STOPPED has a lower ordinal value than PREPARED
in ModelStatusEnum, so the comparison 'statusValue >= PREPARED'
evaluated to false. Since 'stopped' was also set to true, the AiSteps
component rendered the stop icon.

The fix ensures that terminal states (STOPPED, ERROR) do not regress
prior completed steps:
- 'Model Prepared' is always marked completed when stopped or errored
  (since training can only be stopped after preparation)
- 'Training Started' shows the stopped/error indicator instead
- 'Model Created' is always completed (unchanged)

Fixes #29
…dation

4 feature fl port consolidation and fix FLARE client-server connection
…ep-indicators-29

fix: preserve completed step indicators when training is stopped
virginiafdez and others added 10 commits March 17, 2026 17:01
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants