thanks for digging!

@happy-kitchen-89482 I do not believe we have a coursier config file

HANG ON

🤦

@wonderful-yak-59945 Can you see what happens if you put the

osgeo

repo ahead of maven-central in your config file?

hrm same result it looks like

that is with

[coursier]
repos = [
  "<https://repo.osgeo.org/repository/release>",
  "<https://maven-central.storage-download.googleapis.com/maven2>",
  "<https://repo1.maven.org/maven2>",
]

OK, that was worth checking at least 🙂

I feel like I'm constantly needing to sanity check everything any time jvm dependency resolves are involved lol

maven is… Not Very Good, tbqh

so far coursier seems significantly more pleasant than ivy at least!

I'll be in and out of meetings today, but will keep an eye on this thread if there's anything else I can do to help

Until now, it’s worked reasonably for us!

My working hypothesis here is that Coursier isn’t handling this situation where multiple repos supply

javax.media:jai-tools

Hey, Benjy asked me to post this for y’all to see, so here I go: Amongst team members having problems to get going with Pants, one saw some very confusing paths that suggest a mash-up between Python 2.7.0 and 3.9. This is the error they got:

(devtools) Moon-Kang's-MacBook-Pro:devtools moon$ make lint
./pants lint typecheck ::
15:14:58.25 [INFO] Initializing scheduler...
15:14:58.53 [INFO] Scheduler initialized.
15:15:10.94 [ERROR] Exception caught: (pants.engine.internals.scheduler.ExecutionError)
  File "/Users/moon/.cache/pants/setup/bootstrap-Darwin-x86_64/2.7.0_py39/lib/python3.9/site-packages/pants/bin/local_pants_runner.py", line 236, in _run_inner
    return self._perform_run(goals)
  File "/Users/moon/.cache/pants/setup/bootstrap-Darwin-x86_64/2.7.0_py39/lib/python3.9/site-packages/pants/bin/local_pants_runner.py", line 175, in _perform_run
    self._raise_on_error([t for _, t in throws])
  File "/Users/moon/.cache/pants/setup/bootstrap-Darwin-x86_64/2.7.0_py39/lib/python3.9/site-packages/pants/engine/internals/scheduler.py", line 506, in _raise_on_error
    raise ExecutionError(

Exception message: 1 Exception encountered:

  ProcessExecutionFailure: Process 'Find interpreter for constraints: CPython<4,>=3.6' failed with exit code 1.

This is a MacBook Pro running macOS 12.2.1. As far as Python is concerned, they have several installed, including 3.7, 3.8, 3.9, as far as I know mostly with pyenv. Robert

That is confusing, I would have thought putting it ahead would work

@witty-crayon-22786 thoughts here?

@happy-kitchen-89482 I’m working on reproducing this — it looks like we’re not overriding the default coursier repos

so whatever we specify comes after the user’s local

ivy2

cache and

<http://repo1.maven.org|repo1.maven.org>

Aha! Good find!

I’ve added comments to the github thread. There’ll be a fix PR incoming

https://github.com/pantsbuild/pants/pull/14581 (FYI @wonderful-yak-59945)

@wonderful-yak-59945: which version of Pants are you all evaluating? things are still changing on an ongoing basis, so 2.10.x is relatively stable, but will not contain multiple-scala-version or multiple-jdk-version support (which are in 2.11.x)

I think you meant to ping @wonderful-yak-59945 🙂

deerp. sorry about that

hi! we're set up with 2.9.0 currently but probably easy enough to bump that to a higher version

we shouldn't need multiple jdk/scala version support for the moment, though that is certainly something that would be relevant down the road

got it: thanks. i think that we can probably start by cherry-picking only to

2.10.x

then, which should stabilize in the next week or so

@witty-crayon-22786/@happy-kitchen-89482 here’s a CP to 2.10.x. Enjoy: https://github.com/pantsbuild/pants/pull/14584