]
interface samr
{
	import "../rpc.idl";
	import "lsarpc.idl";

	typedef [v1_enum] enum {
		ACB_DISABLED               = 0x00000001, /* 1 = User account disabled */
		ACB_HOMDIRREQ              = 0x00000002, /* 1 = Home directory required */
		ACB_PWNOTREQ               = 0x00000004, /* 1 = User password not required */
		ACB_TEMPDUP                = 0x00000008, /* 1 = Temporary duplicate account */

call:convertxm %FESS_MIN_MEM% JVM_XMS
call:convertxm %FESS_MAX_MEM% JVM_XMX

CALL "%FESS_HOME%\bin\fess.in.bat"

rem thread stack size
set JVM_SS=256

Después de activar el entorno virtual, la variable `PATH` se vería algo así:

//// tab | Linux, macOS

```plaintext
/home/user/code/awesome-project/.venv/bin:/usr/bin:/bin:/usr/sbin:/sbin
```

Eso significa que el sistema ahora comenzará a buscar primero los programas en:

```plaintext
/home/user/code/awesome-project/.venv/bin
```

antes de buscar en los otros directorios.

  <dependencies>
    <dependency>
      <groupId>com.sun</groupId>
      <artifactId>tools</artifactId>
      <version>1.4.2</version>
      <scope>system</scope>
      <systemPath>${jre.home}/../lib/tools.jar</systemPath>
    </dependency>
  </dependencies>

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>

        when(logonInfo.getUserDisplayName()).thenReturn("Display Name");
        when(logonInfo.getProfilePath()).thenReturn("\\\\server\\\\profile");
        when(logonInfo.getHomeDirectory()).thenReturn("\\\\server\\\\home");
        when(logonInfo.getHomeDrive()).thenReturn("H:");
        when(logonInfo.getLogonScript()).thenReturn("logon.bat");
        when(logonInfo.getUserAccountControl()).thenReturn(0x200);

        if (mavenUserConf != null) {
            return Paths.get(mavenUserConf, FILE_NAME);
        }
        // this means we are in UT or alike
        return Paths.get(System.getProperty("user.home"), ".m2", FILE_NAME);
    }

 * This is not correct as it should do this with the built distribution instead.
 *
 * Doing it correctly would require running a Gradle build with the full
 * distribution and extracting the generated api jar from its Gradle user home,
 * slowing down building documentation.
 *
 * All this would be so much simpler if the Kotlin extensions to the Gradle API
 * were generated at build time instead.
 *

            docker stop $running_containers;
          fi
          docker container prune -f
          docker image prune -af
      - name: Clean repository
        shell: bash
        run: find /home/ubuntu/actions-runner/_work/tensorflow/tensorflow/. -name . -o -prune -exec sudo rm -rf -- {} + || true
      - name: Checkout repository for nightly (skipped for releases)
        if: ${{ github.event_name == 'schedule' }}

        val extension =
            project.extensions.create("androidHomeWarmup", AndroidHomeWarmupExtension::class.java).apply {
                warmupProjectsDirectory.convention(project.layout.buildDirectory.dir("android-home-warmup"))
            }

        project.tasks.register("androidHomeWarmup", AndroidHomeWarmupTask::class) {
            warmupProjectsDirectory.set(extension.warmupProjectsDirectory)

        return sessionBuilder;
    }

    private Path resolve(String string) {
        if (string.startsWith("~/") || string.startsWith("~\\")) {
            // resolve based on $HOME
            return Paths.get(System.getProperty("user.home"))
                    .resolve(string.substring(2))
                    .normalize()
                    .toAbsolutePath();
        } else {
            // resolve based on $CWD