Branch: refs/heads/stable-16.10.x Home: https://github.com/xwiki/xwiki-platform Commit: d4f2d1024a82b444bf4922037bb480ba06109a7a https://github.com/xwiki/xwiki-platform/commit/d4f2d1024a82b444bf4922037bb48... Author: Michael Hamann <[email protected]> Date: 2026-09-22 (Tue, 22 Sep 2026) Changed paths: M xwiki-platform-core/xwiki-platform-flamingo/xwiki-platform-flamingo-skin/xwiki-platform-flamingo-skin-test/xwiki-platform-flamingo-skin-test-pageobjects/src/main/java/org/xwiki/flamingo/skin/test/po/AttachmentsPane.java Log Message: ----------- [Misc] Wait for the HTML5 uploader before setting the file to upload AttachmentsPane#setFileToUpload only sent the file path to the file input. The upload itself is started by the change listener that the HTML5 uploader installs on that input, and the uploader is initialized asynchronously, once attachments.js has resolved the 'xwiki-upload' module through RequireJS. Opening the attachments doc extra pane only waits for the pane to be displayed, so the change event could be fired before the listener existed, in which case it was lost and no upload happened at all. This made AttachmentValidationIT#validateDisguisedAttachment fail on CI with a NoSuchElementException on .xnotification-error: the archived video shows the file sitting in the input with the submit buttons still visible, i.e. hideFormButtons() had never run. Wait for the html5upload-initialized marker that the uploader sets on the form, which is added right after the change listener is attached. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> (cherry picked from commit 521028d8ff774945a1ceec75401fba6952a863aa) Commit: 017ef4a1f8b9ba9f7aeaa590747ed97d96880a85 https://github.com/xwiki/xwiki-platform/commit/017ef4a1f8b9ba9f7aeaa590747ed... Author: Michael Hamann <[email protected]> Date: 2026-09-22 (Tue, 22 Sep 2026) Changed paths: M xwiki-platform-core/xwiki-platform-flamingo/xwiki-platform-flamingo-skin/xwiki-platform-flamingo-skin-test/xwiki-platform-flamingo-skin-test-docker/src/test/it/org/xwiki/flamingo/test/docker/SecurityCacheStressIT.java Log Message: ----------- [Misc] Don't run the security cache stress test through the browser The test raised the page load timeout to 10 minutes, but that is not the timeout it was hitting: the Selenium HTTP client gives up on the "get" command after its own read timeout of 3 minutes, and that timeout is fixed when the driver is created, so a test cannot change it. Request the rendered page over HTTP straight from the test JVM instead, where no such timeout applies. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> (cherry picked from commit cbd3bb9d446fa4fde1be25b2418d929000ced3be) Compare: https://github.com/xwiki/xwiki-platform/compare/930378daf653...017ef4a1f8b9 To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-platform/settings/notifications