We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I failed to build a website using quarto using Parsers v2.5.7 with the following error message:
An error occurred while executing the following cell: ------------------ using CSV using DataFrames csv_path = joinpath("working_directory", "data", "scope_0.csv") df = CSV.read(csv_path, DataFrame, header = [1,2]) ------------------ MethodError: no method matching iterate(::Parsers.Token) Closest candidates are: iterate(::Union{LinRange, StepRangeLen}) at /usr/local/julia/share/julia/base/range.jl:826 iterate(::Union{LinRange, StepRangeLen}, ::Integer) at /usr/local/julia/share/julia/base/range.jl:826 iterate(::T) where T<:Union{Base.KeySet{<:Any, <:Dict}, Base.ValueIterator{<:Dict}} at /usr/local/julia/share/julia/base/dict.jl:695 ... Stacktrace: [1] indexed_iterate(I::Parsers.Token, i::Int64) @ Base ./tuple.jl:92 [2] checkcommentandemptyline(buf::Vector{UInt8}, pos::Int64, len::Int64, cmt::Any, ignoreemptyrows::Bool, nlines::Base.RefValue{Int64}) @ CSV ~/.julia/packages/CSV/jFiCn/src/detection.jl:276 [3] skiptorow(buf::Vector{UInt8}, pos::Int64, len::Int64, oq::Parsers.Token, eq::UInt8, cq::Parsers.Token, cmt::Any, ignoreemptyrows::Bool, cur::Int64, dest::Int64) @ CSV ~/.julia/packages/CSV/jFiCn/src/detection.jl:191 [4] detectcolumnnames(buf::Vector{UInt8}, headerpos::Int64, datapos::Int64, len::Int64, options::Parsers.Options, header::Any, normalizenames::Bool) @ CSV ~/.julia/packages/CSV/jFiCn/src/detection.jl:178 [5] CSV.Context(source::CSV.Arg, header::CSV.Arg, normalizenames::CSV.Arg, datarow::CSV.Arg, skipto::CSV.Arg, footerskip::CSV.Arg, transpose::CSV.Arg, comment::CSV.Arg, ignoreemptyrows::CSV.Arg, ignoreemptylines::CSV.Arg, select::CSV.Arg, drop::CSV.Arg, limit::CSV.Arg, buffer_in_memory::CSV.Arg, threaded::CSV.Arg, ntasks::CSV.Arg, tasks::CSV.Arg, rows_to_check::CSV.Arg, lines_to_check::CSV.Arg, missingstrings::CSV.Arg, missingstring::CSV.Arg, delim::CSV.Arg, ignorerepeated::CSV.Arg, quoted::CSV.Arg, quotechar::CSV.Arg, openquotechar::CSV.Arg, closequotechar::CSV.Arg, escapechar::CSV.Arg, dateformat::CSV.Arg, dateformats::CSV.Arg, decimal::CSV.Arg, truestrings::CSV.Arg, falsestrings::CSV.Arg, stripwhitespace::CSV.Arg, type::CSV.Arg, types::CSV.Arg, typemap::CSV.Arg, pool::CSV.Arg, downcast::CSV.Arg, lazystrings::CSV.Arg, stringtype::CSV.Arg, strict::CSV.Arg, silencewarnings::CSV.Arg, maxwarnings::CSV.Arg, debug::CSV.Arg, parsingdebug::CSV.Arg, validate::CSV.Arg, streaming::CSV.Arg) @ CSV ~/.julia/packages/CSV/jFiCn/src/context.jl:392 [6] #File#25 @ ~/.julia/packages/CSV/jFiCn/src/file.jl:221 [inlined] [7] read(source::String, sink::Type; copycols::Bool, kwargs::Base.Pairs{Symbol, Vector{Int64}, Tuple{Symbol}, NamedTuple{(:header,), Tuple{Vector{Int64}}}}) @ CSV ~/.julia/packages/CSV/jFiCn/src/CSV.jl:91 [8] top-level scope @ In[4]:5 [9] eval @ ./boot.jl:373 [inlined] [10] include_string(mapexpr::typeof(REPL.softscope), mod::Module, code::String, filename::String) @ Base ./loading.jl:1196 LoadError: MethodError: no method matching iterate(::Parsers.Token) Closest candidates are: iterate(::Union{LinRange, StepRangeLen}) at /usr/local/julia/share/julia/base/range.jl:826 iterate(::Union{LinRange, StepRangeLen}, ::Integer) at /usr/local/julia/share/julia/base/range.jl:826 iterate(::T) where T<:Union{Base.KeySet{<:Any, <:Dict}, Base.ValueIterator{<:Dict}} at /usr/local/julia/share/julia/base/dict.jl:695
Installing Parsers v2.3.2 fixed the failure. Pipeline failure
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I failed to build a website using quarto using Parsers v2.5.7 with the following error message:
Installing Parsers v2.3.2 fixed the failure. Pipeline failure
The text was updated successfully, but these errors were encountered: