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

    witty-crayon-22786

    11/06/2015, 6:22 PM
    cc @many-engine-77019
  • m

    many-engine-77019

    11/06/2015, 6:28 PM
    I was kinda thinking it’d be unlikely in practice to want different defaults for the two languages
  • w

    witty-crayon-22786

    11/06/2015, 6:31 PM
    @many-engine-77019: we know we want different defaults for 3037
  • w

    witty-crayon-22786

    11/06/2015, 6:32 PM
    ...although we could get around it by adding a bit of boilerplate.
  • w

    witty-crayon-22786

    11/06/2015, 6:32 PM
    maybe start with a single default, and go from there.
  • m

    mammoth-pharmacist-54215

    11/06/2015, 6:49 PM
    Is the ivy cache supposed to live outside of the pants workdir?
  • m

    many-engine-77019

    11/06/2015, 6:50 PM
    yep
  • m

    many-engine-77019

    11/06/2015, 6:50 PM
    theoretically it’s sufficiently immutable that cleaning it is an unnecessary expense
  • w

    witty-crayon-22786

    11/06/2015, 6:50 PM
    there is a question of whether it should at this point, but yes... that's currently intentional
  • m

    mammoth-pharmacist-54215

    11/06/2015, 6:51 PM
    perfect thanks
  • m

    many-engine-77019

    11/06/2015, 6:51 PM
    I mean, if you’re implement multiple levels of clean-all, it could move inside?
  • m

    many-engine-77019

    11/06/2015, 6:51 PM
    oh except you want to share ivy cache across copies of the repo
  • m

    mammoth-pharmacist-54215

    11/06/2015, 6:51 PM
    looking at an optional removal
  • w

    witty-crayon-22786

    11/06/2015, 6:52 PM
    @many-engine-77019: eh, sortof
  • m

    mammoth-pharmacist-54215

    11/06/2015, 6:52 PM
    currently it looks like its usually in a path like ~/ivy2/pants so its at least isolated from non pants stuff.
  • m

    mammoth-pharmacist-54215

    11/06/2015, 6:53 PM
    My understanding is that cleaning ivy is kind of an extreme option though and I don’t think its likely to be the default anywhere.
  • m

    mammoth-pharmacist-54215

    11/06/2015, 6:53 PM
    thats likely to cause more pain for devs
  • b

    bored-art-40741

    11/06/2015, 6:53 PM
    Back when the ivy cache would get corrupted for various reasons, telling someone to delete 
    ~/.ivy2
    was their cue to go home for the day
  • m

    mammoth-pharmacist-54215

    11/06/2015, 6:53 PM
    haha
  • m

    mammoth-pharmacist-54215

    11/06/2015, 6:54 PM
    glad we don’t really have those problems anymore simple smile
  • b

    bored-art-40741

    11/06/2015, 6:54 PM
    We certainly don't have that problem anymore.
  • m

    many-engine-77019

    11/06/2015, 6:55 PM
    yeah it’s been at least, like, a week, since I’ve told someone to delete their .ivy2
  • m

    mammoth-pharmacist-54215

    11/06/2015, 6:56 PM
    not sure what the impact would be in travis if I try and do an integration test that cleans up ivy2 since its not isolated
  • m

    mammoth-pharmacist-54215

    11/06/2015, 6:57 PM
    anyone know of any testing that pokes at the ivy cache at all?
  • r

    rough-minister-58256

    11/06/2015, 6:57 PM
    poison ivy 🌿
  • m

    many-engine-77019

    11/06/2015, 6:57 PM
    you could specify an alternate ivy_settings
  • m

    many-engine-77019

    11/06/2015, 6:57 PM
    that uses an isolated ivy cache
  • m

    many-engine-77019

    11/06/2015, 6:57 PM
    oh wait it’s just ivy cache_dir
  • m

    many-engine-77019

    11/06/2015, 6:57 PM
    I was thinking .m2
  • m

    mammoth-pharmacist-54215

    11/06/2015, 6:59 PM
    I could set the dir to something I don’t care about clobbering in the tests. Was just curious if anyone else ran into this or not.
1...679680681...2420Latest