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

fix: Updated the depreciated RunQueryNVerifyResponseViews to use runQueryAndVerifyResponseViews #37945

Closed
wants to merge 1 commit into from

Conversation

albinAppsmith
Copy link
Collaborator

@albinAppsmith albinAppsmith commented Dec 4, 2024

Description

This PR removes the deprecated RunQueryNVerifyResponseViews and implemented runQueryAndVerifyResponseViews instead.

Fixes

Automation

/ok-to-test tags="@tag.Sanity, @tag.Datasource"

🔍 Cypress test results

Caution

🔴 🔴 🔴 Some tests have failed.
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/12163035711
Commit: aaa6bcd
Cypress dashboard.
Tags: @tag.Sanity, @tag.Datasource
Spec:
The following are new failures, please fix them before merging the PR:

  1. cypress/e2e/Regression/ServerSide/ApiTests/API_MultiPart_Spec.ts
List of identified flaky tests.
Wed, 04 Dec 2024 16:36:04 UTC

Communication

Should the DevRel and Marketing teams inform users about this change?

  • Yes
  • No

Summary by CodeRabbit

  • New Features

    • Enhanced clarity and consistency in method calls for querying and verifying responses across various test cases related to Google Sheets and Oracle/MsSQL data sources.
    • Added a new test case for verifying the default port for Microsoft SQL Server.
  • Bug Fixes

    • Improved error handling in MsSQL tests to validate missing fields with appropriate feedback messages.
  • Refactor

    • Standardized method naming conventions and parameter formats across multiple test cases to improve readability and maintainability.

Copy link
Contributor

coderabbitai bot commented Dec 4, 2024

Walkthrough

The changes in this pull request focus on updating the Cypress end-to-end test suite for Google Sheets functionality. The primary modification involves renaming the method RunQueryNVerifyResponseViews to runQueryAndVerifyResponseViews, which now accepts an object parameter containing a count property instead of a direct integer. This change is applied consistently across multiple test cases, ensuring clarity and standardization in method calls and parameter handling. Minor adjustments to comments for clarity are also included, while the overall test logic and structure remain unchanged.

Changes

File Path Change Summary
app/client/cypress/e2e/GSheet/AllAccess_Spec.ts Renamed method from RunQueryNVerifyResponseViews to runQueryAndVerifyResponseViews. Updated method signature to accept an object parameter.
app/client/cypress/e2e/GSheet/GsheetMisc_Spec.ts Updated method call to runQueryAndVerifyResponseViews with object parameter.
app/client/cypress/e2e/GSheet/ReadNWrite_Access_Spec.ts Renamed method and updated to use object parameter format.
app/client/cypress/e2e/GSheet/ReadOnly_Access_Spec.ts Method renamed and updated to object parameter format. Added assertions for error handling.
app/client/cypress/e2e/GSheet/SelectedSheet_Access_Spec.ts Updated method calls to the new naming convention and object parameter format.
app/client/cypress/e2e/GSheet/WidgetBinding_AllAccess_Spec.ts Renamed method and updated parameter format.
app/client/cypress/e2e/GSheet/WidgetBinding_SelectedAccess_Spec.ts Updated method call to the new naming convention and object parameter format.
app/client/cypress/e2e/Regression/ServerSide/Datasources/Oracle_Spec.ts Renamed method and updated to use object parameter format.
app/client/cypress/e2e/Sanity/Datasources/MsSQL_Basic_Spec.ts Renamed method, updated to object parameter format, and enhanced error handling.

Possibly related PRs

Suggested labels

Enhancement, ok-to-test, Test, Widgets Product, Integrations Pod General

Suggested reviewers

  • ApekshaBhosale
  • sagar-qa007
  • hetunandu

🎉 In the realm of code where tests do play,
A method was renamed, brightening the day!
With parameters wrapped in an object so neat,
Clarity reigns, making tests quite the treat!
From Google Sheets to databases galore,
Our test suite shines, ready to explore! 🌟


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions github-actions bot added the Bug Something isn't working label Dec 4, 2024
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (5)
app/client/cypress/e2e/GSheet/SelectedSheet_Access_Spec.ts (1)

Line range hint 1-350: Remove cy.wait and agHelper.Sleep calls

The test contains multiple instances of agHelper.Sleep() and implicit waits. This makes tests flaky and slower.

Replace these with proper Cypress wait strategies:

- agHelper.Sleep(500);
+ cy.get('[data-cy="dropdown-option"]').should('be.visible');

