Skip to content

v2.21.0

Compare
Choose a tag to compare
@cvat-bot cvat-bot released this 10 Oct 09:51
· 84 commits to master since this release
67d3645

Added

  • New task mode: Honeypots (GT pool) (#8348)

  • New task creation options for quality control: Honeypots (GT pool), GT job (#8348)

  • New GT job frame selection method: random_per_job, which guarantees each job will have GT overlap (#8348)

  • [Server API] POST /jobs/: new frame selection parameters, which accept percentages, instead of absolute values (#8348)

  • [Server API] GET /api/tasks/{id}/ got a new validation_mode field, reflecting the current validation configuration (immutable) (#8348)

  • [Server API] POST /api/tasks/{id}/data got a new validation_params field, which allows to enable GT and GT_POOL validation for a task on its creation (#8348)

  • Added custom certificates documentation (#7508)

  • Support for YOLOv8 Classification format (#8475)

  • [Server API] An option to change real frames for honeypot frames in tasks with honeypots (#8471)

  • [Server API] New endpoints for validation configuration management in tasks and jobs /api/tasks/{id}/validation_layout, /api/jobs/{id}/validation_layout (#8471)

  • [Helm] Readiness and liveness probes (#8488)

Changed

  • [Server API] POST /jobs/ .frames field now expects relative frame numbers instead of absolute (source data) ones (#8348)

  • [Server API] Now chunks in tasks can be changed. There are new API elements to check chunk relevancy, if they are cached: /api/tasks/{id}/data/meta got a new field chunks_updated_date, /api/tasks/{id}/data/?type=chunk got 2 new headers: X-Updated-Date, X-Checksum (#8471)

  • Made the PATCH endpoints for projects, tasks, jobs and memberships check the input more strictly (#8493):

    • unknown fields are rejected;
    • updating a field now requires the same level of permissions regardless of whether the new value is the same as the old value.
  • [Server API] Quality report computation is now allowed to regular users (#8511)

Fixed

  • Invalid chunks for GT jobs when ?number is used in the request and task frame step > 1 (#8510)
  • Invalid output of frames for specific GT frame requests with api/jobs/{id}/data/?type=frame (#8510)