2026-01-30 23:22:05 -08:00
|
|
|
import uuid
|
|
|
|
|
from concurrent.futures import ThreadPoolExecutor
|
|
|
|
|
from pathlib import Path
|
|
|
|
|
|
|
|
|
|
import pytest
|
|
|
|
|
import requests
|
2026-03-07 17:37:25 -08:00
|
|
|
from helpers import get_asset_filename, trigger_sync_seed_assets
|
2026-01-30 23:22:05 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
def test_create_from_hash_success(
|
|
|
|
|
http: requests.Session, api_base: str, seeded_asset: dict
|
|
|
|
|
):
|
|
|
|
|
h = seeded_asset["asset_hash"]
|
|
|
|
|
payload = {
|
|
|
|
|
"hash": h,
|
|
|
|
|
"name": "from_hash_ok.safetensors",
|
|
|
|
|
"tags": ["models", "checkpoints", "unit-tests", "from-hash"],
|
|
|
|
|
"user_metadata": {"k": "v"},
|
|
|
|
|
}
|
|
|
|
|
r1 = http.post(f"{api_base}/api/assets/from-hash", json=payload, timeout=120)
|
|
|
|
|
b1 = r1.json()
|
|
|
|
|
assert r1.status_code == 201, b1
|
|
|
|
|
assert b1["asset_hash"] == h
|
2026-05-25 11:21:35 -07:00
|
|
|
assert b1["hash"] == h
|
|
|
|
|
assert b1["hash"] == b1["asset_hash"]
|
2026-01-30 23:22:05 -08:00
|
|
|
assert b1["created_new"] is False
|
|
|
|
|
aid = b1["id"]
|
|
|
|
|
|
2026-03-07 17:37:25 -08:00
|
|
|
# Calling again with the same name creates a new AssetReference (duplicates allowed)
|
2026-01-30 23:22:05 -08:00
|
|
|
r2 = http.post(f"{api_base}/api/assets/from-hash", json=payload, timeout=120)
|
|
|
|
|
b2 = r2.json()
|
|
|
|
|
assert r2.status_code == 201, b2
|
2026-03-07 17:37:25 -08:00
|
|
|
assert b2["id"] != aid # new reference, not the same one
|
2026-01-30 23:22:05 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
def test_get_and_delete_asset(http: requests.Session, api_base: str, seeded_asset: dict):
|
|
|
|
|
aid = seeded_asset["id"]
|
|
|
|
|
|
|
|
|
|
# GET detail
|
|
|
|
|
rg = http.get(f"{api_base}/api/assets/{aid}", timeout=120)
|
|
|
|
|
detail = rg.json()
|
|
|
|
|
assert rg.status_code == 200, detail
|
|
|
|
|
assert detail["id"] == aid
|
2026-05-25 11:21:35 -07:00
|
|
|
assert detail["hash"] == detail["asset_hash"]
|
2026-01-30 23:22:05 -08:00
|
|
|
assert "user_metadata" in detail
|
|
|
|
|
assert "filename" in detail["user_metadata"]
|
|
|
|
|
|
fix(assets): remove unused delete_content param from deleteAsset (#14241)
* fix(assets): remove unused delete_content param from deleteAsset
The delete_content query param on DELETE /api/assets/{id} was introduced
in #12125 and had its default flipped to false in #12621. In practice no
client sends it: the frontend issues a bare DELETE /assets/{id}, so every
real caller already gets the default soft-delete (the reference is hidden,
content preserved). The only thing that set delete_content=true was this
repo's own test teardown.
Remove the param from the route and the OpenAPI spec so the contract
matches what clients actually use (and lines up with the cloud surface).
The route now always soft-deletes. The underlying delete_asset_reference
helper keeps its delete_content_if_orphan option, so orphan reclamation
remains available internally for a future GC path — it's just no longer
exposed on the public endpoint. Tests that used delete_content=true for
hard cleanup now soft-delete; test_delete_upon_reference_count asserts
content preservation instead of orphan removal.
* test/docs: address review on deleteAsset delete_content removal
- Rename test_delete_upon_reference_count ->
test_soft_delete_preserves_asset_identity_across_references; the old name
implied last-ref cleanup, but it now verifies the opposite (soft delete
preserves identity across references).
- Strengthen the re-association assertion: also check asset_hash == src_hash
so it proves content reuse rather than relying on the now-tautological
created_new is False.
- Document delete_asset_reference: the orphan-reclamation branch is
intentionally internal-only; the public endpoint always soft-deletes.
- Normalize the soft-delete comment phrasing.
* test(assets): make seed content unique per test for isolation
Removing the delete_content param means delete is always a soft delete, so
content created by one test now survives into the next. The suite had been
relying on hard-delete teardown for isolation, so shared fixed-content
fixtures started colliding: seeded_asset (b"A"*4096) and
make_asset_bytes (deterministic on name) produced the same hash every test,
so the second seed deduped to the surviving asset and returned 200 instead
of 201, cascading into ~14 failures/errors.
Salt both fixtures with a per-test uuid so each test creates fresh content
(created_new True, 201), while keeping content deterministic within a test
(same name/size -> same bytes) and preserving exact byte length so size-based
list/sort assertions are unaffected.
2026-06-09 21:52:14 -07:00
|
|
|
# Soft delete — the reference is hidden, content is preserved
|
|
|
|
|
rd = http.delete(f"{api_base}/api/assets/{aid}", timeout=120)
|
2026-01-30 23:22:05 -08:00
|
|
|
assert rd.status_code == 204
|
|
|
|
|
|
|
|
|
|
# GET again -> 404
|
|
|
|
|
rg2 = http.get(f"{api_base}/api/assets/{aid}", timeout=120)
|
|
|
|
|
body = rg2.json()
|
|
|
|
|
assert rg2.status_code == 404
|
|
|
|
|
assert body["error"]["code"] == "ASSET_NOT_FOUND"
|
|
|
|
|
|
|
|
|
|
|
2026-03-07 17:37:25 -08:00
|
|
|
def test_soft_delete_hides_from_get(http: requests.Session, api_base: str, seeded_asset: dict):
|
|
|
|
|
aid = seeded_asset["id"]
|
|
|
|
|
asset_hash = seeded_asset["asset_hash"]
|
|
|
|
|
|
fix(assets): remove unused delete_content param from deleteAsset (#14241)
* fix(assets): remove unused delete_content param from deleteAsset
The delete_content query param on DELETE /api/assets/{id} was introduced
in #12125 and had its default flipped to false in #12621. In practice no
client sends it: the frontend issues a bare DELETE /assets/{id}, so every
real caller already gets the default soft-delete (the reference is hidden,
content preserved). The only thing that set delete_content=true was this
repo's own test teardown.
Remove the param from the route and the OpenAPI spec so the contract
matches what clients actually use (and lines up with the cloud surface).
The route now always soft-deletes. The underlying delete_asset_reference
helper keeps its delete_content_if_orphan option, so orphan reclamation
remains available internally for a future GC path — it's just no longer
exposed on the public endpoint. Tests that used delete_content=true for
hard cleanup now soft-delete; test_delete_upon_reference_count asserts
content preservation instead of orphan removal.
* test/docs: address review on deleteAsset delete_content removal
- Rename test_delete_upon_reference_count ->
test_soft_delete_preserves_asset_identity_across_references; the old name
implied last-ref cleanup, but it now verifies the opposite (soft delete
preserves identity across references).
- Strengthen the re-association assertion: also check asset_hash == src_hash
so it proves content reuse rather than relying on the now-tautological
created_new is False.
- Document delete_asset_reference: the orphan-reclamation branch is
intentionally internal-only; the public endpoint always soft-deletes.
- Normalize the soft-delete comment phrasing.
* test(assets): make seed content unique per test for isolation
Removing the delete_content param means delete is always a soft delete, so
content created by one test now survives into the next. The suite had been
relying on hard-delete teardown for isolation, so shared fixed-content
fixtures started colliding: seeded_asset (b"A"*4096) and
make_asset_bytes (deterministic on name) produced the same hash every test,
so the second seed deduped to the surviving asset and returned 200 instead
of 201, cascading into ~14 failures/errors.
Salt both fixtures with a per-test uuid so each test creates fresh content
(created_new True, 201), while keeping content deterministic within a test
(same name/size -> same bytes) and preserving exact byte length so size-based
list/sort assertions are unaffected.
2026-06-09 21:52:14 -07:00
|
|
|
# Soft delete — the reference is hidden, content is preserved
|
2026-03-07 17:37:25 -08:00
|
|
|
rd = http.delete(f"{api_base}/api/assets/{aid}", timeout=120)
|
|
|
|
|
assert rd.status_code == 204
|
|
|
|
|
|
|
|
|
|
# GET by reference ID -> 404 (soft-deleted references are hidden)
|
|
|
|
|
rg = http.get(f"{api_base}/api/assets/{aid}", timeout=120)
|
|
|
|
|
assert rg.status_code == 404
|
|
|
|
|
|
|
|
|
|
# Asset identity is preserved (underlying content still exists)
|
|
|
|
|
rh = http.head(f"{api_base}/api/assets/hash/{asset_hash}", timeout=120)
|
|
|
|
|
assert rh.status_code == 200
|
|
|
|
|
|
|
|
|
|
# Soft-deleted reference should not appear in listings
|
|
|
|
|
rl = http.get(
|
|
|
|
|
f"{api_base}/api/assets",
|
|
|
|
|
params={"include_tags": "unit-tests", "limit": "500"},
|
|
|
|
|
timeout=120,
|
|
|
|
|
)
|
|
|
|
|
ids = [a["id"] for a in rl.json().get("assets", [])]
|
|
|
|
|
assert aid not in ids
|
|
|
|
|
|
fix(assets): remove unused delete_content param from deleteAsset (#14241)
* fix(assets): remove unused delete_content param from deleteAsset
The delete_content query param on DELETE /api/assets/{id} was introduced
in #12125 and had its default flipped to false in #12621. In practice no
client sends it: the frontend issues a bare DELETE /assets/{id}, so every
real caller already gets the default soft-delete (the reference is hidden,
content preserved). The only thing that set delete_content=true was this
repo's own test teardown.
Remove the param from the route and the OpenAPI spec so the contract
matches what clients actually use (and lines up with the cloud surface).
The route now always soft-deletes. The underlying delete_asset_reference
helper keeps its delete_content_if_orphan option, so orphan reclamation
remains available internally for a future GC path — it's just no longer
exposed on the public endpoint. Tests that used delete_content=true for
hard cleanup now soft-delete; test_delete_upon_reference_count asserts
content preservation instead of orphan removal.
* test/docs: address review on deleteAsset delete_content removal
- Rename test_delete_upon_reference_count ->
test_soft_delete_preserves_asset_identity_across_references; the old name
implied last-ref cleanup, but it now verifies the opposite (soft delete
preserves identity across references).
- Strengthen the re-association assertion: also check asset_hash == src_hash
so it proves content reuse rather than relying on the now-tautological
created_new is False.
- Document delete_asset_reference: the orphan-reclamation branch is
intentionally internal-only; the public endpoint always soft-deletes.
- Normalize the soft-delete comment phrasing.
* test(assets): make seed content unique per test for isolation
Removing the delete_content param means delete is always a soft delete, so
content created by one test now survives into the next. The suite had been
relying on hard-delete teardown for isolation, so shared fixed-content
fixtures started colliding: seeded_asset (b"A"*4096) and
make_asset_bytes (deterministic on name) produced the same hash every test,
so the second seed deduped to the surviving asset and returned 200 instead
of 201, cascading into ~14 failures/errors.
Salt both fixtures with a per-test uuid so each test creates fresh content
(created_new True, 201), while keeping content deterministic within a test
(same name/size -> same bytes) and preserving exact byte length so size-based
list/sort assertions are unaffected.
2026-06-09 21:52:14 -07:00
|
|
|
# The reference is already soft-deleted; content is preserved.
|
2026-03-07 17:37:25 -08:00
|
|
|
|
|
|
|
|
|
fix(assets): remove unused delete_content param from deleteAsset (#14241)
* fix(assets): remove unused delete_content param from deleteAsset
The delete_content query param on DELETE /api/assets/{id} was introduced
in #12125 and had its default flipped to false in #12621. In practice no
client sends it: the frontend issues a bare DELETE /assets/{id}, so every
real caller already gets the default soft-delete (the reference is hidden,
content preserved). The only thing that set delete_content=true was this
repo's own test teardown.
Remove the param from the route and the OpenAPI spec so the contract
matches what clients actually use (and lines up with the cloud surface).
The route now always soft-deletes. The underlying delete_asset_reference
helper keeps its delete_content_if_orphan option, so orphan reclamation
remains available internally for a future GC path — it's just no longer
exposed on the public endpoint. Tests that used delete_content=true for
hard cleanup now soft-delete; test_delete_upon_reference_count asserts
content preservation instead of orphan removal.
* test/docs: address review on deleteAsset delete_content removal
- Rename test_delete_upon_reference_count ->
test_soft_delete_preserves_asset_identity_across_references; the old name
implied last-ref cleanup, but it now verifies the opposite (soft delete
preserves identity across references).
- Strengthen the re-association assertion: also check asset_hash == src_hash
so it proves content reuse rather than relying on the now-tautological
created_new is False.
- Document delete_asset_reference: the orphan-reclamation branch is
intentionally internal-only; the public endpoint always soft-deletes.
- Normalize the soft-delete comment phrasing.
* test(assets): make seed content unique per test for isolation
Removing the delete_content param means delete is always a soft delete, so
content created by one test now survives into the next. The suite had been
relying on hard-delete teardown for isolation, so shared fixed-content
fixtures started colliding: seeded_asset (b"A"*4096) and
make_asset_bytes (deterministic on name) produced the same hash every test,
so the second seed deduped to the surviving asset and returned 200 instead
of 201, cascading into ~14 failures/errors.
Salt both fixtures with a per-test uuid so each test creates fresh content
(created_new True, 201), while keeping content deterministic within a test
(same name/size -> same bytes) and preserving exact byte length so size-based
list/sort assertions are unaffected.
2026-06-09 21:52:14 -07:00
|
|
|
def test_soft_delete_preserves_asset_identity_across_references(
|
2026-01-30 23:22:05 -08:00
|
|
|
http: requests.Session, api_base: str, seeded_asset: dict
|
|
|
|
|
):
|
|
|
|
|
# Create a second reference to the same asset via from-hash
|
|
|
|
|
src_hash = seeded_asset["asset_hash"]
|
|
|
|
|
payload = {
|
|
|
|
|
"hash": src_hash,
|
|
|
|
|
"name": "unit_ref_copy.safetensors",
|
|
|
|
|
"tags": ["models", "checkpoints", "unit-tests", "del-flow"],
|
|
|
|
|
"user_metadata": {"note": "copy"},
|
|
|
|
|
}
|
|
|
|
|
r2 = http.post(f"{api_base}/api/assets/from-hash", json=payload, timeout=120)
|
|
|
|
|
copy = r2.json()
|
|
|
|
|
assert r2.status_code == 201, copy
|
|
|
|
|
assert copy["asset_hash"] == src_hash
|
2026-05-25 11:21:35 -07:00
|
|
|
assert copy["hash"] == src_hash
|
2026-01-30 23:22:05 -08:00
|
|
|
assert copy["created_new"] is False
|
|
|
|
|
|
2026-03-07 17:37:25 -08:00
|
|
|
# Soft-delete original reference (default) -> asset identity must remain
|
2026-01-30 23:22:05 -08:00
|
|
|
aid1 = seeded_asset["id"]
|
|
|
|
|
rd1 = http.delete(f"{api_base}/api/assets/{aid1}", timeout=120)
|
|
|
|
|
assert rd1.status_code == 204
|
|
|
|
|
|
|
|
|
|
rh1 = http.head(f"{api_base}/api/assets/hash/{src_hash}", timeout=120)
|
2026-03-07 17:37:25 -08:00
|
|
|
assert rh1.status_code == 200 # identity still present (second ref exists)
|
2026-01-30 23:22:05 -08:00
|
|
|
|
2026-03-07 17:37:25 -08:00
|
|
|
# Soft-delete the last reference -> asset identity preserved (no hard delete)
|
2026-01-30 23:22:05 -08:00
|
|
|
aid2 = copy["id"]
|
|
|
|
|
rd2 = http.delete(f"{api_base}/api/assets/{aid2}", timeout=120)
|
|
|
|
|
assert rd2.status_code == 204
|
|
|
|
|
|
|
|
|
|
rh2 = http.head(f"{api_base}/api/assets/hash/{src_hash}", timeout=120)
|
2026-03-07 17:37:25 -08:00
|
|
|
assert rh2.status_code == 200 # asset identity preserved (soft delete)
|
|
|
|
|
|
fix(assets): remove unused delete_content param from deleteAsset (#14241)
* fix(assets): remove unused delete_content param from deleteAsset
The delete_content query param on DELETE /api/assets/{id} was introduced
in #12125 and had its default flipped to false in #12621. In practice no
client sends it: the frontend issues a bare DELETE /assets/{id}, so every
real caller already gets the default soft-delete (the reference is hidden,
content preserved). The only thing that set delete_content=true was this
repo's own test teardown.
Remove the param from the route and the OpenAPI spec so the contract
matches what clients actually use (and lines up with the cloud surface).
The route now always soft-deletes. The underlying delete_asset_reference
helper keeps its delete_content_if_orphan option, so orphan reclamation
remains available internally for a future GC path — it's just no longer
exposed on the public endpoint. Tests that used delete_content=true for
hard cleanup now soft-delete; test_delete_upon_reference_count asserts
content preservation instead of orphan removal.
* test/docs: address review on deleteAsset delete_content removal
- Rename test_delete_upon_reference_count ->
test_soft_delete_preserves_asset_identity_across_references; the old name
implied last-ref cleanup, but it now verifies the opposite (soft delete
preserves identity across references).
- Strengthen the re-association assertion: also check asset_hash == src_hash
so it proves content reuse rather than relying on the now-tautological
created_new is False.
- Document delete_asset_reference: the orphan-reclamation branch is
intentionally internal-only; the public endpoint always soft-deletes.
- Normalize the soft-delete comment phrasing.
* test(assets): make seed content unique per test for isolation
Removing the delete_content param means delete is always a soft delete, so
content created by one test now survives into the next. The suite had been
relying on hard-delete teardown for isolation, so shared fixed-content
fixtures started colliding: seeded_asset (b"A"*4096) and
make_asset_bytes (deterministic on name) produced the same hash every test,
so the second seed deduped to the surviving asset and returned 200 instead
of 201, cascading into ~14 failures/errors.
Salt both fixtures with a per-test uuid so each test creates fresh content
(created_new True, 201), while keeping content deterministic within a test
(same name/size -> same bytes) and preserving exact byte length so size-based
list/sort assertions are unaffected.
2026-06-09 21:52:14 -07:00
|
|
|
# Re-associate via from-hash: it must reuse the same preserved content
|
|
|
|
|
# (created_new False AND the same hash), proving the soft deletes did not
|
|
|
|
|
# destroy the underlying asset. Then soft-delete again -> still preserved.
|
2026-03-07 17:37:25 -08:00
|
|
|
r3 = http.post(f"{api_base}/api/assets/from-hash", json=payload, timeout=120)
|
|
|
|
|
assert r3.status_code == 201, r3.json()
|
fix(assets): remove unused delete_content param from deleteAsset (#14241)
* fix(assets): remove unused delete_content param from deleteAsset
The delete_content query param on DELETE /api/assets/{id} was introduced
in #12125 and had its default flipped to false in #12621. In practice no
client sends it: the frontend issues a bare DELETE /assets/{id}, so every
real caller already gets the default soft-delete (the reference is hidden,
content preserved). The only thing that set delete_content=true was this
repo's own test teardown.
Remove the param from the route and the OpenAPI spec so the contract
matches what clients actually use (and lines up with the cloud surface).
The route now always soft-deletes. The underlying delete_asset_reference
helper keeps its delete_content_if_orphan option, so orphan reclamation
remains available internally for a future GC path — it's just no longer
exposed on the public endpoint. Tests that used delete_content=true for
hard cleanup now soft-delete; test_delete_upon_reference_count asserts
content preservation instead of orphan removal.
* test/docs: address review on deleteAsset delete_content removal
- Rename test_delete_upon_reference_count ->
test_soft_delete_preserves_asset_identity_across_references; the old name
implied last-ref cleanup, but it now verifies the opposite (soft delete
preserves identity across references).
- Strengthen the re-association assertion: also check asset_hash == src_hash
so it proves content reuse rather than relying on the now-tautological
created_new is False.
- Document delete_asset_reference: the orphan-reclamation branch is
intentionally internal-only; the public endpoint always soft-deletes.
- Normalize the soft-delete comment phrasing.
* test(assets): make seed content unique per test for isolation
Removing the delete_content param means delete is always a soft delete, so
content created by one test now survives into the next. The suite had been
relying on hard-delete teardown for isolation, so shared fixed-content
fixtures started colliding: seeded_asset (b"A"*4096) and
make_asset_bytes (deterministic on name) produced the same hash every test,
so the second seed deduped to the surviving asset and returned 200 instead
of 201, cascading into ~14 failures/errors.
Salt both fixtures with a per-test uuid so each test creates fresh content
(created_new True, 201), while keeping content deterministic within a test
(same name/size -> same bytes) and preserving exact byte length so size-based
list/sort assertions are unaffected.
2026-06-09 21:52:14 -07:00
|
|
|
assert r3.json()["created_new"] is False
|
|
|
|
|
assert r3.json()["asset_hash"] == src_hash # reused the surviving content
|
2026-03-07 17:37:25 -08:00
|
|
|
aid3 = r3.json()["id"]
|
|
|
|
|
|
fix(assets): remove unused delete_content param from deleteAsset (#14241)
* fix(assets): remove unused delete_content param from deleteAsset
The delete_content query param on DELETE /api/assets/{id} was introduced
in #12125 and had its default flipped to false in #12621. In practice no
client sends it: the frontend issues a bare DELETE /assets/{id}, so every
real caller already gets the default soft-delete (the reference is hidden,
content preserved). The only thing that set delete_content=true was this
repo's own test teardown.
Remove the param from the route and the OpenAPI spec so the contract
matches what clients actually use (and lines up with the cloud surface).
The route now always soft-deletes. The underlying delete_asset_reference
helper keeps its delete_content_if_orphan option, so orphan reclamation
remains available internally for a future GC path — it's just no longer
exposed on the public endpoint. Tests that used delete_content=true for
hard cleanup now soft-delete; test_delete_upon_reference_count asserts
content preservation instead of orphan removal.
* test/docs: address review on deleteAsset delete_content removal
- Rename test_delete_upon_reference_count ->
test_soft_delete_preserves_asset_identity_across_references; the old name
implied last-ref cleanup, but it now verifies the opposite (soft delete
preserves identity across references).
- Strengthen the re-association assertion: also check asset_hash == src_hash
so it proves content reuse rather than relying on the now-tautological
created_new is False.
- Document delete_asset_reference: the orphan-reclamation branch is
intentionally internal-only; the public endpoint always soft-deletes.
- Normalize the soft-delete comment phrasing.
* test(assets): make seed content unique per test for isolation
Removing the delete_content param means delete is always a soft delete, so
content created by one test now survives into the next. The suite had been
relying on hard-delete teardown for isolation, so shared fixed-content
fixtures started colliding: seeded_asset (b"A"*4096) and
make_asset_bytes (deterministic on name) produced the same hash every test,
so the second seed deduped to the surviving asset and returned 200 instead
of 201, cascading into ~14 failures/errors.
Salt both fixtures with a per-test uuid so each test creates fresh content
(created_new True, 201), while keeping content deterministic within a test
(same name/size -> same bytes) and preserving exact byte length so size-based
list/sort assertions are unaffected.
2026-06-09 21:52:14 -07:00
|
|
|
rd3 = http.delete(f"{api_base}/api/assets/{aid3}", timeout=120)
|
2026-03-07 17:37:25 -08:00
|
|
|
assert rd3.status_code == 204
|
|
|
|
|
|
|
|
|
|
rh3 = http.head(f"{api_base}/api/assets/hash/{src_hash}", timeout=120)
|
fix(assets): remove unused delete_content param from deleteAsset (#14241)
* fix(assets): remove unused delete_content param from deleteAsset
The delete_content query param on DELETE /api/assets/{id} was introduced
in #12125 and had its default flipped to false in #12621. In practice no
client sends it: the frontend issues a bare DELETE /assets/{id}, so every
real caller already gets the default soft-delete (the reference is hidden,
content preserved). The only thing that set delete_content=true was this
repo's own test teardown.
Remove the param from the route and the OpenAPI spec so the contract
matches what clients actually use (and lines up with the cloud surface).
The route now always soft-deletes. The underlying delete_asset_reference
helper keeps its delete_content_if_orphan option, so orphan reclamation
remains available internally for a future GC path — it's just no longer
exposed on the public endpoint. Tests that used delete_content=true for
hard cleanup now soft-delete; test_delete_upon_reference_count asserts
content preservation instead of orphan removal.
* test/docs: address review on deleteAsset delete_content removal
- Rename test_delete_upon_reference_count ->
test_soft_delete_preserves_asset_identity_across_references; the old name
implied last-ref cleanup, but it now verifies the opposite (soft delete
preserves identity across references).
- Strengthen the re-association assertion: also check asset_hash == src_hash
so it proves content reuse rather than relying on the now-tautological
created_new is False.
- Document delete_asset_reference: the orphan-reclamation branch is
intentionally internal-only; the public endpoint always soft-deletes.
- Normalize the soft-delete comment phrasing.
* test(assets): make seed content unique per test for isolation
Removing the delete_content param means delete is always a soft delete, so
content created by one test now survives into the next. The suite had been
relying on hard-delete teardown for isolation, so shared fixed-content
fixtures started colliding: seeded_asset (b"A"*4096) and
make_asset_bytes (deterministic on name) produced the same hash every test,
so the second seed deduped to the surviving asset and returned 200 instead
of 201, cascading into ~14 failures/errors.
Salt both fixtures with a per-test uuid so each test creates fresh content
(created_new True, 201), while keeping content deterministic within a test
(same name/size -> same bytes) and preserving exact byte length so size-based
list/sort assertions are unaffected.
2026-06-09 21:52:14 -07:00
|
|
|
assert rh3.status_code == 200 # content preserved (soft delete)
|
2026-01-30 23:22:05 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
def test_update_asset_fields(http: requests.Session, api_base: str, seeded_asset: dict):
|
|
|
|
|
aid = seeded_asset["id"]
|
|
|
|
|
original_tags = seeded_asset["tags"]
|
|
|
|
|
|
|
|
|
|
payload = {
|
|
|
|
|
"name": "unit_1_renamed.safetensors",
|
|
|
|
|
"user_metadata": {"purpose": "updated", "epoch": 2},
|
|
|
|
|
}
|
|
|
|
|
ru = http.put(f"{api_base}/api/assets/{aid}", json=payload, timeout=120)
|
|
|
|
|
body = ru.json()
|
|
|
|
|
assert ru.status_code == 200, body
|
|
|
|
|
assert body["name"] == payload["name"]
|
2026-05-25 11:21:35 -07:00
|
|
|
assert body["hash"] == body["asset_hash"]
|
2026-01-30 23:22:05 -08:00
|
|
|
assert body["tags"] == original_tags # tags unchanged
|
|
|
|
|
assert body["user_metadata"]["purpose"] == "updated"
|
|
|
|
|
# filename should still be present and normalized by server
|
|
|
|
|
assert "filename" in body["user_metadata"]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
def test_head_asset_by_hash(http: requests.Session, api_base: str, seeded_asset: dict):
|
|
|
|
|
h = seeded_asset["asset_hash"]
|
|
|
|
|
|
|
|
|
|
# Existing
|
|
|
|
|
rh1 = http.head(f"{api_base}/api/assets/hash/{h}", timeout=120)
|
|
|
|
|
assert rh1.status_code == 200
|
|
|
|
|
|
|
|
|
|
# Non-existent
|
|
|
|
|
rh2 = http.head(f"{api_base}/api/assets/hash/blake3:{'0'*64}", timeout=120)
|
|
|
|
|
assert rh2.status_code == 404
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
def test_head_asset_bad_hash_returns_400_and_no_body(http: requests.Session, api_base: str):
|
|
|
|
|
# Invalid format; handler returns a JSON error, but HEAD responses must not carry a payload.
|
|
|
|
|
# requests exposes an empty body for HEAD, so validate status and that there is no payload.
|
|
|
|
|
rh = http.head(f"{api_base}/api/assets/hash/not_a_hash", timeout=120)
|
|
|
|
|
assert rh.status_code == 400
|
|
|
|
|
body = rh.content
|
|
|
|
|
assert body == b""
|
|
|
|
|
|
|
|
|
|
|
2026-03-07 17:37:25 -08:00
|
|
|
@pytest.mark.parametrize(
|
|
|
|
|
"method,endpoint_template,payload,expected_status,error_code",
|
|
|
|
|
[
|
|
|
|
|
# Delete nonexistent asset
|
|
|
|
|
("delete", "/api/assets/{uuid}", None, 404, "ASSET_NOT_FOUND"),
|
|
|
|
|
# Bad hash algorithm in from-hash
|
|
|
|
|
(
|
|
|
|
|
"post",
|
|
|
|
|
"/api/assets/from-hash",
|
|
|
|
|
{"hash": "sha256:" + "0" * 64, "name": "x.bin", "tags": ["models", "checkpoints", "unit-tests"]},
|
|
|
|
|
400,
|
|
|
|
|
"INVALID_BODY",
|
|
|
|
|
),
|
|
|
|
|
# Get with bad UUID format
|
|
|
|
|
("get", "/api/assets/not-a-uuid", None, 404, None),
|
|
|
|
|
# Get content with bad UUID format
|
|
|
|
|
("get", "/api/assets/not-a-uuid/content", None, 404, None),
|
|
|
|
|
],
|
|
|
|
|
ids=["delete_nonexistent", "bad_hash_algorithm", "get_bad_uuid", "content_bad_uuid"],
|
|
|
|
|
)
|
|
|
|
|
def test_error_responses(
|
|
|
|
|
http: requests.Session, api_base: str, method, endpoint_template, payload, expected_status, error_code
|
|
|
|
|
):
|
|
|
|
|
# Replace {uuid} placeholder with a random UUID for delete test
|
|
|
|
|
endpoint = endpoint_template.replace("{uuid}", str(uuid.uuid4()))
|
|
|
|
|
url = f"{api_base}{endpoint}"
|
|
|
|
|
|
|
|
|
|
if method == "get":
|
|
|
|
|
r = http.get(url, timeout=120)
|
|
|
|
|
elif method == "post":
|
|
|
|
|
r = http.post(url, json=payload, timeout=120)
|
|
|
|
|
elif method == "delete":
|
|
|
|
|
r = http.delete(url, timeout=120)
|
|
|
|
|
|
|
|
|
|
assert r.status_code == expected_status
|
|
|
|
|
if error_code:
|
|
|
|
|
body = r.json()
|
|
|
|
|
assert body["error"]["code"] == error_code
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
def test_create_from_hash_invalid_json(http: requests.Session, api_base: str):
|
|
|
|
|
"""Invalid JSON body requires special handling (data= instead of json=)."""
|
|
|
|
|
r = http.post(f"{api_base}/api/assets/from-hash", data=b"{not json}", timeout=120)
|
2026-01-30 23:22:05 -08:00
|
|
|
body = r.json()
|
2026-03-07 17:37:25 -08:00
|
|
|
assert r.status_code == 400
|
|
|
|
|
assert body["error"]["code"] == "INVALID_JSON"
|
2026-01-30 23:22:05 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
def test_update_requires_at_least_one_field(http: requests.Session, api_base: str, seeded_asset: dict):
|
|
|
|
|
aid = seeded_asset["id"]
|
|
|
|
|
r = http.put(f"{api_base}/api/assets/{aid}", json={}, timeout=120)
|
|
|
|
|
body = r.json()
|
|
|
|
|
assert r.status_code == 400
|
|
|
|
|
assert body["error"]["code"] == "INVALID_BODY"
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
@pytest.mark.parametrize("root", ["input", "output"])
|
|
|
|
|
def test_concurrent_delete_same_asset_info_single_204(
|
|
|
|
|
root: str,
|
|
|
|
|
http: requests.Session,
|
|
|
|
|
api_base: str,
|
|
|
|
|
asset_factory,
|
|
|
|
|
make_asset_bytes,
|
|
|
|
|
):
|
|
|
|
|
"""
|
|
|
|
|
Many concurrent DELETE for the same AssetInfo should result in:
|
|
|
|
|
- exactly one 204 No Content (the one that actually deleted)
|
|
|
|
|
- all others 404 Not Found (row already gone)
|
|
|
|
|
"""
|
|
|
|
|
scope = f"conc-del-{uuid.uuid4().hex[:6]}"
|
|
|
|
|
name = "to_delete.bin"
|
|
|
|
|
data = make_asset_bytes(name, 1536)
|
|
|
|
|
|
|
|
|
|
created = asset_factory(name, [root, "unit-tests", scope], {}, data)
|
|
|
|
|
aid = created["id"]
|
|
|
|
|
|
|
|
|
|
# Hit the same endpoint N times in parallel.
|
|
|
|
|
n_tests = 4
|
fix(assets): remove unused delete_content param from deleteAsset (#14241)
* fix(assets): remove unused delete_content param from deleteAsset
The delete_content query param on DELETE /api/assets/{id} was introduced
in #12125 and had its default flipped to false in #12621. In practice no
client sends it: the frontend issues a bare DELETE /assets/{id}, so every
real caller already gets the default soft-delete (the reference is hidden,
content preserved). The only thing that set delete_content=true was this
repo's own test teardown.
Remove the param from the route and the OpenAPI spec so the contract
matches what clients actually use (and lines up with the cloud surface).
The route now always soft-deletes. The underlying delete_asset_reference
helper keeps its delete_content_if_orphan option, so orphan reclamation
remains available internally for a future GC path — it's just no longer
exposed on the public endpoint. Tests that used delete_content=true for
hard cleanup now soft-delete; test_delete_upon_reference_count asserts
content preservation instead of orphan removal.
* test/docs: address review on deleteAsset delete_content removal
- Rename test_delete_upon_reference_count ->
test_soft_delete_preserves_asset_identity_across_references; the old name
implied last-ref cleanup, but it now verifies the opposite (soft delete
preserves identity across references).
- Strengthen the re-association assertion: also check asset_hash == src_hash
so it proves content reuse rather than relying on the now-tautological
created_new is False.
- Document delete_asset_reference: the orphan-reclamation branch is
intentionally internal-only; the public endpoint always soft-deletes.
- Normalize the soft-delete comment phrasing.
* test(assets): make seed content unique per test for isolation
Removing the delete_content param means delete is always a soft delete, so
content created by one test now survives into the next. The suite had been
relying on hard-delete teardown for isolation, so shared fixed-content
fixtures started colliding: seeded_asset (b"A"*4096) and
make_asset_bytes (deterministic on name) produced the same hash every test,
so the second seed deduped to the surviving asset and returned 200 instead
of 201, cascading into ~14 failures/errors.
Salt both fixtures with a per-test uuid so each test creates fresh content
(created_new True, 201), while keeping content deterministic within a test
(same name/size -> same bytes) and preserving exact byte length so size-based
list/sort assertions are unaffected.
2026-06-09 21:52:14 -07:00
|
|
|
url = f"{api_base}/api/assets/{aid}"
|
2026-01-30 23:22:05 -08:00
|
|
|
|
|
|
|
|
def _do_delete(delete_url):
|
|
|
|
|
with requests.Session() as s:
|
|
|
|
|
return s.delete(delete_url, timeout=120).status_code
|
|
|
|
|
|
|
|
|
|
with ThreadPoolExecutor(max_workers=n_tests) as ex:
|
|
|
|
|
statuses = list(ex.map(_do_delete, [url] * n_tests))
|
|
|
|
|
|
|
|
|
|
# Exactly one actual delete, the rest must be 404
|
|
|
|
|
assert statuses.count(204) == 1, f"Expected exactly one 204; got: {statuses}"
|
|
|
|
|
assert statuses.count(404) == n_tests - 1, f"Expected {n_tests-1} 404; got: {statuses}"
|
|
|
|
|
|
|
|
|
|
# The resource must be gone.
|
|
|
|
|
rg = http.get(f"{api_base}/api/assets/{aid}", timeout=120)
|
|
|
|
|
assert rg.status_code == 404
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
@pytest.mark.parametrize("root", ["input", "output"])
|
|
|
|
|
def test_metadata_filename_is_set_for_seed_asset_without_hash(
|
|
|
|
|
root: str,
|
|
|
|
|
http: requests.Session,
|
|
|
|
|
api_base: str,
|
|
|
|
|
comfy_tmp_base_dir: Path,
|
|
|
|
|
):
|
|
|
|
|
"""Seed ingest (no hash yet) must compute user_metadata['filename'] immediately."""
|
|
|
|
|
scope = f"seedmeta-{uuid.uuid4().hex[:6]}"
|
|
|
|
|
name = "seed_filename.bin"
|
|
|
|
|
|
|
|
|
|
base = comfy_tmp_base_dir / root / "unit-tests" / scope / "a" / "b"
|
|
|
|
|
base.mkdir(parents=True, exist_ok=True)
|
|
|
|
|
fp = base / name
|
|
|
|
|
fp.write_bytes(b"Z" * 2048)
|
|
|
|
|
|
|
|
|
|
trigger_sync_seed_assets(http, api_base)
|
|
|
|
|
|
|
|
|
|
r1 = http.get(
|
|
|
|
|
api_base + "/api/assets",
|
feat(assets): add namespaced model_type tags and align tag semantics (#14511)
* feat(assets): add namespaced model type tags
* fix(assets): mark path-derived upload tags automatic
* fix(assets): merge duplicate scan specs
* test(assets): make duplicate path normalization portable
* feat(assets): add loader_path as the authoritative loader locator (#14796)
* fix(assets): filter model_type tags by bucket extension sets
Buckets sharing a base directory (e.g. diffusion_models and a custom
unet_gguf) tagged every file in the directory regardless of whether the
bucket could load it, so .safetensors files were tagged
model_type:unet_gguf and vice versa. Carry each bucket's registered
extension set through get_comfy_models_folders and only emit a
model_type tag when the file extension matches, keeping the empty-set
match-all convention from folder_paths.filter_files_extensions.
Files under a model base matching no bucket now keep only the models
tag instead of every directory-matching model_type tag.
* feat(assets): replace response file_path with persisted loader_path
The old file_path response field was a namespaced storage locator
(models/checkpoints/foo.safetensors): not an absolute path, not unique
identity, and not the value a loader consumes. Nothing needs that shape
on the wire (hash/ID-based locating is the long-term direction), so it
is dropped rather than renamed; the storage-root matching stays internal,
powering display_name.
What loaders DO need is the in-root loader path (category dropped:
models/checkpoints/foo/bar.safetensors -> foo/bar.safetensors). Serve it
as a first-class loader_path field, persisted on asset_references
(migration 0006) and written by every ingest pipeline at insert, so
responses read the column verbatim.
Like the model_type tags, loader_path is a seed-time derivative of the
model folder registry, maintained by the same scan lifecycle (new files seed
fresh values, pruning retires rows whose bucket disappeared). Rows
predating the column serve a null loader_path; databases from before
this stack already need recreating for the base branch's tag changes.
loader_path resolves every registered base including extra_model_paths
entries; display_name only the canonical storage roots. A file can
therefore be loadable with no display name (extra-path models) or the
reverse (unregistered files under the models root), and loader_path is
null exactly when no loader can resolve the file.
* test(assets): lock loader_path matrix (asymmetry, null, persist/read)
Cover the behaviour that has no production change but is easy to regress:
the extra-path asymmetry (loadable but no storage namespace), null
loader_path persistence for orphan files, and the response reading the
stored column with a compute fallback for un-backfilled rows.
* fix(assets): persist subfolder-qualified loader_path for ingested outputs
ingest_existing_file built its seed spec with the file's basename, so
outputs saved into a subfolder persisted loader_path (and the
user_metadata filename that preview URLs split for their subfolder
param) as just the basename: the served locator pointed at a file that
does not exist at that path. Scanner and seeder specs already derive
fname via compute_loader_path; use the same derivation here.
* fix(assets): only extension-matching buckets contribute a loader_path
The model-base match in get_asset_category_and_relative_path ignored
each bucket's extension set, so a file inside a registered base whose
extension the bucket cannot load (e.g. a .txt uploaded into
model_type:checkpoints) advertised a loader_path that no loader list
would ever resolve, while the tag side of the same stack already
excluded it. Apply the extension check used for backend tags (empty set
accepts any extension), keeping loader_path null exactly when no loader
can resolve the file.
* fix(assets): refresh loader_path when re-ingesting an existing reference
upsert_reference only wrote loader_path on the INSERT branch, so
re-ingesting an existing reference (an output overwritten in place, or a
file re-registered after its loader_path derivation changed) kept the
stale or NULL value forever. Write it on the UPDATE branch too, with a
null-safe change guard so a loader_path difference alone is enough to
trigger the update, and identical values stay a no-op.
* fix(assets): repair semantic merge breakage from #14796 and master
Two textually-clean but semantically-broken merges:
- routes.py lost its folder_paths import when #14796's import block
superseded the base's, while the content-type hardening added via the
base's master merge still calls folder_paths.is_dangerous_content_type.
- master's SVG download-hardening test uploads with the pre-namespacing
bare checkpoints tag, which this branch's destination validation
rejects; use model_type:checkpoints.
---------
Co-authored-by: guill <jacob.e.segal@gmail.com>
2026-07-09 17:00:08 +12:00
|
|
|
params={"include_tags": root, "name_contains": name},
|
2026-01-30 23:22:05 -08:00
|
|
|
timeout=120,
|
|
|
|
|
)
|
|
|
|
|
body = r1.json()
|
|
|
|
|
assert r1.status_code == 200, body
|
|
|
|
|
matches = [a for a in body.get("assets", []) if a.get("name") == name]
|
|
|
|
|
assert matches, "Seed asset should be visible after sync"
|
2026-05-25 11:21:35 -07:00
|
|
|
# Seed assets have no hash; exclude_none drops both keys from the response
|
|
|
|
|
assert "asset_hash" not in matches[0]
|
|
|
|
|
assert "hash" not in matches[0]
|
2026-01-30 23:22:05 -08:00
|
|
|
aid = matches[0]["id"]
|
|
|
|
|
|
|
|
|
|
r2 = http.get(f"{api_base}/api/assets/{aid}", timeout=120)
|
|
|
|
|
detail = r2.json()
|
|
|
|
|
assert r2.status_code == 200, detail
|
|
|
|
|
filename = (detail.get("user_metadata") or {}).get("filename")
|
|
|
|
|
expected = str(fp.relative_to(comfy_tmp_base_dir / root)).replace("\\", "/")
|
|
|
|
|
assert filename == expected, f"expected filename={expected}, got {filename!r}"
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
@pytest.mark.skip(reason="Requires computing hashes of files in directories to retarget cache states")
|
|
|
|
|
@pytest.mark.parametrize("root", ["input", "output"])
|
|
|
|
|
def test_metadata_filename_computed_and_updated_on_retarget(
|
|
|
|
|
root: str,
|
|
|
|
|
http: requests.Session,
|
|
|
|
|
api_base: str,
|
|
|
|
|
comfy_tmp_base_dir: Path,
|
|
|
|
|
asset_factory,
|
|
|
|
|
make_asset_bytes,
|
|
|
|
|
run_scan_and_wait,
|
|
|
|
|
):
|
|
|
|
|
"""
|
|
|
|
|
1) Ingest under {root}/unit-tests/<scope>/a/b/<name> -> filename reflects relative path.
|
|
|
|
|
2) Retarget by copying to {root}/unit-tests/<scope>/x/<new_name>, remove old file,
|
|
|
|
|
run fast pass + scan -> filename updates to new relative path.
|
|
|
|
|
"""
|
|
|
|
|
scope = f"meta-fn-{uuid.uuid4().hex[:6]}"
|
|
|
|
|
name1 = "compute_metadata_filename.png"
|
|
|
|
|
name2 = "compute_changed_metadata_filename.png"
|
|
|
|
|
data = make_asset_bytes(name1, 2100)
|
|
|
|
|
|
|
|
|
|
# Upload into nested path a/b
|
|
|
|
|
a = asset_factory(name1, [root, "unit-tests", scope, "a", "b"], {}, data)
|
|
|
|
|
aid = a["id"]
|
|
|
|
|
|
|
|
|
|
root_base = comfy_tmp_base_dir / root
|
|
|
|
|
p1 = (root_base / "unit-tests" / scope / "a" / "b" / get_asset_filename(a["asset_hash"], ".png"))
|
|
|
|
|
assert p1.exists()
|
|
|
|
|
|
|
|
|
|
# filename at ingest should be the path relative to root
|
|
|
|
|
rel1 = str(p1.relative_to(root_base)).replace("\\", "/")
|
|
|
|
|
g1 = http.get(f"{api_base}/api/assets/{aid}", timeout=120)
|
|
|
|
|
d1 = g1.json()
|
|
|
|
|
assert g1.status_code == 200, d1
|
|
|
|
|
fn1 = d1["user_metadata"].get("filename")
|
|
|
|
|
assert fn1 == rel1
|
|
|
|
|
|
|
|
|
|
# Retarget: copy to x/<name2>, remove old, then sync+scan
|
|
|
|
|
p2 = root_base / "unit-tests" / scope / "x" / name2
|
|
|
|
|
p2.parent.mkdir(parents=True, exist_ok=True)
|
|
|
|
|
p2.write_bytes(data)
|
|
|
|
|
if p1.exists():
|
|
|
|
|
p1.unlink()
|
|
|
|
|
|
|
|
|
|
trigger_sync_seed_assets(http, api_base) # seed the new path
|
|
|
|
|
run_scan_and_wait(root) # verify/hash and reconcile
|
|
|
|
|
|
|
|
|
|
# filename should now point at x/<name2>
|
|
|
|
|
rel2 = str(p2.relative_to(root_base)).replace("\\", "/")
|
|
|
|
|
g2 = http.get(f"{api_base}/api/assets/{aid}", timeout=120)
|
|
|
|
|
d2 = g2.json()
|
|
|
|
|
assert g2.status_code == 200, d2
|
|
|
|
|
fn2 = d2["user_metadata"].get("filename")
|
|
|
|
|
assert fn2 == rel2
|