/**
     * Constructs a tree connect AndX request to establish a connection to a shared resource.
     *
     * @param ctx the CIFS context containing configuration
     * @param server the server data containing security information
     * @param path the UNC path to the shared resource
     * @param service the service type (e.g., "A:" for disk share, "LPT1:" for printer)
     * @param andx the next command in the AndX chain, or null
     */

        assertNotEquals(a, c);

        // Same subject instance -> equal
        Subject shared = new Subject();
        Kerb5Authenticator d1 = new Kerb5Authenticator(shared);
        Kerb5Authenticator d2 = new Kerb5Authenticator(shared);
        assertEquals(d1, d2);

        // Different type -> false
        assertFalse(a.equals("not-an-auth"));
    }

    @Test

        SmbTreeConnection c1 = newConn();
        SmbTreeConnection c2 = newConn();
        SmbTreeImpl shared = mock(SmbTreeImpl.class);
        when(shared.acquire(false)).thenReturn(shared);

        setTree(c1, shared);
        setTree(c2, shared);
        assertTrue(c1.isSame(c2));

        SmbTreeImpl other = mock(SmbTreeImpl.class);
        when(other.acquire(false)).thenReturn(other);

# packages only provide the "0.10-2build1" version. We use patchelf to manipulate
# certain shared libraries during the wheel building process (https://github.com/tensorflow/tensorflow/blob/master/tensorflow/tools/pip_package/build_pip_package.sh#L255-L262).
# When we use Patchelf versions <0.12, those shared libraries end up with a

    }),
    tags = [
        "no_cuda_asan",  # TODO(b/181771536)
        "no_windows",  # TODO(b/155444728)
    ],
    # We must ensure that the dependencies can be dynamically linked since
    # the shared library must be able to use core:framework.
    deps = [
        ":c_api",
        ":c_api_internal",
        ":c_test_util",
        ":test_op_kernel",
        ":tf_buffer",
        ":tf_buffer_internal",

This can be very useful for setting up **resources** that you need to use for the whole app, and that are **shared** among requests, and/or that you need to **clean up** afterwards. For example, a database connection pool, or loading a shared machine learning model.

## Use Case { #use-case }

Let's start with an example **use case** and then see how to solve it with this.

Shared scheme

```
org.gradle[.<qualifier>].<feature-name>.<detail>
```

The optional qualifier defines the secondary aspects, if any.

For better ergonomics on the CLI, some properties can have supplementary command-line build option(s).
The name of the feature in the build option SHOULD be the same as in the property name.

Shared scheme for long-form build options:

```

   * the internal list.
   */
  @JvmStatic
  fun fragmentBuffer(buffer: Buffer): Buffer {
    // Write each byte into a new buffer, then clone it so that the segments are shared.
    // Shared segments cannot be compacted so we'll get a long chain of short segments.
    val result = Buffer()
    while (!buffer.exhausted()) {
      val box = Buffer()
      box.write(buffer, 1)

 * See the License for the specific language governing permissions and
 * limitations under the License.
 */

description = "Provides a set of plugins that are shared between the Gradle and build-logic builds"

tasks.register("check") {
    dependsOn(subprojects.map { "${it.name}:check" })

# under the License.

name: PR Automation
on:
  pull_request_target:
    types:
      - closed

jobs:
  pr-automation:
    name: PR Automation