- cy.wait('@postExecute')
+ cy.wait('@postExecute').its('response.statusCode').should('eq', 200)
app/client/cypress/e2e/GSheet/ReadOnly_Access_Spec.ts (2)

Line range hint 1-350: Refactor test assertions for better maintainability

Consider extracting common assertion messages and test data into constants or fixtures.

+ const ERROR_MESSAGES = {
+   INSUFFICIENT_SCOPE: "Request had insufficient authentication scopes.",
+   INVALID_RANGE: "Unable to parse range: 'Sheet 2'!1:1"
+ };

- expect(interception.response.body.data.body).to.deep.equal(
-   "Request had insufficient authentication scopes."
- );
+ expect(interception.response.body.data.body).to.deep.equal(
+   ERROR_MESSAGES.INSUFFICIENT_SCOPE
+ );

Line range hint 1-1: Consider implementing shared test utilities

Multiple test files share similar patterns for:

  • Query verification
  • Error message assertions
  • Data setup and teardown

Consider creating shared test utilities to reduce duplication and improve maintainability.

app/client/cypress/e2e/GSheet/ReadNWrite_Access_Spec.ts (2)

245-245: Method signature updates look good, but avoid using Sleep/wait.

While the method updates are correct, there are instances of agHelper.Sleep() and cy.wait() in this test file which should be avoided per coding guidelines.

Consider replacing agHelper.Sleep() and cy.wait() with Cypress's built-in retry-ability and assertions:

// Instead of:
agHelper.Sleep();
// Use:
cy.get('selector').should('exist');

// Instead of:
cy.wait('@networkCall')
// Use:
cy.intercept('POST', '/api/endpoint').as('networkCall');
cy.get('selector').should('exist');
cy.wait('@networkCall').its('response.statusCode').should('eq', 200);

Also applies to: 278-278


Line range hint 1-400: Consider additional improvements for test reliability.

While the method signature updates are good, there are several areas for improvement in the test file:

  1. Replace all instances of agHelper.Sleep() and cy.wait() with proper Cypress assertions
  2. Consider using data-* attributes for selectors instead of class names
  3. Consider moving test data to fixtures instead of inline JSON

Would you like assistance in implementing these improvements?

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 1f07be3 and aaa6bcd.

📒 Files selected for processing (9)
  • app/client/cypress/e2e/GSheet/AllAccess_Spec.ts (8 hunks)
  • app/client/cypress/e2e/GSheet/GsheetMisc_Spec.ts (2 hunks)
  • app/client/cypress/e2e/GSheet/ReadNWrite_Access_Spec.ts (7 hunks)
  • app/client/cypress/e2e/GSheet/ReadOnly_Access_Spec.ts (7 hunks)
  • app/client/cypress/e2e/GSheet/SelectedSheet_Access_Spec.ts (8 hunks)
  • app/client/cypress/e2e/GSheet/WidgetBinding_AllAccess_Spec.ts (1 hunks)
  • app/client/cypress/e2e/GSheet/WidgetBinding_SelectedAccess_Spec.ts (1 hunks)
  • app/client/cypress/e2e/Regression/ServerSide/Datasources/Oracle_Spec.ts (7 hunks)
  • app/client/cypress/e2e/Sanity/Datasources/MsSQL_Basic_Spec.ts (1 hunks)
🧰 Additional context used
📓 Path-based instructions (9)
app/client/cypress/e2e/GSheet/AllAccess_Spec.ts (1)

Pattern app/client/cypress/**/**.*: Review the following e2e test code written using the Cypress test library. Ensure that:

  • Follow best practices for Cypress code and e2e automation.
  • Avoid using cy.wait in code.
  • Avoid using cy.pause in code.
  • Avoid using agHelper.sleep().
  • Use locator variables for locators and do not use plain strings.
  • Use data-* attributes for selectors.
  • Avoid Xpaths, Attributes and CSS path.
  • Avoid selectors like .btn.submit or button[type=submit].
  • Perform logins via API with LoginFromAPI.
  • Perform logout via API with LogOutviaAPI.
  • Perform signup via API with SignupFromAPI.
  • Avoid using it.only.
  • Avoid using after and aftereach in test cases.
  • Use multiple assertions for expect statements.
  • Avoid using strings for assertions.
  • Do not use duplicate filenames even with different paths.
  • Avoid using agHelper.Sleep, this.Sleep in any file in code.
app/client/cypress/e2e/GSheet/ReadNWrite_Access_Spec.ts (1)

