Is there any way to stop coursier from running when I don't need the deps it provides?

⏺ oss/pants-pyright % ./pants --changed-since=origin/main fmt                                                                                ⎇ 17557-npx-dep-version*
⠠ 107.83s Fetching with coursier: org.scala-lang:scala-reflect:2.13.7
⠤ 107.73s Fetching with coursier: org.jline:jline:3.20.0
⠤ 107.73s Fetching with coursier: org.scalameta:scalafmt-interfaces:3.2.1
⠤ 107.73s Fetching with coursier: org.scala-lang.modules:scala-parallel-collections_2.13:1.0.4
⠤ 107.73s Fetching with coursier: org.scala-lang:scala-compiler:2.13.7

That went up to 3000 seconds before I cancelled it yesterday, and I'm formatting 3 python files in the nodejs backend

besides toggle the jvm off, that seems very broken..

besides toggle the jvm off

Like remove the backend packages?

> besides toggle the jvm off

Like remove the backend packages?

can’t you disable the jvm backend?

─❯ ./pants global --help-advanced | grep backend
  --backend-packages="['<str>', '<str>', ...]"
  PANTS_BACKEND_PACKAGES
  backend_packages
      default: []
      current value: [
          "pants.backend.build_files.fix.deprecations",
          "pants.backend.build_files.fmt.black",
          "pants.backend.python",
          "pants.backend.experimental.python.packaging.pyoxidizer",
          "pants.backend.explorer",
          "pants.backend.python.lint.autoflake",
          "pants.backend.python.lint.black",
          "pants.backend.python.lint.docformatter",
          "pants.backend.python.lint.flake8",
          "pants.backend.python.lint.isort",
          "pants.backend.python.typecheck.mypy",
          "pants.backend.python.mixed_interpreter_constraints",
          "pants.backend.shell",
          "pants.backend.shell.lint.shellcheck",
          "pants.backend.shell.lint.shfmt",
          "pants.backend.docker",
          "pants.backend.docker.lint.hadolint",
          "pants.backend.experimental.go",
          "pants.backend.experimental.java",
          "pants.backend.experimental.java.lint.google_java_format",
          "pants.backend.experimental.java.debug_goals",
          "pants.backend.experimental.python",
          "pants.backend.experimental.python.packaging.pyoxidizer",
          "pants.backend.experimental.scala",
          "pants.backend.experimental.scala.lint.scalafmt",
          "pants.backend.experimental.scala.debug_goals",
          "internal_plugins.releases",
          "internal_plugins.test_lockfile_fixtures"
      ] (from pants.toml)
      Register functionality from these backends.

╰─❯ ./pants --backend-packages="-['pants.backend.experimental.java', 'pants.backend.experimental.java.lint.google_java_format', 'pants.backend.experimental.java.debug_goals']" global --help-advanced | grep backend
10:41:43.77 [INFO] Initialization options changed: reinitializing scheduler...
10:41:45.08 [INFO] Scheduler initialized.
  --backend-packages="['<str>', '<str>', ...]"
  backend_packages
          "pants.backend.build_files.fix.deprecations",
          "pants.backend.build_files.fmt.black",
          "pants.backend.python",
          "pants.backend.experimental.python.packaging.pyoxidizer",
          "pants.backend.explorer",
          "pants.backend.python.lint.autoflake",
          "pants.backend.python.lint.black",
          "pants.backend.python.lint.docformatter",
          "pants.backend.python.lint.flake8",
          "pants.backend.python.lint.isort",
          "pants.backend.python.typecheck.mypy",
          "pants.backend.python.mixed_interpreter_constraints",
          "pants.backend.shell",
          "pants.backend.shell.lint.shellcheck",
          "pants.backend.shell.lint.shfmt",
          "pants.backend.docker",
          "pants.backend.docker.lint.hadolint",
          "pants.backend.experimental.go",
          "pants.backend.experimental.python",
          "pants.backend.experimental.python.packaging.pyoxidizer",
          "pants.backend.experimental.scala",
          "pants.backend.experimental.scala.lint.scalafmt",
          "pants.backend.experimental.scala.debug_goals",
      Register functionality from these backends.

I was just confirming what you meant by toggle the jvm off.. yep, testing that shortly to see what happens

Ah, misread your “remove backend” as actually removing the sources… 🤣

Delete.... EVERYTHING!!!!!!!

Oh huh thought

So, two surprises here. I is the actual

coursier

-centric "bug"? Still determining what's going on. The other is that, removing the scalafmt from the backend packages still caused an issue during

lint

I believe.

The other is no surprise, if you’re using fields in your BUILD files that comes from a disabled backend, expect issues..

🙂 True, but! Isn't this one a weird one? I've skipped/disabled scalafmt globally, and can no longer use Pants because I want to... skip ... scala... formatting.... .....

Pantsoboros? Ouropantsos?

Pants 3.0 aka Jörmungandr

.. I say “no?“, based on https://github.com/pantsbuild/pants/blob/b4334427b07bd057034718d3b7b8ea013b9a9bf1/src/python/pants/backend/scala/dependency_inference/BUILD#L14 🙂

Yeah, technically makes sense - but UX feels a bit janky. This is actually part of a bigger discussion that I'm not sure how I feel about - where I wonder if BUILD files without the correct backend should be so strict, unless something is specifically intended to be run in the dependency chain or via

::

But that's more just spitballing

FWIW I want general goal fields. (E.g. "skip_fmt") which might've been intended here

Yep, I'm working on a UX doc for next month's meeting, so just collecting some anecdotes as we run into them. A general

skip_goal

I think makes more sense here, rather than

skip_this_backendoption_which_may_not_be_registered

I think there's 2 here: • General fields for skipping goals • Allow "unknown" fields