https://pantsbuild.org/ logo
Powered by
#general
  • s

    strong-crayon-70379

    02/08/2019, 4:28 PM
    unless I am missing something
  • a

    aloof-angle-91616

    02/08/2019, 4:29 PM
    yes, commenting out the lines in 
    /etc/pexrc
    (which i believe happens to be on your specific machine) temporarily addresses the issue. it’s been broken for some period of time, see #pex for status on fixes
    👍 2
  • s

    strong-crayon-70379

    02/08/2019, 4:30 PM
    ah thank you
  • a

    aloof-angle-91616

    02/08/2019, 4:31 PM
    (the message in #pex might be something different but i do believe john is working on it 🙏, just woke up)
    💤 2
    👍 1
  • w

    witty-crayon-22786

    02/08/2019, 4:47 PM
  • w

    witty-crayon-22786

    02/08/2019, 4:47 PM
    . @red-balloon-89377 is working on one piece of it, but if you have time left over from other efforts, syncing with him or John about it would be great.
  • s

    strong-crayon-70379

    02/08/2019, 4:56 PM
    ack
  • s

    strong-crayon-70379

    02/08/2019, 4:56 PM
    @red-balloon-89377 I have an idea for that one that I can sync with you and John on (if you havent started yet)
    r
    • 2
    • 4
  • f

    flaky-photographer-75744

    02/08/2019, 4:56 PM
    Hello guys, we are having a little issue setupping 
    scalafix
    with pants. When using 
    scalafix
    rule: 
    RemoveUnused
    , the following error occurs:
    Copy code
    ==== stdout ====
                     error: The Scala compiler option "-Ywarn-unused" is required to use RemoveUnused.
                     To fix this problem, update your build to use at least one Scala compiler
                     option that starts with "-Ywarn-unused"
    However in 
    pants.ini
    , we have set up correctly the following `zinc arguments`:
    Copy code
    ...
'-S-Ywarn-unused:implicits',
'-S-Ywarn-unused:imports',
'-S-Ywarn-unused:locals',
'-S-Ywarn-unused:params',
'-S-Ywarn-unused:patvars',
'-S-Ywarn-unused:privates',
...
    Is this a known issue or are we forgetting something ?
    a
    • 2
    • 4
  • f

    flaky-photographer-75744

    02/08/2019, 4:57 PM
    Thanks
  • f

    fierce-park-88503

    02/08/2019, 11:46 PM
    is there any way to enforce that tests targets declare dependencies on data files? (python tests, if it matters) i.e., only expose the data files that a test declares, all other files shouldn’t be accessible
    w
    • 2
    • 2
  • a

    aloof-angle-91616

    02/10/2019, 7:17 PM
  • s

    some-farmer-97614

    02/11/2019, 7:51 PM
    Hi! Can I build Rust with pants?
    a
    • 2
    • 7
  • j

    jolly-memory-78838

    02/12/2019, 5:37 PM
    I am running into a issue that go introduced today from pytests where they are broken for python 2.7 (https://github.com/pytest-dev/pytest/issues/4770) from my understanding their isn't a way to pin the dependency (more-iteratools) that is causing the problem. Looks like some of the other packages are configurable for pytests in (https://github.com/pantsbuild/pants/blob/master/src/python/pants/backend/python/subsystems/pytest.py) anyone else running into this issues? Can open up a github issue if that is better
    ☝️ 1
  • a

    aloof-angle-91616

    02/12/2019, 5:41 PM
    this is happening on our ci as well https://travis-ci.org/pantsbuild/pants/jobs/492004734
  • j

    jolly-memory-78838

    02/12/2019, 5:43 PM
    from reading the thread in pytest they are having some problems reproducing it and so far only workaround have seen is pinning more-itertools to 5.0.0
  • a

    aloof-angle-91616

    02/12/2019, 5:45 PM
    it looks like we might need to edit the subsystem to support pinning any of its transitive deps (EDIT: you can set this in pants.ini, actually, trying to get an example)
  • j

    jolly-memory-78838

    02/12/2019, 5:46 PM
    haven't gone to deep into it, but unless they update their deps and do a patch release for a version <= 3.7, from my understanding that would have to be done
    a
    • 2
    • 6
  • a

    aloof-angle-91616

    02/12/2019, 5:47 PM
    we should be able to pin the more-itertools transitive dep though
    e
    • 2
    • 5
  • j

    jolly-memory-78838

    02/12/2019, 5:48 PM
    i saw the flags wired through for setuptools, unittest2-requirements, cov|timeout-requirements
  • e

    enough-analyst-54434

    02/12/2019, 5:54 PM
    I think pinning pytest to 3.0.7, the minimum we allow right now, should work. That version does not use more-itertools: https://github.com/pytest-dev/pytest/blob/3.0.7/setup.py#L51
  • a

    aloof-angle-91616

    02/12/2019, 5:54 PM
    i can try that and see if it fixes my ci run
  • e

    enough-analyst-54434

    02/12/2019, 5:56 PM
    Copy code
    [pytest]
requirements: pytest==3.0.7
  • a

    aloof-angle-91616

    02/12/2019, 5:56 PM
    beat me by a second
  • e

    enough-analyst-54434

    02/12/2019, 5:56 PM
    I just tried this in pantsbuild/pants and seems to work fine.
    👍 2
  • a

    aloof-angle-91616

    02/12/2019, 5:57 PM
    i can make the PR pinning the subsystem pytest requirement to 3.0.7? (but users outside of the pants repo should be able to make the pants.ini change above)
    e
    • 2
    • 2
  • a

    aloof-angle-91616

    02/12/2019, 6:03 PM
    @jolly-memory-78838 ^ does the pants.ini change above fix your issue? sorry for the back and forth
  • j

    jolly-memory-78838

    02/12/2019, 6:03 PM
    I cleared my cache and worked
    👍 3
    e
    • 2
    • 1
  • j

    jolly-memory-78838

    02/12/2019, 6:11 PM
    thanks for the help for the bandaid, will keep an eye out for a fix
    ☝️ 1
  • a

    aloof-angle-91616

    02/12/2019, 6:13 PM
1...209620972098...2420Latest