Discourse/discourse
Discourse/discourse
0
0
Fork 0
mirror of https://github.com/discourse/discourse.git synced 2026-08-12 05:37:26 +08:00
Code Packages Activity Actions
discourse/spec
History
Exact
autoresearch 3631eaa999 Revert "experiment[219]: Switch The Core System Job's Headless Browser From Full Chromium's "New Headless" Mode (Pinned By channel: :chromium Since The May-2025 Chrome-To-Chromium Migration) To Playwright's Purpose-Built chromium-headless-shell Of The Identical Build Revision 1217, Installed By A New Core-Scoped Workflow Step Beside The Image's --no-shell Bake And Selected By A Binary-Availability Check In SystemDrivers So Dev Boxes, Plugin/Theme System Jobs, And Headful Debugging Keep Full Chromium Byte-Identically (PLAYWRIGHT_FULL_CHROMIUM=1 Restores It Anywhere), Because Interleaved A/B On create_invite Measures The Shell At -2.0% Wall On All Four Pairs (15.84 vs 16.17s Median) And ~8% Less Browser CPU (17.8/17.8/18.6 vs 19.3/19.6s Plus A 27.5s Control Outlier) With Two Fewer Crashpad Processes Per Browser Across The 10 CPU-Saturated Workers — Shipped After This Session's Deep Falsification Of The Bigger Compile-Cache Family: Chromium Never Code-Caches The Production Build's ES-Module Bundles At Any Level (Persistent-Profile Disk Cache Consumed Only 168KB Of Classic Scripts After 9 Loads, Same-Tab Same-Isolate Re-Navigation Still Recompiles ~400-600ms CPU Every Round), Killing The addCompilationCache/Persistent-Context/Kept-Page-CPU Leads And Retroactively Explaining iter-213/217's Renderer-Reuse Wash — Validated Green On The Shipping Bytes: 152/152 Ten-File 4-Worker turbo_rspec With Complete 258-Entry Runtime Log, 62/62 Social Auth Serial Through The Second Driver Connection, 29/29 Seed-5309 Five-Class CI=1 Basket, 51/51 Risky-API Specs (WebAuthn CDP, CSV Downloads, Clipboard, webm Video Upload, Canvas/Lightbox), And The Kill Switch Verified Relaunching Full Chrome Plus Crashpad" 
This reverts commit 547b04d31a.
2026-06-12 03:08:13 +00:00
..
db FIX: Prevent backslash accumulation in upload markdown labels (#39461) 2026-06-03 18:10:38 +02:00
fabricators FEATURE: Add Search section to the redesigned admin dashboard (#40779) 2026-06-11 12:25:10 +08:00
fixtures DEV: Allow plugins to register admin-panel-specific CSS (#40345) 2026-05-28 11:03:38 +01:00
generator DEV: Enable Rails/FilePath rubocop rule (#40097) 2026-05-19 19:07:54 +02:00
helpers DEV: Replace JS build system with Rolldown (#35963) 2026-05-29 11:11:55 +01:00
import_export
initializers Revert "FEATURE: discourse-workflows (#39704)" (#40366) 2026-05-28 13:59:42 +01:00
integration FIX: Correctly rescue failed embed_mode parsing (#40298) 2026-05-26 15:29:48 +01:00
integrity DEV: Make upcoming change CSS classes opt-in (#40669) 2026-06-10 12:12:58 +10:00
jobs FIX: Match webhook-related messagebus audience to controller audience (#40693) 2026-06-09 18:22:26 +01:00
lib DEV: move desktop sidebar-section CSS to common, remove desktop css index (#40803) 2026-06-11 15:09:09 -04:00
mailers FIX: allow custom email sender name via translation overrides (#40674) 2026-06-09 14:03:03 +04:00
migrations FEATURE: Exclude small actions from topic counters and unread tracking (#40481) 2026-06-08 08:03:55 +02:00
models FIX: Stat type grouping (#40783) 2026-06-11 16:59:33 +10:00
multisite DEV: Enable Rails/FilePath rubocop rule (#40097) 2026-05-19 19:07:54 +02:00
queries/reports FEATURE: Activity by category section of the new dashboard's engagement section (#40227) 2026-05-22 13:10:38 +08:00
requests DEV: Check featured topic visibility in CurrentUserSerializer (#40755) 2026-06-11 10:38:00 -03:00
script DEV: Automatic upcoming change status report and PR creation (#40291) 2026-06-11 15:19:15 +10:00
serializers FEATURE: User API key device authorization flow (#40189) 2026-06-10 16:09:44 -04:00
services FEATURE: Warn admins when Content Security Policy is disabled (#40791) 2026-06-11 11:34:37 +01:00
support Revert "experiment[219]: Switch The Core System Job's Headless Browser From Full Chromium's "New Headless" Mode (Pinned By channel: :chromium Since The May-2025 Chrome-To-Chromium Migration) To Playwright's Purpose-Built chromium-headless-shell Of The Identical Build Revision 1217, Installed By A New Core-Scoped Workflow Step Beside The Image's --no-shell Bake And Selected By A Binary-Availability Check In SystemDrivers So Dev Boxes, Plugin/Theme System Jobs, And Headful Debugging Keep Full Chromium Byte-Identically (PLAYWRIGHT_FULL_CHROMIUM=1 Restores It Anywhere), Because Interleaved A/B On create_invite Measures The Shell At -2.0% Wall On All Four Pairs (15.84 vs 16.17s Median) And ~8% Less Browser CPU (17.8/17.8/18.6 vs 19.3/19.6s Plus A 27.5s Control Outlier) With Two Fewer Crashpad Processes Per Browser Across The 10 CPU-Saturated Workers — Shipped After This Session's Deep Falsification Of The Bigger Compile-Cache Family: Chromium Never Code-Caches The Production Build's ES-Module Bundles At Any Level (Persistent-Profile Disk Cache Consumed Only 168KB Of Classic Scripts After 9 Loads, Same-Tab Same-Isolate Re-Navigation Still Recompiles ~400-600ms CPU Every Round), Killing The addCompilationCache/Persistent-Context/Kept-Page-CPU Leads And Retroactively Explaining iter-213/217's Renderer-Reuse Wash — Validated Green On The Shipping Bytes: 152/152 Ten-File 4-Worker turbo_rspec With Complete 258-Entry Runtime Log, 62/62 Social Auth Serial Through The Second Driver Connection, 29/29 Seed-5309 Five-Class CI=1 Basket, 51/51 Risky-API Specs (WebAuthn CDP, CSV Downloads, Clipboard, webm Video Upload, Canvas/Lightbox), And The Kill Switch Verified Relaunching Full Chrome Plus Crashpad" 2026-06-12 03:08:13 +00:00
system experiment[216]: Re-Land The Never-CI-Falsified Six-Mechanism Stack On The Rebased Base (capyq + IPC Fold + MiniRacer GC No-Op + Race-Fixed Runtime Split + Stable-Wait Skip + Avatar Stub + Honest Content-Keyed Digests, Atop The iter-199 Promoted Layer Of Production Ember Build + Vendored-Driver Soft Context Reset + Rack become.json sign_in That The Rebase Replay Dropped Along With Every Other Patch From iter-146 Onward) By Materializing git merge-tree's Clean Auto-Merge Of iter-215's Measured Sha 1a086e06cb With New Base b5ba10eb5f And Byte-Verifying Every Path Against The Merge Tree, Because iter-215's Three Green Draws (401/437/466, Run-1 The Best In Loop History) Were pull_request Merge-Commit Runs That Already Tested Exactly This Composition — Stack Merged With Main's Spec-Infra Restructure (SystemDrivers, MessageBusTestSync, Extracted Helpers) — Modulo Only Two Commits Outside The Core System Job (Migrations Tooling + discourse-ai Plugin Under LOAD_PLUGINS=0), With All Five 3-Way Merge Points Auto-Merged And Hand-Reviewed, origin/main Verified Still At The New Base So PR Merge Runs Work Again (The Killed Prior-216 push: Trigger Intentionally Not Re-Landed), And Re-Validated Green On The Shipping Bytes: 63/63 Five-Class Seed-5309 Basket, 8/8 Locale Defined-Order, 62/62 Social Auth Through The Wrapper's Second Driver Connection, And 131/131 4-Worker turbo_rspec With A Complete 258-Entry Parent-Merged Runtime Log 2026-06-12 01:09:22 +00:00
tasks DEV: better multisite suppport for migrate gifs (#40792) 2026-06-11 17:51:27 +04:00
views
rails_helper.rb experiment[216]: Re-Land The Never-CI-Falsified Six-Mechanism Stack On The Rebased Base (capyq + IPC Fold + MiniRacer GC No-Op + Race-Fixed Runtime Split + Stable-Wait Skip + Avatar Stub + Honest Content-Keyed Digests, Atop The iter-199 Promoted Layer Of Production Ember Build + Vendored-Driver Soft Context Reset + Rack become.json sign_in That The Rebase Replay Dropped Along With Every Other Patch From iter-146 Onward) By Materializing git merge-tree's Clean Auto-Merge Of iter-215's Measured Sha 1a086e06cb With New Base b5ba10eb5f And Byte-Verifying Every Path Against The Merge Tree, Because iter-215's Three Green Draws (401/437/466, Run-1 The Best In Loop History) Were pull_request Merge-Commit Runs That Already Tested Exactly This Composition — Stack Merged With Main's Spec-Infra Restructure (SystemDrivers, MessageBusTestSync, Extracted Helpers) — Modulo Only Two Commits Outside The Core System Job (Migrations Tooling + discourse-ai Plugin Under LOAD_PLUGINS=0), With All Five 3-Way Merge Points Auto-Merged And Hand-Reviewed, origin/main Verified Still At The New Base So PR Merge Runs Work Again (The Killed Prior-216 push: Trigger Intentionally Not Re-Landed), And Re-Validated Green On The Shipping Bytes: 63/63 Five-Class Seed-5309 Basket, 8/8 Locale Defined-Order, 62/62 Social Auth Through The Wrapper's Second Driver Connection, And 131/131 4-Worker turbo_rspec With A Complete 258-Entry Parent-Merged Runtime Log 2026-06-12 01:09:22 +00:00
regenerate_swagger_docs
swagger_helper.rb