Pattern app/client/cypress/**/**.*: Review the following e2e test code written using the Cypress test library. Ensure that:

  • Follow best practices for Cypress code and e2e automation.
  • Avoid using cy.wait in code.
  • Avoid using cy.pause in code.
  • Avoid using agHelper.sleep().
  • Use locator variables for locators and do not use plain strings.
  • Use data-* attributes for selectors.
  • Avoid Xpaths, Attributes and CSS path.
  • Avoid selectors like .btn.submit or button[type=submit].
  • Perform logins via API with LoginFromAPI.
  • Perform logout via API with LogOutviaAPI.
  • Perform signup via API with SignupFromAPI.
  • Avoid using it.only.
  • Avoid using after and aftereach in test cases.
  • Use multiple assertions for expect statements.
  • Avoid using strings for assertions.
  • Do not use duplicate filenames even with different paths.
  • Avoid using agHelper.Sleep, this.Sleep in any file in code.
app/client/cypress/e2e/Regression/ServerSide/Datasources/Oracle_Spec.ts (1)

Pattern app/client/cypress/**/**.*: Review the following e2e test code written using the Cypress test library. Ensure that:

  • Follow best practices for Cypress code and e2e automation.
  • Avoid using cy.wait in code.
  • Avoid using cy.pause in code.
  • Avoid using agHelper.sleep().
  • Use locator variables for locators and do not use plain strings.
  • Use data-* attributes for selectors.
  • Avoid Xpaths, Attributes and CSS path.
  • Avoid selectors like .btn.submit or button[type=submit].
  • Perform logins via API with LoginFromAPI.
  • Perform logout via API with LogOutviaAPI.
  • Perform signup via API with SignupFromAPI.
  • Avoid using it.only.
  • Avoid using after and aftereach in test cases.
  • Use multiple assertions for expect statements.
  • Avoid using strings for assertions.
  • Do not use duplicate filenames even with different paths.
  • Avoid using agHelper.Sleep, this.Sleep in any file in code.
app/client/cypress/e2e/GSheet/GsheetMisc_Spec.ts (1)

Pattern app/client/cypress/**/**.*: Review the following e2e test code written using the Cypress test library. Ensure that:

  • Follow best practices for Cypress code and e2e automation.
  • Avoid using cy.wait in code.
  • Avoid using cy.pause in code.
  • Avoid using agHelper.sleep().
  • Use locator variables for locators and do not use plain strings.
  • Use data-* attributes for selectors.
  • Avoid Xpaths, Attributes and CSS path.
  • Avoid selectors like .btn.submit or button[type=submit].
  • Perform logins via API with LoginFromAPI.
  • Perform logout via API with LogOutviaAPI.
  • Perform signup via API with SignupFromAPI.
  • Avoid using it.only.
  • Avoid using after and aftereach in test cases.
  • Use multiple assertions for expect statements.
  • Avoid using strings for assertions.
  • Do not use duplicate filenames even with different paths.
  • Avoid using agHelper.Sleep, this.Sleep in any file in code.
app/client/cypress/e2e/GSheet/WidgetBinding_SelectedAccess_Spec.ts (1)

Pattern app/client/cypress/**/**.*: Review the following e2e test code written using the Cypress test library. Ensure that:

  • Follow best practices for Cypress code and e2e automation.
  • Avoid using cy.wait in code.
  • Avoid using cy.pause in code.
  • Avoid using agHelper.sleep().
  • Use locator variables for locators and do not use plain strings.
  • Use data-* attributes for selectors.
  • Avoid Xpaths, Attributes and CSS path.
  • Avoid selectors like .btn.submit or button[type=submit].
  • Perform logins via API with LoginFromAPI.
  • Perform logout via API with LogOutviaAPI.
  • Perform signup via API with SignupFromAPI.
  • Avoid using it.only.
  • Avoid using after and aftereach in test cases.
  • Use multiple assertions for expect statements.
  • Avoid using strings for assertions.
  • Do not use duplicate filenames even with different paths.
  • Avoid using agHelper.Sleep, this.Sleep in any file in code.
app/client/cypress/e2e/Sanity/Datasources/MsSQL_Basic_Spec.ts (1)

