MarioJGMsoft

This commit performs **telemetry optimization** within the **container runtime's summary generation** process. It **reduces the volume of telemetry data** by modifying the `packages/runtime/container-runtime/src/summary/orderedClientElection.ts` file. Specifically, the `_electInteractiveClient` and `_electParent` functions are updated to no longer force-send the `InteractiveClientElected` and `ParentElected` events, leveraging an existing `forceSend` parameter to filter out unnecessary transmissions. This **maintenance** change improves the efficiency of the **telemetry system** by reducing noise and data volume.

This commit **fixes a formatting error** within the **development container configuration** by **removing a trailing comma** from the extensions list in the `.devcontainer/devcontainer.json` file. This **maintenance fix** addresses a syntax issue introduced in a previous change, ensuring the configuration file remains valid. The change is a **style correction** that improves the robustness of the **development environment setup** for users leveraging **Dev Containers**, preventing potential parsing errors without altering any functional aspects.

This commit introduces a **test maintenance** change to improve pipeline stability by addressing **known test flakiness**. It **conditionally skips** a specific **end-to-end presence test** within the `packages/service-clients/end-to-end-tests/azure-client` module. The test is bypassed when the number of clients exceeds 50, as this scenario frequently leads to intermittent failures in the Service Clients pipelines due to network or service instability. This **temporary workaround** prevents pipeline disruptions, allowing other tests to pass reliably while the underlying flakiness issue (tracked by AB#59980) is investigated.

This commit **reverts** the previous introduction of **incremental summary performance tests** within the `tree` package's `forest-summary` feature. This **rollback** is a critical **maintenance** action, addressing a severe **performance regression** that caused the project's CI benchmarks pipeline to consistently timeout. By removing the problematic test suite, which involved refactoring test setups and utilities in `forestSummarizer.spec.ts` and `incrementalSummaryBuilder.spec.ts`, the commit restores stability to the automated performance validation system.

This commit **disables** the **`Forest Summarizer benchmarks`** test suite within the **`@fluidframework/tree`** package by adding `.skip` to its `describe` block in `forestSummarizer.bench.ts`. This **maintenance** action is a **temporary fix** to prevent **CI/CD pipeline failures**, as the recently introduced performance test was suspected of causing build breaks. Consequently, performance monitoring for the `ForestSummarizer` component is temporarily suspended until the underlying issue is resolved.

This commit **fixes flaky end-to-end tests** within the **migration shim's reconnect scenarios** by addressing timing issues in Fluid Runtime Services (FRS). It specifically removes the `await provider.ensureSynchronized()` call from two test cases in `packages/test/test-end-to-end-tests/src/test/migration-shim/reconnect.spec.ts`. Since these tests only validate the local state of `container2`, this **maintenance change** prevents timeouts and significantly improves the overall reliability of the test suite.

This commit implements a **maintenance** change by **conditionally skipping a flaky end-to-end test** within the `packages/test/test-end-to-end-tests` suite. Specifically, the test 'Create data store with group id Non-Compat, Can create loadingGroupId' in `initialSequenceNumberAndStashedOps.spec.ts` is now skipped when using the `routerlicious` driver. This **workaround** addresses a **server-side bug** that causes the container to get stuck in an 'EstablishingConnection' state, leading to test timeouts and CI failures. The test will be re-enabled once the underlying server issue is resolved, preventing unnecessary CI pipeline failures.

This commit **improves the reliability** of dynamic module loading within the **ODSP driver** by addressing intermittent "Loading chunk 883 failed" errors. It implements **retry logic** with a 50ms delay for the dynamic import of `createNewModule.js` within the `useCreateNewModule` function. This **bug fix** enhances the robustness of the driver's **createNewModule functionality**, preventing failures caused by transient network or loading issues and ensuring a more stable user experience.

This commit **enhances telemetry collection** for **real service tests** by **disabling throttling** and **increasing the after-flush delay** within the test logger configuration. Specifically, modifications in `packages/test/mocha-test-setup/src/mochaHooks.ts` ensure that more comprehensive telemetry data is captured during Mocha test runs. This **instrumentation improvement** also extends the `afterAll` hook timeout to guarantee all collected telemetry is properly flushed. The change aims to provide better insights into test execution by allowing the system to receive a higher volume of test telemetry.

build: Update tar-fs in lockfiles to address CVE (#25098)

This commit delivers a **bug fix** to resolve an issue causing the instantiation of **two session loggers** within the test pipeline. It specifically corrects the module path resolution for the test logger within the **test setup configuration** in `packages/test/mocha-test-setup/mocharc-common.cjs`. By modifying the `getFluidTestMochaConfig` function to use `path.join` instead of `require.resolve`, this change prevents the erroneous double logger creation, ensuring proper and singular logging during **test execution**.

This commit **refactors** the **test telemetry setup** to address a **bug** where not all test results were being reflected in the portal. Specifically, it replaces the `getTestLogger` function with `createTestLogger` in `packages/test/mocha-test-setup/src/mochaHooks.ts` and introduces an `afterAll` hook to ensure proper logger flushing. Concurrently, it **updates** the environment variable `FLUID_TEST_LOGGER_PKG_PATH` to `FLUID_TEST_LOGGER_PKG_SPECIFIER` across `packages/test/mocha-test-setup/mocharc-common.cjs` and several **CI/CD pipelines** (e.g., `test-perf-benchmarks.yml`, `test-real-service.yml`, `test-service-clients.yml`). This **maintenance** change standardizes pipeline configurations and improves the reliability of **test result reporting**.

This commit introduces a **new feature** to the **ODSP driver** by adding the `isRedemptionNonDurable` property and header. This change is essential for enabling **temporal access** to documents for specific user types when redeeming share links. It updates the `odsp-driver-definitions` and `odsp-driver` packages, modifying interfaces like `ShareLinkInfoType` and `ISharingLinkHeader` to support this new flag. The core logic in `fetchSnapshot.ts` and `odspDriverUrlResolverForShareLink.ts` is updated to correctly handle `isRedemptionNonDurable` during **share link redemption** and **snapshot fetching**. This ensures proper authorization and access control for shared documents, with new tests verifying the functionality.

This commit **resolves an issue in the internal build-client pipelines** to ensure reliable artifact publishing to ARROW. It introduces a new `shouldShip` parameter within the `tools/pipelines/build-client.yml` definition and its `tools/pipelines/templates/build-npm-client-package.yml` template. This parameter explicitly controls artifact uploading based on the release type, **guaranteeing consistent delivery of build artifacts**. This **maintenance update** ensures that all necessary artifacts are properly shipped for downstream consumption.

This commit **reverts** the deprecation of the `containerPackageInfo` parameter within the `createOdspCreateContainerRequest` function in the **ODSP driver**. It **restores** the parameter's presence in the API signature and removes the previously added deprecated overload and associated comments. This **maintenance** change ensures that existing partner code relying on the `containerPackageInfo` parameter continues to function without modification. By undoing the planned deprecation, this commit prevents a potential **breaking change** for consumers of the **ODSP driver's container creation API**.

This commit **fixes a bug** in the **CI/CD pipeline** responsible for **internal build-client packages**, ensuring that **artifacts are correctly sent to ARROW**. The **pipeline maintenance** involves **simplifying the conditional logic** within the `tools/pipelines/templates/build-npm-client-package.yml` template, which determines when artifacts should be shipped. This change directly impacts the **artifact management** process for client-side NPM packages, improving the reliability and availability of build outputs for downstream consumption.

This commit performs a **maintenance API removal** by eliminating the **`getContainerPackageInfo`** method from the **`IContainer`** interface within the **`container-loader`** package. This action completes a deprecation cycle, removing a non-generic API that was previously marked for removal. The change ensures a cleaner and more consistent API surface for the `container-loader` layer, impacting any consumers who might have relied on this specific public method. A changeset entry documents this significant API change, reflecting the final step in deprecating and removing this public API.

This commit **enhances the build pipeline** by updating the internal build-client packages to send generated artifacts to the **ARROW service connection**. It modifies the `tools/pipelines/templates/build-npm-client-package.yml` template, introducing conditional logic to publish these artifacts. This **new capability** ensures that both release and pre-release builds correctly transfer their outputs, improving the availability and management of build artifacts. The change primarily affects the **CI/CD infrastructure** for client-side NPM packages, streamlining the artifact publishing process.

This commit **adds a deprecation remark** to the JSDoc of the `Loader` class within `packages/loader/container-loader/src/loader.ts`. This **documentation update** serves as a warning to consumers that the `Loader` class should no longer be used, encouraging a transition to free-form functions instead. It is a **maintenance step** towards eventually making the `Loader` class internal, without formally deprecating it via an `@deprecated` tag yet. This change impacts users of the **Fluid Framework loader** by guiding them away from an older API and preparing for future internalizations.

This commit **deprecates** the `containerPackageInfo` parameter in the `createOdspCreateContainerRequest` function within the **`odsp-driver`** package. This **API change** guides consumers to use the URL resolver for specifying `containerPackageName`, aligning with a new preferred pattern. It involves **refactoring** the function signature to mark the parameter as deprecated and updating API reports. Downstream, packages like `odsp-client` and `test-drivers` are updated with lint suppressions, anticipating a **future breaking change** where this parameter will be removed entirely in release 2.40.