Merge '59962ffd3df' into 'master'#2037
Conversation
GitOrigin-RevId: e648389e088397b4dda9c129075e9da17a7c13ae
…ame UUID in renameCollectionAcrossDatabases (#58502) GitOrigin-RevId: 0ac60e4840c726ecd17d168676ec3982f70995a6
GitOrigin-RevId: 790fb2f60ac6a2ba5d246ebf10989c4aef90e1f7
GitOrigin-RevId: dc868a6afb4f5abc3b880c634340d6febf3c72d2
…end (#58861) GitOrigin-RevId: 2edff1d2f3fe96357be39efaf66136d09d65817a
…dexKeyPattern (#58372) GitOrigin-RevId: 703350c5d18038a41e6a2254acee63cc8d7b2f47
…icipant` without `secondaryCheckMode` (#58910) GitOrigin-RevId: 66fc367313c19eae2bd805b6ddf9e3a03abd1de0
…to QE (#58368) Co-authored-by: mongodb-sage-bot[bot] <247496174+mongodb-sage-bot[bot]@users.noreply.github.com> GitOrigin-RevId: ee20d6b6d4c2d8c781c69d0a09ca1c0b3d20be29
GitOrigin-RevId: ab4542e6102dbdcd746bc4aae7fec0454f7ffbc6
…8869) GitOrigin-RevId: 43f00637e64144792c1f7cf65adbd9fa30075605
…58520) GitOrigin-RevId: 507fcc6f66e0dce82a5c354dc39e286a2381bd34
…8717) Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> GitOrigin-RevId: 31bc7a2afeb30b1a9f7b986fcf27bace7986fd0a
… registering and executing query stats (#58713) GitOrigin-RevId: 7dc8b97b803121d9a2cd906f36d325e339dc12fe
GitOrigin-RevId: d870d6caf2aeef8d1069b379041f60de8e47b186
GitOrigin-RevId: eb056a94ae7fb73e6acc59efc2f3e03f00e1e00e
GitOrigin-RevId: 85dc3b5f6f0a6a6316f37c5b5b3ac7251a737649
…ly when it is actually being used (#58862) GitOrigin-RevId: 5cafb918ab0af723fa8b0ded4a47a066f81e7f74
… rooted $or subplanning (#58285) GitOrigin-RevId: c6a310565d4af23ec0a3e28d77fa6432d12d9ce4
…497) GitOrigin-RevId: c002a4f193f322a7c5a3ddfa39159057abbd4c44
GitOrigin-RevId: ec7e897a28d20738fd49e96ed5e80e70bcf85da4
GitOrigin-RevId: 8422d929386f5ef66e1cbb36eab0916f446e3291
GitOrigin-RevId: a32eef588c3a74ca53ddd6aae57821467b3d40c6
…no_passthrough (#58940) GitOrigin-RevId: 6014e6f610c3e135b5d196c835b22627383f09c0
… unsharded timeseries collections (#54863)" (#58866) GitOrigin-RevId: a34888454e8df0ea3a655f93a97cd48f8b964dce
… (#58876) GitOrigin-RevId: bb45495150dff57a1d8554f7599a372a91ad1358
GitOrigin-RevId: 05eeddb5f57693b792bd7c7d975343d3d666b349
GitOrigin-RevId: fd983d3cf1a16b97647a65af6afb313fdbf7bcb7
…persistent NDV stats (#58953) GitOrigin-RevId: 9a7ee59dcbdff3eaeee2e9591b26fb7287260709
…#58947) GitOrigin-RevId: 109fb9b1929c8ae64b8d050b9c6a3a44a9af0c76
GitOrigin-RevId: c5dc0fa9c1a00aa5ad6fffbeeb10864cabb177f7
…e_primary priority_ports on {A,UB}SAN to fix memory-pressure timeout (#58979)
GitOrigin-RevId: 5fc76db23a4ed3a28572abd7d8e359c76bd1bced
GitOrigin-RevId: f256faf00d5c7f79a31d35aa713206fee89007d5
…(#58951) GitOrigin-RevId: 4934735f1e1eeb90c4836ff59d261c5ef00265ab
… config (#58933) GitOrigin-RevId: 0d1f70b60392f4903418560bd298f58c47b32618
…8969) GitOrigin-RevId: bbb7492b02c862b7b6f994011d9139af07c3c543
GitOrigin-RevId: 7582750d61cf2528890a81603566971ca8aed4ec
…58851) GitOrigin-RevId: fbb8aeaf97aa27efd88edb594e39de2d832b04df
…ns (#57824) GitOrigin-RevId: 50f49d7acc4a341c9b4cead3cb40da4b6f53fb76
…th detached OpCtx (#58875) GitOrigin-RevId: a22d9e93838d6226532a4ee21b4cfc02947c0efe
…ent after hitting an exception (#58930) GitOrigin-RevId: 06814cc7fb425016b9d7300223aadae6b0b7e7d9
…s during CheckMetadataConsistencyInBackground testing (#58603) GitOrigin-RevId: 0049ffd18aa639dbc3c513d459b0e0e6cd330d94
GitOrigin-RevId: c60987a1e221093e8fa670d89baa56f177808d46
… (#58047) GitOrigin-RevId: b5ee8c05d9aa9f0622a39765c316bb493a419036
…ch mongodb-master (#59021) Co-authored-by: wt-vendoring-bot <wt-vendoring-bot@mongodb.com> GitOrigin-RevId: a65e481ab7b6437bbec2864437233ae379f94bf7
|
psmdb-bot[bot] seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
|
The Bucket (d) — flaky/environmental failure. //src/mongo/otel/traces/span:span_telemetry_context_impl_test crashed with a Segmentation fault during test startup (log shows 'Running 5 tests in 1 suites [ 0 of 1 ]' immediately followed by 'Segmentation fault (core dumped)'), with no assertion mismatch. The test and its entire linked dependency closure are byte-for-byte unchanged by this merge, so no source defect was introduced that I can fix without chasing a flake. Unresolved:
Verification steps: (1) |
|
/fast-forward |
|
Fast-forward merge completed successfully. Merged |
Merge Info
master8bdd75650937f1240aa23fc00a9ca7f95ce17b6c59962ffd3dfd37f2d5bcac7ebf3b9e196b7703cfMerge Context
Important Files Modified
src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cppsrc/mongo/db/storage/wiredtiger/wiredtiger_kv_engine_test.cppAuto-Merged Files
.bazelrcMODULE.bazel.lockREADME.third_party.mdbazel/config/BUILD.bazelbazel/resmoke/resmoke.bzlbuildscripts/resmokelib/testing/fixtures/replicaset.pysbom.jsonsrc/mongo/db/BUILD.bazelsrc/mongo/db/index_builds/BUILD.bazelsrc/mongo/db/repl/replication_coordinator_impl.cppsrc/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cppsrc/mongo/db/storage/wiredtiger/wiredtiger_util.cppsrc/mongo/db/storage/wiredtiger/wiredtiger_util_test.cppsrc/third_party/wiredtiger/src/include/wiredtiger.h.inMerged with strategy: ort
Show details
59962ffd3dfd37f2d5bcac7ebf3b9e196b7703cfff622631a9f8bbb22c0548202b0739203fbd86fc47881b6e3e09c17c093dbe84e13263fc548062c04299f64d15be03e2c40a47237d434bb059d7b6bfb638b6e8fe246a96dff7721712dc4a44f7ba1d8c6f1203062f47a0a23ca0ec9a6d5af8d5e640bed42481269cc9acb7393930f37d5abded88b14f1d8c0ec4a35d62136cf046ca77a88526a86d29e1af679eda0508e2e242c3b153af4a84ba3a6ca89355478e3581e49aa99bebd07ed97cb4630efe5b1f3c3c310ea4c7f46b027f3b158fe309f0c4145fd7133ca62edd9cb1ba3f7116fb52532ad3e05795e5ca8dfd864f3a9f70cf1b804c2ac7c8294e021d61b6c0bc39b3face3f567c79259d73789cf3c07c22ac7f69ce480c43f7e6e120ca79c693aee956c31ea9a2590aa79cad29dddccc44c8b34feff4b2d3f5d3cbb19ac578ec8403b42538a7f41b97612898a4d25fac7eeb58aa41c3d9cf15cc9c4a9e5d9d696eca4f7a8988a9914bbba381209293a3a8233dc9ed5c90adef6f5d87a32f57714b4e9e65793c7d1da3b8afe9f67ddd6b530fadb3b9dac9bf1679cbfc438bba509c7028d5db0b725ff6978fab8102415a8af8b8bd4ad7199b07880ff1287084fc7ecc907713df311b48c97c9923853d5dc06ced74d903ff04763d7eaa6797c1d4ac07293a355b78e7ce806dcb58a6aaef5dcb48743196c2a2b5d00c905ca4529970bea7ab110e93392d95cdb1faf6bd35ade062b4fa968c3f36242d8cebc070146fa4cd28fd81ce05ef98e13609f167530f3de3216e357d0f23223bc817c2e08d14e838febc4ddc4e327e9c76181c44c0f5df4c163c929d229e7063e40af39c138e0b076b1cbe1f204ce9c690fd58fed708764a6365f9a142452836e5f837c926e9b2c4b2130080f320eb56ba71cdf54c4a0b729f055e198afece70b640158145dfaea066563216014dcab8d1cd258f821b66fdc7c929d640e712a1d859e7cf804b1094a09e5c37406f85eaddc7c64b6d9d65ee9eecb7706c3e147f06641b1ddeaf4ed528e78f822c4c1e8d8d45adc6709d9bc82bc37e940fd004f6a959b234fc2e11943ceae1054543659ad628ec4957a1dc4f5743445b9139c5d7a1a4175b1dc3ba82b742d852b165a86aa34e079a0e534fd45bf6408e6ad73dec50cfe6dd5c217de9eca223376adbf92633f732e5d24002ec748e43037cedc78aab4bf405c13e675590c5c805347974fcd2325f31c409a9e9df54ceaf798edd39441640b3d30d60eb272791e19bb3bae511bf69ae30cfc3269a5a91c52f8ededa23b160b1240284f78984ba7c0a2992101e4b602f96d53adf902b95d2896ce4d329dbdf776db4be217e5cd05675e3b4ebbcbd2f8c410e418c027fdf96864f831995c1dfd7370d88f35213eda553abe834c7ec24020ae4087ded28255eBSONObjMaxUserSizein registering and executing query stats (#58713)256f0646330d9812170a79b9912626a46929ec2f569ce042a38b6b98cbaf324056993b3314c27c11e6bb96d7d10a8c4219f509c32f2008586723fe32dc3d315a92366826702cec74d488f8f4c6fc5fcfd1bf655bff327b89d8dd780501dcd8b05363c8706bbc74144b92824782eef0d5630f9d97736e6e27_shardsvrCheckMetadataConsistencyParticipantwithoutsecondaryCheckMode(#58910)59907c1f34efcc4a47863834415a50349c082695a09de5fb270532ba78767879cf4efaf136610d384d73d13d16a6140a54a15139a9ef3af1d4b747b9b8a093a3188f1e3660353ee64fd965c85412dfe2e9da4562ce83695da3e50f3be4056208cb160c4c2a62f06250c4476c7600fce907efb8956a003ff8Merge Description
Summary
Upstream merge (base c48b8d1 → merge 59962ff) into the PSMDB master fork branch. The main functional change reworks how WiredTiger statistics errors are classified when computing index/ident storage sizes: getStatisticsValue now routes cursor-open failures through wtRCToStatus() (yielding NoSuchKey/BadValue/ObjectIsBusy instead of the old blanket CursorNotFound), and the KV engine and util callers were updated to treat NoSuchKey as "missing file → 0", ObjectIsBusy as a transient/retryable busy state, and to surface other errors. A new WTIndexStorageSizeReturnBusy failpoint was added to simulate the busy path. Other changes are build/infrastructure: LLVM source-based coverage plumbing in the Bazel resmoke rule, a coverage remote-download tweak in .bazelrc, a new rhel10_ppc64le_gcc_linkstatic config_setting_group, a valgrind.h version relabel (commit SHA → 3.17.0), BUILD.bazel dependency/source list adjustments, a resmoke replica-set heartbeat interval bump, removal of an unused constant, and WiredTiger public-header documentation-comment updates. sbom.json and MODULE.bazel.lock also carry the routine SBOM/lockfile refreshes.
Auto-Merged Files
.bazelrccoverage --remote_download_outputs=allwithcoverage --remote_download_regex=.*coverage.*\.dat$(plus an explanatory comment) so that under remote execution only coverage report files are pulled back rather than every instrumented output.MODULE.bazel.lockbzlTransitiveDigestvalues for the bazel_features_deps and setup_mongo_python_toolchains module extensions change from IrYH+a7... to hKYNVSGE.... This file is a merge conflict (both modified) and must be regenerated per the MODULE.bazel.lock conflict hint.README.third_party.mdbazel/config/BUILD.bazelrhel10_ppc64le_gcc_linkstaticselects.config_setting_group matching linux + ppc64le + gcc + rhel10 + linkstatic_enabled.bazel/resmoke/resmoke.bzlbuildscripts/resmokelib/testing/fixtures/replicaset.pyheartbeatIntervalMillissetting from 1000 to 1800.sbom.jsonversionandmetadata.timestamp, bumps the Endor Labs tool service version (v1.7.1053 → v1.7.1060), and relabels the valgrind component version/bom-ref/purl/dependency refs from the commit SHA to 3.17.0. This file is a merge conflict (both modified) and must be resolved per the sbom.json conflict hint (keep Percona's supplier URL and remove the metadata.tools section).src/mongo/db/BUILD.bazelifr_context_decoration.cppto the source list of the affected mongo_cc_library target.src/mongo/db/index_builds/BUILD.bazel//src/mongo/db/index_builds/primary_driven:tearable_side_write_redo_statedependency from a mongo_cc_library target.src/mongo/db/repl/replication_coordinator_impl.cppkQuiesceModeShutdownMessage.src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cppWTIndexStorageSizeReturnBusyfailpoint and reworks the error handling in getIndexStorageSize: the failpoint can inject an ObjectIsBusy status; an ObjectIsBusy status is now returned to the caller for retry; a NoSuchKey status is treated as "no on-disk checkpoint yet" and skipped (continue). The previous CursorNotFound + getMetadata()==NoSuchKey ambiguity check was replaced by this direct status-code handling.src/mongo/db/storage/wiredtiger/wiredtiger_util.cppsrc/mongo/db/storage/wiredtiger/wiredtiger_util_test.cppsrc/third_party/wiredtiger/src/include/wiredtiger.h.inoverwriteconfig description to document layered-follower WT_CURSOR::remove tombstone behavior, and adds/clarifies @param and field comments on the WT_PAGE_LOG callbacks and the page-log args structs (complete_checkpoint, get_complete_checkpoint, put/get/discard args, and cache_put/has/del/available).Review Notes
The provided merge_commit (59962ff) is the incoming upstream tip; its sbom.json still shows MongoDB's supplier URL (https://mongodb.com) and retains the metadata.tools (Endor Labs) section. Both MODULE.bazel.lock and sbom.json are 'both modified' conflicts and require the standard Percona resolution: for sbom.json keep Percona's supplier url (https://percona.com) and remove the metadata.tools section (serialNumber/version are release-time concerns); for MODULE.bazel.lock remove conflict markers and regenerate with
bazel query //... >/dev/nulllast. The substantive change to double-check is the WiredTiger error-code reclassification (CursorNotFound → NoSuchKey/BadValue/ObjectIsBusy) since callers now branch on the new codes — verify no other PSMDB callers of getStatisticsValue/getIdentSize still rely on CursorNotFound. All C++ diffs applied cleanly without conflict markers; verify a build/unit-test run of the wiredtiger storage tests.Agent Stats
Agent: claude_cli (version 2.1.215 (Claude Code))
Conflict Context
c48b8d1873efa5297e9d4bca894df85a4e1bffa48bdd75650937f1240aa23fc00a9ca7f95ce17b6c59962ffd3dfd37f2d5bcac7ebf3b9e196b7703cfConflicted Files
MODULE.bazel.locksbom.jsonConflict details
Their Commits
MODULE.bazel.lock69ce480c43f7e6e120ca79c693aee956c31ea9a2sbom.jsone5f837c926e9b2c4b2130080f320eb56ba71cdf5Solutions
Solution 1
Summary
Resolve conflicts for merge commit '59962ffd3df' into master
By: psmdb-bot[bot] <2942401+psmdb-bot[bot]@users.noreply.github.com>
Resolved Files
MODULE.bazel.locksbom.jsonUnresolved Files
All conflicts have been resolved.
Modified Files
No additional files were modified.
Review Notes
Resolved conflicts in sbom.json and MODULE.bazel.lock. For sbom.json,
kept Percona's serialNumber/version and supplier URL
(https://percona.com) and removed the MongoDB-generated metadata.tools
section per the conflict hints. For MODULE.bazel.lock, removed the
conflict markers by accepting one side and regenerated the file with
'bazel query //...' as instructed.
Resolved:
sbom.json
MODULE.bazel.lock
Note: commit created by mergai
note created with mergai 0.1.dev1+g07faa5a05