Repository navigation
Send application logs to stderr across Server deployment paths - #623
Conversation
|
Exact The corrected isolation policy and all 72 existing controls pass locally; shell syntax and diff checks pass. No policy, assertion, threshold or native/shared source is relaxed. Fresh exact-head gates are required; neither failed original is a pass. |
|
CI correction: I cancelled current Server Perf 39697978242 as optional, which also failed its source-qualification aggregate because both bounded-growth and polling-cache jobs were cancelled. That classification was mistaken for the intended Dockerfile qualification route. Attempt 1 remains cancelled/failed, not passed. One exact-head attempt 2 is now submitted at unchanged |
|
The Current source |
|
|
Main has advanced to The only merge conflicts were the unpublished chart source version. The combined release retains Server 2.11.0 / chart 0.3.0 and includes the logging change in its chart notes. Native tree, shared runner and frozen fixtures match main exactly. Source metadata synchronization and all 28 Helm controls pass locally; the test's OCI message is mocked, not publication. This PR's exact |



Refs #618. Keep that issue open until actual produced-image and chart acceptance.
Delivery is incorporated into the current Server 2.11 candidate #564 at
aefb8698efor fresh combined qualification. This PR will close as delivered after that merge; its unpublished intermediate chart 0.2.4 is not released. See the integration receipt below for exact source identity and preserved original results.Change
Default image, raw Kubernetes and Helm logging to
LOG_CHANNEL=stderr; preserve explicit channel overrides and severity. DocumentLOG_STDERR_FORMATTER=Monolog\Formatter\JsonFormatterand remove the unusedDW_LOG_FORMATexample. Chart source metadata advances to 0.2.4 because published 0.2.3 is immutable.Normal publication and recovery of releases containing the acceptance helper require actual API, worker and scheduler logging checks before chart publication. Older immutable releases retain their historical recovery contract. Standard job-scoped labels and tolerant
always()deletion cover partial setup/cancellation; the pre-bootstrap container is stopped and renamed before replacement. Recovery requires the complete verification job to succeed.Evidence and limits
446ab3bbff97deabb8c1c4dbb5dbf2361063a2013a0b00366b5dbc67b4b0a3c4fails six stderr checks; explicit file logging and severity filtering pass. This older baseline is not attributed to 2.10.1.LOG_CHANNEL=stderrpasses all eight real-process checks. A foreign-labelled volume is refused before bootstrap and preserved. These do not qualify a newly built source image. The earlier seeders-hidden-by-bind setup remains unsuccessful.cc4dba7d7bcd5250bf3856cf09a904edc0d06155, wholeb1b078346511e6bdcaf2f445c50939d4cba07334, integrates exact Security mainfbef60962without altering its conformance proxy/native/shared changes. The net logging diff remains scoped to 16 files.17f15b114Sonar API review found zero open/confirmed issues and three explicitly accepted serial-I/O recommendations. No profile or threshold relaxation and no carried whole-tree pass.b0e425144. Perf attempt 1 was mistakenly cancelled and its aggregate failed; unchanged attempt 2 remains its own17f15b114run. Current-head normal checks remain independent.The final protected release must exercise its actual produced image. This PR publishes no new Server image/chart by itself; #564 supplies the subsequent release/consumer follow-through. Website #352 is delivered and actually verified on all eight language pages (publishing 39697387144, Pages 39698271387). All local prototype/browser/lint resources and raw outputs are removed; only pushed active source remains.