Caideyipi opened a new pull request, #19112:
URL: https://github.com/apache/iotdb/pull/19112

   `assertDataAlwaysOnEnv` returned after configuring `failFast`, so its query 
and assertions never ran. Restore immediate polling throughout the requested 
observation period, and fail on the first mismatch. Correct the dormant 
schema-only query headers and user/privilege result expectations, and wait for 
asynchronous permission propagation.
   
   Scoped backport of the continuous-assertion changes from #18899, commit 
`c9c16af42f696eb9fcecf287704c7825d2524e2c`, onto `dev/1.3` at 
`c0811e54d01c1f4480d10506930c44d06cfb12e6`.
   
   The 1.3 adaptation retains its single tree-model helper, `User` and `Path` 
columns, and existing privilege names. Applicable helper regression tests use 
the tree-model categories. The table-only APIs and independent 
deletion/status-polling changes from #18899 are outside this scoped backport. 
The later slow-query timing change in #19095 remains a separate follow-up.
   
   Validation on JDK 17:
   
   - Spotless passed.
   - Rebuilt the matching TsFile revision 
(`96bf5c0a99308454da66448ec62930ede9481f44`) and the required IoTDB reactor 
modules from clean source; test-node packaging passed.
   - Both new regression tests failed against the original helper: the 
observation returned before one second, and an incorrect result header raised 
no assertion.
   - Both new regression tests passed with the fix under `ClusterIT`.
   - Four affected Pipe tests passed under `MultiClusterIT`: schema-only 
inclusion, authentication exclusion, authentication inclusion with a path 
pattern, and historical authentication inclusion.
   
   The full integration suite was not run. The two existing ignored 
multi/exclusion-pattern scenarios remain ignored.
   


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