search

fonsp / Pluto.jl

🎈 Simple reactive notebooks for Julia
https://plutojl.org/
MIT License
4.91k stars 284 forks source link

"more" buttons not expanding previews #2795

Closed simonsteiger closed 5 months ago

simonsteiger commented 5 months ago

Thank you for all the great work on Pluto! I enjoy working with the notebooks sooo much! 🎈

After updating packages recently (Pluto 0.19.36 -> 0.19.37), I cannot expand vectors anymore by clicking on the "more" button. It gets stuck loading. It did however work in the release notebook hosted on binder (beautiful art!). I have tried removing the Pluto package and reinstalling it, but this did not help. Below are a screen recording, a notebook, and the terminal output of the issue.

Screen recording https://github.com/fonsp/Pluto.jl/assets/106233551/08ec2f15-ef02-433d-b53b-d46411daf0bc

Pluto notebook https://gist.github.com/simonsteiger/a2461cf25091344c5765dea1f3d4ca64

Terminal output

┌ Warning: Response function to message of type :reshow_cell failed
â”” @ Pluto ~/.julia/packages/Pluto/h22mT/src/webserver/WebServer.jl:410
┌ Warning: Processing message failed for unknown reason:
│   parentbody =
│    Dict{Any, Any} with 5 entries:
│      "client_id"   => "1hgakma"
│      "body"        => Dict{Any, Any}("cell_id"=>"2968eb27-c778-437f-b23b-c125…
│      "request_id"  => "15m1oa9"
│      ⋮             => ⋮
│   exception =
│    MethodError: no method matching Pluto.PlutoDependencyExplorer.ExprAnalysisCache(::Pluto.Notebook, ::Pluto.Cell)
│    
│    Closest candidates are:
│      Pluto.PlutoDependencyExplorer.ExprAnalysisCache(::Any, ::Any, ::Any, ::Any, ::Any)
│       @ Pluto ~/.julia/packages/Pluto/h22mT/src/analysis/PlutoDependencyExplorer/Topology.jl:5
│    
│    Stacktrace:
│      [1] response_reshow_cell(🙋::Pluto.ClientRequest)
│        @ Pluto ~/.julia/packages/Pluto/h22mT/src/webserver/Dynamic.jl:524
│      [2] process_ws_message(session::Pluto.ServerSession, parentbody::Dict{Any, Any}, clientstream::HTTP.WebSockets.WebSocket)
│        @ Pluto ~/.julia/packages/Pluto/h22mT/src/webserver/WebServer.jl:408
│      [3] (::Pluto.var"#382#392"{Pluto.ServerSession})(clientstream::HTTP.WebSockets.WebSocket)
│        @ Pluto ~/.julia/packages/Pluto/h22mT/src/webserver/WebServer.jl:215
│      [4] upgrade(f::Pluto.var"#382#392"{Pluto.ServerSession}, http::HTTP.Streams.Stream{HTTP.Messages.Request, HTTP.Connections.Connection{Sockets.TCPSocket}}; suppress_close_error::Bool, maxframesize::Int64, maxfragmentation::Int64, kw::@Kwargs{})
│        @ HTTP.WebSockets ~/.julia/packages/HTTP/bDoga/src/WebSockets.jl:440
│      [5] upgrade
│        @ ~/.julia/packages/HTTP/bDoga/src/WebSockets.jl:420 [inlined]
│      [6] (::Pluto.var"#381#391"{Pluto.ServerSession, Pluto.var"#278#280"{Pluto.var"#281#283"{HTTP.Handlers.Router{typeof(Pluto.default_404), typeof(HTTP.Handlers.default405), Nothing}}, Pluto.ServerSession}})(http::HTTP.Streams.Stream{HTTP.Messages.Request, HTTP.Connections.Connection{Sockets.TCPSocket}})
│        @ Pluto ~/.julia/packages/Pluto/h22mT/src/webserver/WebServer.jl:196
│      [7] #invokelatest#2
│        @ ./essentials.jl:887 [inlined]
│      [8] invokelatest
│        @ ./essentials.jl:884 [inlined]
│      [9] handle_connection(f::Function, c::HTTP.Connections.Connection{Sockets.TCPSocket}, listener::HTTP.Servers.Listener{Nothing, Sockets.TCPServer}, readtimeout::Int64, access_log::Nothing)
│        @ HTTP.Servers ~/.julia/packages/HTTP/bDoga/src/Servers.jl:450
│     [10] (::HTTP.Servers.var"#16#17"{Pluto.var"#381#391"{Pluto.ServerSession, Pluto.var"#278#280"{Pluto.var"#281#283"{HTTP.Handlers.Router{typeof(Pluto.default_404), typeof(HTTP.Handlers.default405), Nothing}}, Pluto.ServerSession}}, HTTP.Servers.Listener{Nothing, Sockets.TCPServer}, Set{HTTP.Connections.Connection}, Int64, Nothing, Base.Semaphore, HTTP.Connections.Connection{Sockets.TCPSocket}})()
│        @ HTTP.Servers ~/.julia/packages/HTTP/bDoga/src/Servers.jl:386
â”” @ Pluto ~/.julia/packages/Pluto/h22mT/src/webserver/WebServer.jl:222
simonsteiger commented 5 months ago

Ah, sorry! I only see now that #2791 concerns the same issue. Checked a few days ago if the issue had been reported and did not make sure to check again before filing the issue right now. This can be closed with #2791 then.