Pluto.jl: Tables.jl object not triggering Pluto table viewer

The attached notebook (see also below) defines a geotable, which is a Tables.jl object. The Pluto’s built-in table viewer is not being triggered:

image

Can you help understand why that is the case?

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 29 (3 by maintainers)

Most upvoted comments

For some reason, in the environment you’re running Pluto it’s true (but it’s not really true). What are you importing in parallel with pluto (in the session you’re doing Pluto.run())?

I am running Pluto from a global environment with OhMyREPL.jl, PkgDependency.jl and other utility packages that are not loaded in the Pluto session itself. @eliascarv could also reproduce the issue in his own computer with a different environment than mine.

Is the tutorial going to be available online? I’d like to take a look!

It will be a video tutorial, I will share it on YouTube 😃 Unfortunately the data is too large to share in a repository this time.

I ran this notebook on Pluto v0.19.6 and I found this error message: image

Yes, the issue is still valid with the latest release.

Em qua., 23 de nov. de 2022 03:21, Παναγιώτης Γεωργακόπουλος < @.***> escreveu:

Hey @juliohm https://github.com/juliohm ! Is this still happening on Pluto 0.19.16? We did apply some fix 🤔

— Reply to this email directly, view it on GitHub https://github.com/fonsp/Pluto.jl/issues/2309#issuecomment-1324604695, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAZQW3KSXLRDN5VKXFCZ6XDWJWZV7ANCNFSM6AAAAAARCEYO64 . You are receiving this because you were mentioned.Message ID: <fonsp/Pluto .@.***>

This is my global env:

(@v1.8) pkg> st
Status `C:\Users\Dev01\.julia\environments\v1.8\Project.toml`
  [6e4b80f9] BenchmarkTools v1.3.1
  [5fb14364] OhMyREPL v0.5.12
  [c3e4b0f8] Pluto v0.19.14
  [295af30f] Revise v3.4.0

@pankgeorg anything I can do to help? A video chat where I try a few things in front of you? I am planning a tutorial where the table viewer would be very didactic.

Maybe it is related to the name of the columns in the table? The logic implemented in that PR assumes ascii column names? I noticed that whenever I introduce Greek letters as column names the viewer is not triggered.