Pattern app/client/cypress/**/**.*: Review the following e2e test code written using the Cypress test library. Ensure that:

  • Follow best practices for Cypress code and e2e automation.
  • Avoid using cy.wait in code.
  • Avoid using cy.pause in code.
  • Avoid using agHelper.sleep().
  • Use locator variables for locators and do not use plain strings.
  • Use data-* attributes for selectors.
  • Avoid Xpaths, Attributes and CSS path.
  • Avoid selectors like .btn.submit or button[type=submit].
  • Perform logins via API with LoginFromAPI.
  • Perform logout via API with LogOutviaAPI.
  • Perform signup via API with SignupFromAPI.
  • Avoid using it.only.
  • Avoid using after and aftereach in test cases.
  • Use multiple assertions for expect statements.
  • Avoid using strings for assertions.
  • Do not use duplicate filenames even with different paths.
  • Avoid using agHelper.Sleep, this.Sleep in any file in code.
app/client/cypress/e2e/GSheet/WidgetBinding_AllAccess_Spec.ts (1)

Pattern app/client/cypress/**/**.*: Review the following e2e test code written using the Cypress test library. Ensure that:

  • Follow best practices for Cypress code and e2e automation.
  • Avoid using cy.wait in code.
  • Avoid using cy.pause in code.
  • Avoid using agHelper.sleep().
  • Use locator variables for locators and do not use plain strings.
  • Use data-* attributes for selectors.
  • Avoid Xpaths, Attributes and CSS path.
  • Avoid selectors like .btn.submit or button[type=submit].
  • Perform logins via API with LoginFromAPI.
  • Perform logout via API with LogOutviaAPI.
  • Perform signup via API with SignupFromAPI.
  • Avoid using it.only.
  • Avoid using after and aftereach in test cases.
  • Use multiple assertions for expect statements.
  • Avoid using strings for assertions.
  • Do not use duplicate filenames even with different paths.
  • Avoid using agHelper.Sleep, this.Sleep in any file in code.
app/client/cypress/e2e/GSheet/ReadOnly_Access_Spec.ts (1)

Pattern app/client/cypress/**/**.*: Review the following e2e test code written using the Cypress test library. Ensure that:

  • Follow best practices for Cypress code and e2e automation.
  • Avoid using cy.wait in code.
  • Avoid using cy.pause in code.
  • Avoid using agHelper.sleep().
  • Use locator variables for locators and do not use plain strings.
  • Use data-* attributes for selectors.
  • Avoid Xpaths, Attributes and CSS path.
  • Avoid selectors like .btn.submit or button[type=submit].
  • Perform logins via API with LoginFromAPI.
  • Perform logout via API with LogOutviaAPI.
  • Perform signup via API with SignupFromAPI.
  • Avoid using it.only.
  • Avoid using after and aftereach in test cases.
  • Use multiple assertions for expect statements.
  • Avoid using strings for assertions.
  • Do not use duplicate filenames even with different paths.
  • Avoid using agHelper.Sleep, this.Sleep in any file in code.
app/client/cypress/e2e/GSheet/SelectedSheet_Access_Spec.ts (1)

Pattern app/client/cypress/**/**.*: Review the following e2e test code written using the Cypress test library. Ensure that:

  • Follow best practices for Cypress code and e2e automation.
  • Avoid using cy.wait in code.
  • Avoid using cy.pause in code.
  • Avoid using agHelper.sleep().
  • Use locator variables for locators and do not use plain strings.
  • Use data-* attributes for selectors.
  • Avoid Xpaths, Attributes and CSS path.
  • Avoid selectors like .btn.submit or button[type=submit].
  • Perform logins via API with LoginFromAPI.
  • Perform logout via API with LogOutviaAPI.
  • Perform signup via API with SignupFromAPI.
  • Avoid using it.only.
  • Avoid using after and aftereach in test cases.
  • Use multiple assertions for expect statements.
  • Avoid using strings for assertions.
  • Do not use duplicate filenames even with different paths.
  • Avoid using agHelper.Sleep, this.Sleep in any file in code.
🔇 Additional comments (12)
app/client/cypress/e2e/GSheet/WidgetBinding_AllAccess_Spec.ts (1)

60-60: Method signature update looks good

The update to use runQueryAndVerifyResponseViews with an object parameter improves code clarity and maintainability.

app/client/cypress/e2e/GSheet/WidgetBinding_SelectedAccess_Spec.ts (1)

60-60: Method signature update looks good

The update maintains consistency with the new method signature pattern.

app/client/cypress/e2e/GSheet/GsheetMisc_Spec.ts (2)

107-107: Method signature update looks good

The update maintains consistency with the new method signature pattern throughout the test suite.


93-93: Method signature update looks good

