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

Compiling Query results in errors #191

Closed
shaktee opened this issue Aug 21, 2018 · 5 comments
Closed

Compiling Query results in errors #191

shaktee opened this issue Aug 21, 2018 · 5 comments

Comments

@shaktee
Copy link

shaktee commented Aug 21, 2018

I am trying to use Query with the latest julia, and get these errors.

[ Info: Precompiling Query [1a8c2f83-1ff3-5112-b086-8aa67b057ba1]
ERROR: LoadError: UndefVarError: start not defined
Stacktrace:
 [1] getproperty(::Module, ::Symbol) at ./sysimg.jl:13
 [2] top-level scope at none:0
 [3] include at ./boot.jl:317 [inlined]
 [4] include_relative(::Module, ::String) at ./loading.jl:1038
 [5] include(::Module, ::String) at ./sysimg.jl:29
 [6] top-level scope at none:2
 [7] eval at ./boot.jl:319 [inlined]
 [8] eval(::Expr) at ./client.jl:389
 [9] top-level scope at ./none:3
in expression starting at /home/rv/.julia/packages/NamedTuples/MIrnh/src/NamedTuples.jl:16
ERROR: LoadError: Failed to precompile NamedTuples [73a701b4-84e1-5df0-88ff-1968ee2ee8dc] to /home/rv/.julia/compiled/v1.1/NamedTuples/SN1pr.ji.
Stacktrace:
 [1] error(::String) at ./error.jl:33
 [2] macro expansion at ./logging.jl:313 [inlined]
 [3] compilecache(::Base.PkgId, ::String) at ./loading.jl:1184
 [4] _require(::Base.PkgId) at ./logging.jl:311
 [5] require(::Base.PkgId) at ./loading.jl:852
 [6] require(::Module, ::Symbol) at ./logging.jl:311
 [7] include at ./boot.jl:317 [inlined]
 [8] include_relative(::Module, ::String) at ./loading.jl:1038
 [9] include(::Module, ::String) at ./sysimg.jl:29
 [10] top-level scope at none:2
 [11] eval at ./boot.jl:319 [inlined]
 [12] eval(::Expr) at ./client.jl:389
 [13] top-level scope at ./none:3
in expression starting at /home/rv/.julia/packages/Query/VIFkY/src/Query.jl:4
ERROR: Failed to precompile Query [1a8c2f83-1ff3-5112-b086-8aa67b057ba1] to /home/rv/.julia/compiled/v1.1/Query/wGX7b.ji.
Stacktrace:
 [1] error(::String) at ./error.jl:33
 [2] macro expansion at ./logging.jl:313 [inlined]
 [3] compilecache(::Base.PkgId, ::String) at ./loading.jl:1184
 [4] macro expansion at ./logging.jl:311 [inlined]
 [5] _require(::Base.PkgId) at ./loading.jl:941
 [6] require(::Base.PkgId) at ./loading.jl:852
 [7] require(::Module, ::Symbol) at ./logging.jl:311

julia> versioninfo()
Julia Version 1.1.0-DEV.74
Commit f0146c7e6e (2018-08-21 02:24 UTC)
Platform Info:
  OS: Linux (x86_64-linux-gnu)
  CPU: AMD Ryzen 7 1800X Eight-Core Processor
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-6.0.0 (ORCJIT, znver1)

@sidravi1
Copy link

+1

Same issue here. I raised an issue with NamedTuples.jl since it is trying to load NamedTuples: JuliaData/NamedTuples.jl#75

But the conclusion is that NamedTuples is not supported for Julia 1.0

Here's my version info:

julia> versioninfo()
Julia Version 1.0.0
Commit 5d4eaca0c9 (2018-08-08 20:58 UTC)
Platform Info:
  OS: macOS (x86_64-apple-darwin14.5.0)
  CPU: Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-6.0.0 (ORCJIT, skylake)

and package status:

(v1.0) pkg> status
    Status `~/.julia/environments/v1.0/Project.toml`
  [c52e3926] Atom v0.7.3
  [336ed68f] CSV v0.3.1
  [a93c6f00] DataFrames v0.13.1
  [38e38edf] GLM v0.11.0
  [28b8d3ca] GR v0.32.3
  [7073ff75] IJulia v1.9.3
  [699e389a] IntroToJulia v0.0.0 [`~/.julia/dev/IntroToJulia`]
  [42fd0dbc] IterativeSolvers v0.7.1
  [e5e0dc1b] Juno v0.5.2
  [6f286f6a] MultivariateStats v0.5.0
  [58dd65bb] Plotly v0.1.1
  [f0f68f2c] PlotlyJS v0.10.2
  [91a5bcdd] Plots v0.19.3
  [1a8c2f83] Query v0.9.3
  [189a3867] Reexport v0.2.0
  [1986cc42] Unitful v0.11.0
  [0f1e0344] WebIO v0.3.1

@davidanthoff
Copy link
Member

Julia 0.7/1.0 is almost done, but not yet finished, I'm on it!

@lewisl
Copy link

lewisl commented Aug 26, 2018

You can't close it if a commit has not been made with the fixes, at least for testing. It's not closed until resolved fixed or resolved as not a bug or resolved will not be fixed.

@davidanthoff
Copy link
Member

Well, I can close whatever I want to :) 0.7 compat is tracked in the PR that has 0.7 compat in it. Beyond that there is nothing to do.

@lewisl
Copy link

lewisl commented Aug 27, 2018 via email

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

4 participants