imbajin commented on PR #391:
URL: https://github.com/apache/hugegraph-ai/pull/391#issuecomment-6718136011

   Follow-up at head `066a796247c5fd8afaa31f3178ad64a42d829ec2`: the eight 
previously reported threads have been addressed and individually replied to. 
This does not establish that the entire stacked PR has been reviewed or is 
ready to merge.
   
   Remaining confirmed boundaries:
   
   - Document IDs are derived from the relative path and content without a 
store identifier. Two stores containing the same relative path and bytes can 
therefore attempt to insert the same global document ID. Changing existing IDs 
requires a compatibility/migration design; this has not been fixed here.
   - Incorrect historical attempt/run associations created before this fix are 
not backfilled; old action revision snapshots also do not gain derived fields 
automatically.
   - For the outbox migration, stop the old worker before upgrading and use one 
service process per database. The first dispatch after startup reconciles 
historical receipts once.
   - This PR targets `apache:ontogeny` and depends on #380, which remains open. 
Recheck the base and complete diff after that dependency changes. The CI for 
this exact head is still running.
   
   Validation: 156 targeted backend tests passed and 4 PostgreSQL-dependent 
tests were skipped in that run; a separate run against a real PostgreSQL 16 
instance passed 12 outbox/lifespan tests, and the frontend access tests passed 
(19 tests). The combined backend run emitted three aiosqlite event-loop-closed 
warnings. No production deployment or old-data migration was validated.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to