Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add driver type information in service-client telemetry #22951

Draft
wants to merge 13 commits into
base: main
Choose a base branch
from

Conversation

sonalideshpandemsft
Copy link
Contributor

This change adds driver, driverEndpointName and testVariant information to service-client telemetry. Rest of the field such as clientType, loaderId and containerId are not displayed as part of Test_start and Test_end event name

ADO Work Item

@github-actions github-actions bot added the base: main PRs targeted against main branch label Oct 31, 2024
Updates website build to no longer dynamically generate
`fallback/index.js`. Instead, the redirects are hard-coded in
`fallback/routes.js`.

This work is in preparation for the Docusaurus migration.


[AB#19990](https://dev.azure.com/fluidframework/235294da-091d-4c29-84fc-cdfc3d90890b/_workitems/edit/19990)
Copy link
Collaborator

@msfluid-bot msfluid-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Coverage Summary

↑ packages.dds.tree.src.simple-tree:
Line Coverage Change: No change    Branch Coverage Change: 0.01%
Metric NameBaseline coveragePR coverageCoverage Diff
Branch Coverage 93.33% 93.34% ↑ 0.01%
Line Coverage 97.10% 97.10% → No change
↑ packages.dds.tree.src.shared-tree:
Line Coverage Change: No change    Branch Coverage Change: 0.03%
Metric NameBaseline coveragePR coverageCoverage Diff
Branch Coverage 91.34% 91.37% ↑ 0.03%
Line Coverage 97.44% 97.44% → No change
↑ packages.dds.tree.src.simple-tree.api:
Line Coverage Change: No change    Branch Coverage Change: 0.04%
Metric NameBaseline coveragePR coverageCoverage Diff
Branch Coverage 86.49% 86.53% ↑ 0.04%
Line Coverage 81.77% 81.77% → No change

Baseline commit: e432720
Baseline build: 303572
Happy Coding!!

Code coverage comparison check passed!!

## Description

Adjusts the `condition` parameter of
`include-conditionally-run-stress-test` to apply to the entire stage
rather than the test-running job. This improves the clarity from the
pipeline overview page, see most recent run vs previous ones:


![image](https://github.com/user-attachments/assets/e344d02a-a617-4163-bbda-0bfaac276541)

This also fixes the `stressMode` parameter not being given options at
queue time, which was introduced in microsoft#21702 and prevented the pipeline
from being queued.

---------

Co-authored-by: Abram Sanderson <[email protected]>
…ched tree (microsoft#22947)

## Description

It is possible to load a summary into a detached SharedTree. In this
case, the detached revision that is used to generate sequence IDs for
commits while detached must be updated to ensure that it doesn't
duplicate any of the sequence IDs already used in the summary. This PR
fixes the issue and also adds an assert when sequencing in the
EditManager to ensure that we don't sequence regressive sequence IDs.

This fix also allows us to trim the trunk when summarizing (without
breaking our fuzz tests), which reduces summary sizes especially for
detached trees with many synchronous edits.
const testVariant = getFluidTestVariant();
process.env.FLUID_TEST_VARIANT = testVariant;

return config(packageDir, additionalRequiredModules, testVariant);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this looks wrong, seems like you want getFluidTestMochaConfig(packageDir, additionalRequiredModules, testVariant) here. Same in other mocharc

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks for catching that!

@@ -30,7 +30,7 @@
"test": "npm run test:realsvc:odsp:run",
"test:coverage": "c8 npm test",
"test:realsvc:odsp": "cross-env npm run test:realsvc:odsp:run",
"test:realsvc:odsp:run": "mocha --recursive \"lib/test/**/*.spec.*js\" --exit --timeout 20000",
"test:realsvc:odsp:run": "mocha --recursive \"lib/test/**/*.spec.*js\" --exit --timeout 20000 --config src/test/.mocharc.cjs -- --driver=odsp --driverEndpoint=odsp",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a reason for the -- (i.e. not passing --driver=odsp directly to mocha)?

AFAIK that syntax is mostly just a thing for npm, where generally speaking, command-line arguments to npm are not plumbed through to child processes it creates. So e.g. npm run foo --someFlag runs the script foo and passes someFlag to the npm process, but whatever code executes as a result of running the foo script won't see --someFlag in its arguments. However npm run foo -- --someFlag is the opposite: the npm process doesn't have --someFlag but the script for foo will.

…oft#22953)

## Description

Make SchematizingSimpleTreeView implement TreeViewAlpha, and add some
helper types.
…2954)

previous shouldDeploy condition have not been included in deployment
condition. This variable has been updated to "forceDeployment" and
included back in the deployment condition.

shouldDeploy has been updated to check if release builds are the latest
version in its major version series.
@github-actions github-actions bot added area: build Build related issues area: dds Issues related to distributed data structures area: dds: tree area: framework Framework is a tag for issues involving the developer framework. Eg Aqueduct area: website changeset-present public api change Changes to a public API labels Nov 1, 2024
Copy link
Contributor

github-actions bot commented Nov 1, 2024

🔗 Found some broken links! 💔

Run a link check locally to find them. See
https://github.com/microsoft/FluidFramework/wiki/Checking-for-broken-links-in-the-documentation for more information.

linkcheck output


> [email protected] ci:linkcheck /home/runner/work/FluidFramework/FluidFramework/docs
> start-server-and-test ci:start 1313 linkcheck:full

1: starting server using command "npm run ci:start"
and when url "[ 'http://127.0.0.1:1313' ]" is responding with HTTP status code 200
running tests using command "npm run linkcheck:full"


> [email protected] ci:start
> http-server ./public --port 1313 --silent


> [email protected] linkcheck:full
> npm run linkcheck:fast -- --external


> [email protected] linkcheck:fast
> linkcheck http://localhost:1313 --skip-file skipped-urls.txt --external

Crawling...

http://localhost:1313/docs/start/quick-start/
- (3422:4) 'Node.js' => https://nodejs.org/en/download (connection failed)


Stats:
  440694 links
    3397 destination URLs
       2 URLs ignored
       1 warnings
       1 errors

 ELIFECYCLE  Command failed with exit code 1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: build Build related issues area: dds: tree area: dds Issues related to distributed data structures area: framework Framework is a tag for issues involving the developer framework. Eg Aqueduct area: website base: main PRs targeted against main branch changeset-present public api change Changes to a public API
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants