Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Nov 02 07:12
    kevinresol commented #168
  • Nov 02 06:45
    back2dos commented #168
  • Oct 29 04:57
    kevinresol opened #168
  • Oct 08 12:09
    back2dos commented #167
  • Oct 06 21:10
    sebthom opened #167
  • Sep 28 17:07
    gene-pavlovsky opened #166
  • Sep 14 20:21
    MasterEric opened #72
  • Sep 11 14:00

    kevinresol on master

    Quote download location to work… Merge pull request #165 from se… (compare)

  • Sep 11 14:00
    kevinresol closed #165
  • Sep 11 14:00
    kevinresol closed #162
  • Sep 11 14:00
    kevinresol commented #165
  • Sep 11 13:59
    kevinresol commented #165
  • Sep 11 13:59
    kevinresol review_requested #165
  • Sep 02 10:51
    sebthom commented #165
  • Sep 02 10:51
    sebthom opened #165
  • Aug 31 17:02

    dependabot[bot] on npm_and_yarn

    (compare)

  • Aug 31 17:02
    dependabot[bot] closed #161
  • Aug 31 17:02
    dependabot[bot] commented #161
  • Aug 31 17:02
    dependabot[bot] labeled #164
  • Aug 31 17:02
    dependabot[bot] opened #164
Thomas J. Webb
@thomasjwebb
sPoOoOoKy
Juraj Kirchheim
@back2dos
haxe --run resolve-args ${HAXE_LIBCACHE} should point you to a sub-directory of where lix puts its stuff
from there it's ../neko
Thomas J. Webb
@thomasjwebb
that gives me empty line
Juraj Kirchheim
@back2dos
oO
ok, what OS are you on? ^^
Thomas J. Webb
@thomasjwebb
macos
Juraj Kirchheim
@back2dos
and do you have ~/haxe/neko?
Thomas J. Webb
@thomasjwebb
I do. Ah mac uses zsh now that could be the issue..
I mean for the blank line not neko being old
Juraj Kirchheim
@back2dos
ah ... right ^^
Thomas J. Webb
@thomasjwebb
Yup escaping the curly braces worked
Juraj Kirchheim
@back2dos
yeah ... haha ... I hate operating systems ...
ok, well then just delete ~/haxe/neko and that should make lix pull a fresh version
Thomas J. Webb
@thomasjwebb
yeah I keep forgetting that. zsh is actually pretty powerful but it's like not truly compatible with bash.
bam it's downloading
Juraj Kirchheim
@back2dos
I hope it's the right version now :D
Thomas J. Webb
@thomasjwebb
Yeah that fixed it. Thanks! So this shouldn't be an issue on deploy servers and such since they don't have this already there crap baggage
Juraj Kirchheim
@back2dos
but I think I bumped it almost two years ago ^^
yeah, normally only early adopters should be facing this problem on their machines ... only the cool kids!
Thomas J. Webb
@thomasjwebb
Yeah I installed lix globally more recently than that on this machine, but it's possible I accidentally let it install an old haxe version even though I've been using 4 since it was in rc stage
Philippe
@elsassph
Oh hi, I'm trying to do haxelib run formatter ... with lix but fail miserably
Juraj Kirchheim
@back2dos
hmm, formatter 1.11.0 + lix 15.9.0 seem to work just fine for me
can you illustrate your misery any further? ^^
Philippe
@elsassph
I must not understand how to map haxelib run formatter ... to lix.
Closest to something which almost works is lix run-haxelib . formatter ... which fails with
Unknown command run-dir
Haxe Library Manager 3.3.0 ...
I have latest lix / latest haxe as far as I can tell
Juraj Kirchheim
@back2dos
hmm, seems like a precedence thing
lix formatter and lix run formatter should work for global lix
but so should haxelib run formatter
Juraj Kirchheim
@back2dos
here's a fully isolated setup: mkdir foo && cd foo && npm init -y && npm i lix && npx lix scope create && npx lix install haxelib:formatter && npx lix formatter
works for me even if I have no lix installed and whether or not I have haxe and haxelib installed globally through the normal installer .. can you try that please?
Philippe
@elsassph
Hmm ok so lix formatter works when run as a npm script, but not in the terminal.
VSCode's integrated terminal. And scoped lix. Not adding npx if that matters.
Well that matters visibly :D
Juraj Kirchheim
@back2dos
lix formatter should work if and only if you've install lix via npm i -g lix
Philippe
@elsassph
I'd have thought that a global lix running in a scoped location would figure things out...
Juraj Kirchheim
@back2dos
hmm, ordinarily it does, but as always, there's a dozen things that can go wrong
tbh, I don't even understand how you managed to get lix and nonshimmed haxelib in the same $PATH (as your output fromlix run-haxelib . formatter indicates) ... that takes a quite peculiar setup ... are you throwing npm-haxe in the mix or something? ^^
Philippe
@elsassph
Haha no it's a clean lix setup. But I may have an old static install of haxe.
Philippe
@elsassph
Got a very interesting issue in CI: I forgot lix download and when building I got
haxelib path: /root/haxe/versions/4.1.2/haxelib: error while loading shared libraries: libneko.so.2: cannot open shared object file: No such file or directory
Juraj Kirchheim
@back2dos
where's haxelib from in that case?
Philippe
@elsassph
I dont know, I just ran npx haxe build.hxml which contains -lib. It's a clean Node docker image and lix only downloaded Haxe.
Juraj Kirchheim
@back2dos
ok, I managed to repro that ;)
Kevin Leung
@kevinresol
how to use git: protocol to fetch a particular branch?
tried lix install --flat git:https://gitlab.com/<org>/<repo>.git\#<branch> but gave me Cannot resolve version <branch>
Kevin Leung
@kevinresol
my bad, i forgot to actually push the branch to remote
so it is now able to resolve the SHA but unable to download:
downloading git:https://gitlab.com/<org>/<repo>.git#<sha>
From https://gitlab.com/<org>/<repo>
 * branch              HEAD       -> FETCH_HEAD
fatal: reference is not a tree: <sha>
Juraj Kirchheim
@back2dos
oh, wow, cool ... can you give details on how to repro that? Andre from innogames asked me about this, but he had solved it by killing his library cache and a clean install worked
Juraj Kirchheim
@back2dos
can you check the repo in ~/haxe/haxe_libraries/.gitrepos or similar?