chstercc opened a new pull request, #6403:
URL: https://github.com/apache/rocketmq-dashboard/pull/6403

   ### Which Issue(s) This PR Fixes
   
   - Fixes #6397
   
   ### Brief Description
   
   A query for an instance named `global` currently replaces an otherwise 
identical unscoped/legacy history record because both scopes use the same 
string sentinel. Encode history identity fields as JSON tuples, preserving 
absent instance scope separately from literal names. Apply the same encoding to 
generated entry IDs and distinguish an implicit data source from a literal 
`default` key.
   
   Existing persisted records remain readable and deduplication continues to 
use query fields, including for legacy IDs. The change is limited to history 
identity and its regression tests.
   
   ### How Did You Test This Change?
   
   - Four new scope/source collision regressions fail against the original 
implementation.
   - Added coverage for both insertion orders, persistence, repeated same-scope 
queries, legacy IDs, and IDs generated at the same timestamp.
   - `cd web && npm test`: 159 files / 1,610 tests passed.
   - `cd web && npm run lint`: passed (0 errors; 10 existing warnings).
   - `cd web && npm run build`: passed, including the license check (133 
components / 140 license files).
   - `git diff --check`: passed.
   
   ### Checklist
   
   - [x] One coherent change; unrelated modifications are not bundled in
   - [x] Commit subject follows Conventional Commits
   - [x] Regression tests added, new test names end in Test
   - [x] No new UI text or source files
   - [ ] Backend/ArchUnit tests not rerun (frontend utility only)
   
   ### AI assistance
   
   AI assistance was used to investigate the defect, implement the fix, and add 
regression tests. The diff and validation results were reviewed in this 
contribution session.
   


-- 
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]

Reply via email to