The update to use object parameter improves readability. Consider verifying that GSHEET_DATA is properly loaded.

✅ Verification successful

Let me verify the test data structure further to ensure it's properly defined and used.


GSHEET_DATA is properly defined and used correctly

The constant is well-structured with test data containing all required fields (rowIndex, uniq_id, etc.) and is used consistently throughout the test file for verifying response counts and specific field values.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Verify GSHEET_DATA constant is properly defined
rg -A 5 "GSHEET_DATA.*=.*\[" app/client/cypress/fixtures/

Length of output: 519


Script:

#!/bin/bash
# Check how GSHEET_DATA is used in the test file
rg -B 2 -A 2 "GSHEET_DATA" app/client/cypress/e2e/GSheet/GsheetMisc_Spec.ts

# Check the complete test data structure
cat app/client/cypress/fixtures/test-data-gsheet.ts

Length of output: 12196

app/client/cypress/e2e/GSheet/SelectedSheet_Access_Spec.ts (1)

117-117: Replace deprecated method calls with updated version

The changes from RunQueryNVerifyResponseViews to runQueryAndVerifyResponseViews are correct, improving consistency across the codebase.

Also applies to: 126-126, 136-136, 152-152, 172-172, 190-190, 240-240, 275-275

app/client/cypress/e2e/GSheet/AllAccess_Spec.ts (2)

129-129: Replace deprecated method calls with updated version

The changes from RunQueryNVerifyResponseViews to runQueryAndVerifyResponseViews are correct, improving consistency across the codebase.

Also applies to: 138-138, 148-148, 164-164, 184-184, 202-202, 249-249, 284-284


Line range hint 15-15: Verify if describe.skip is intentional

The test suite is marked with describe.skip. Please verify if this is intentional or if the tests should be enabled.

✅ Verification successful

The skip is intentional and consistent across GSheet test files

All GSheet test files in the e2e directory are currently skipped:

  • app/client/cypress/e2e/GSheet/WidgetBinding_AllAccess_Spec.ts
  • app/client/cypress/e2e/GSheet/ReadOnly_Access_Spec.ts
  • app/client/cypress/e2e/GSheet/GsheetMisc_Spec.ts
  • app/client/cypress/e2e/GSheet/ReadNWrite_Access_Spec.ts
  • app/client/cypress/e2e/GSheet/AllAccess_Spec.ts

This appears to be a deliberate decision to skip the entire GSheet test suite.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if other GSheet test files are also skipped
rg "describe\.skip.*GSheet" -A 1

Length of output: 34


Script:

#!/bin/bash
# Let's try a broader search for skipped tests in the GSheet directory
fd ".*Spec\.ts$" --exec rg -l "describe\.skip|it\.skip" {}

# Also get the content of the specific file to verify the skip
cat "app/client/cypress/e2e/GSheet/AllAccess_Spec.ts"

Length of output: 13026

app/client/cypress/e2e/GSheet/ReadOnly_Access_Spec.ts (1)

139-139: Replace deprecated method calls with updated version

The changes from RunQueryNVerifyResponseViews to runQueryAndVerifyResponseViews are correct, improving consistency across the codebase.

Also applies to: 147-147, 156-156, 171-171, 190-190, 207-207, 227-227, 260-260

app/client/cypress/e2e/Regression/ServerSide/Datasources/Oracle_Spec.ts (1)

241-241: Method calls updated correctly to use object parameter

The updates to runQueryAndVerifyResponseViews are consistent across all occurrences, properly using the new object parameter format.

Also applies to: 275-275, 337-337, 340-340, 378-378, 407-407, 442-442, 452-452

app/client/cypress/e2e/Sanity/Datasources/MsSQL_Basic_Spec.ts (1)

143-143: Method call updated correctly to use object parameter

The update to runQueryAndVerifyResponseViews follows the new signature pattern consistently.

app/client/cypress/e2e/GSheet/ReadNWrite_Access_Spec.ts (2)

131-131: LGTM! Method signature update looks good.

The changes consistently update the deprecated method calls to use the new signature with object parameters.

Also applies to: 139-139, 148-148, 163-163


182-182: LGTM! Consistent method updates in filtering tests.

The method signature updates are properly applied in the filtering and cell range verification sections.

Also applies to: 199-199

@albinAppsmith albinAppsmith added the ok-to-test Required label for CI label Dec 4, 2024
@albinAppsmith
Copy link
Collaborator Author

Closing this PR. These changes are already available in #37897

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working ok-to-test Required label for CI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant