Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 6 of 6 for workspace (0.04 sec)

  1. configure.py

      parser = argparse.ArgumentParser()
      parser.add_argument(
          '--workspace',
          type=str,
          default=os.path.abspath(os.path.dirname(__file__)),
          help='The absolute path to your active Bazel workspace.')
      args = parser.parse_args()
    
      _TF_WORKSPACE_ROOT = args.workspace
      _TF_BAZELRC = os.path.join(_TF_WORKSPACE_ROOT, _TF_BAZELRC_FILENAME)
    
    Registered: Tue Sep 09 12:39:10 UTC 2025
    - Last Modified: Wed Apr 30 15:18:54 UTC 2025
    - 48.3K bytes
    - Viewed (0)
  2. compat/maven-compat/src/main/java/org/apache/maven/project/artifact/MavenMetadataSource.java

            RepositorySystemSession repositorySession = legacySupport.getRepositorySession();
            final WorkspaceReader workspace = repositorySession.getWorkspaceReader();
            Model model;
            if (workspace instanceof MavenWorkspaceReader mavenWorkspaceReader) {
                model = mavenWorkspaceReader.findModel(RepositoryUtils.toArtifact(artifact));
            } else {
    Registered: Sun Sep 07 03:35:12 UTC 2025
    - Last Modified: Wed Mar 26 10:49:22 UTC 2025
    - 30.4K bytes
    - Viewed (0)
  3. doc/godebug.md

    Using `panicnil=1` restores the behavior of Go 1.20 and earlier.
    
    When compiling a work module or workspace that declares
    an older Go version, the Go toolchain amends its defaults
    to match that older Go version as closely as possible.
    For example, when a Go 1.21 toolchain compiles a program,
    if the work module's `go.mod` or the workspace's `go.work`
    says `go` `1.20`, then the program defaults to `panicnil=1`,
    matching Go 1.20 instead of Go 1.21.
    Registered: Tue Sep 09 11:13:09 UTC 2025
    - Last Modified: Tue Jul 08 18:30:38 UTC 2025
    - 22.9K bytes
    - Viewed (0)
  4. compat/maven-compat/src/main/java/org/apache/maven/artifact/resolver/DefaultArtifactResolver.java

            RepositorySystemSession session = getSession(request.getLocalRepository());
    
            // TODO: hack because metadata isn't generated in m2e correctly and i want to run the maven i have in the
            // workspace
            if (source == null) {
                try {
                    source = container.lookup(ArtifactMetadataSource.class);
                } catch (ComponentLookupException e) {
                    // won't happen
    Registered: Sun Sep 07 03:35:12 UTC 2025
    - Last Modified: Fri Jun 06 14:28:57 UTC 2025
    - 25K bytes
    - Viewed (0)
  5. CONTRIBUTING.md

        which case remember to change the directory from `/root` to `/tensorflow`
        once you get into the running container so `bazel` can find the `tensorflow`
        workspace).
    
        you can do this by using the following command. As an example-
    
        ```bash
        docker run -it --rm -v $PWD:/tmp -w /tmp tensorflow/build:2.15-python3.10
        ```
    
    Registered: Tue Sep 09 12:39:10 UTC 2025
    - Last Modified: Sat Jan 11 04:47:59 UTC 2025
    - 15.9K bytes
    - Viewed (0)
  6. compat/maven-compat/src/main/java/org/apache/maven/repository/legacy/LegacyRepositorySystem.java

                    } finally {
                        request.setLocalRepository(localRepository);
                    }
                }
            } catch (ComponentLookupException e) {
                // no ide workspace artifact resolution
            }
    
            return artifactResolver.resolve(request);
        }
    
        @Override
        public List<ArtifactRepository> getEffectiveRepositories(List<ArtifactRepository> repositories) {
    Registered: Sun Sep 07 03:35:12 UTC 2025
    - Last Modified: Fri Jun 06 14:28:57 UTC 2025
    - 31.2K bytes
    - Viewed (0)
Back to top