Skip to content

Increased the scope of File Interceptor to intercept methods from FileSystemProvider.class #18068

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

Closed

Conversation

pranu2502
Copy link
Contributor

@pranu2502 pranu2502 commented Apr 24, 2025

Description

Increased the scope of File Interceptor to intercept methods from FileSystemProvider.class, as newByteChannel is currently not being intercepted.

Related Issues

Resolves #[Issue number to be closed when this PR is merged]

Check List

  • Functionality includes testing.
  • API changes companion pull request created, if applicable.
  • Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Copy link
Contributor

❌ Gradle check result for 248947d: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

@pranu2502 pranu2502 force-pushed the newByteChannel-intercept branch from 248947d to ff368cd Compare April 24, 2025 07:37
@pranu2502 pranu2502 changed the title New byte channel intercept Increased the scope of File Interceptor to intercept methods from FileSystemProvider.class Apr 24, 2025
Copy link
Contributor

❌ Gradle check result for ff368cd: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Copy link
Contributor

❌ Gradle check result for 34804be: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

@pranu2502 pranu2502 force-pushed the newByteChannel-intercept branch from 34804be to f359dc3 Compare April 24, 2025 18:26
Copy link
Contributor

❌ Gradle check result for f359dc3: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

@pranu2502 pranu2502 force-pushed the newByteChannel-intercept branch from f359dc3 to 67f198d Compare April 24, 2025 19:09
Copy link
Contributor

❌ Gradle check result for 67f198d: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

@pranu2502 pranu2502 force-pushed the newByteChannel-intercept branch from 67f198d to c1036a4 Compare April 25, 2025 05:27
Copy link
Contributor

❌ Gradle check result for c1036a4: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant