Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compiled app errors when loading depencies #927

Closed
biona001 opened this issue Mar 14, 2024 · 2 comments
Closed

Compiled app errors when loading depencies #927

biona001 opened this issue Mar 14, 2024 · 2 comments

Comments

@biona001
Copy link

biona001 commented Mar 14, 2024

I create an app, and it runs fine on my local or remote machines (the remote machine does not have Julia installed).

My collaborator reported a bug, in which the error logs include directories that are native to the local machine I used to compile the app. His operating system is 64bit linux x86, the same as what I used to compile the app.

  • The main error seems to be a dependency issue (I'm calling JLD2.load but somehow it is calling the package FileIO instead, which is somehow an undefined behavior). If all Julia package dependencies are bundled into my app, why would the app run locally and on my remote machine but not on my collaborators machine?
  • Are these "native paths" supposed to exist in my app?
  • What is the recommended way for me, the app author, to debug this? I cannot reproduce the error anywhere, and I am not sure how JLD2, FileIO, or HDF5 (they seem to be the culprits) work internally.

For reference, I compiled my app with the following

using PackageCompiler, GhostKnockoffGWAS
src = normpath(pathof(GhostKnockoffGWAS), "../..")
des = normpath(pathof(GhostKnockoffGWAS), "../../app_linux_x86")
precompile_script = normpath(pathof(GhostKnockoffGWAS), "../precompile.jl")
@time create_app(src, des, 
    include_lazy_artifacts=true, 
    force=true, 
    precompile_execution_file=precompile_script
)
@biona001
Copy link
Author

Well, it seems the paths of the build machine is expected, according to the docs. I'm still not sure why the app runs on some machine but not others, however.

@biona001
Copy link
Author

biona001 commented Mar 29, 2024

Issue resolved by creating a personal fork of those packages and commenting out all Requires.@require in them, see #933 for better description of the issue and in particular this post

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant