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

Ark: Variable pane can't compute the size in presence of immediate bindings #4700

Open
lionel- opened this issue Sep 17, 2024 · 1 comment
Open
Labels
area: kernels Issues related to Jupyter kernels and LSP servers area: variables Issues related to Variables category. lang: r

Comments

@lionel-
Copy link
Contributor

lionel- commented Sep 17, 2024

Describe the issue:

The variable pane computes the size of objects in the global environments. If those objects contain environments with "immediate bindings", the size computation fails with a warning in the Ark logs.

See the parent issue #4686 and the investigation notes in #4686 (comment). See also the issue in lobstr, from which we pulled our size computation routine: r-lib/lobstr#48

Steps to reproduce the issue:

Run this in the R console:

library(brms)
m <- brm(bf(mpg ~ hp + (1 | cyl), sigma ~ cyl), data = mtcars, seed = 123)

Expected or desired behavior:

No warning in the logs:

[R]   2024-09-17T09:34:59.797038Z  WARN  Can't compute size of object: bad binding access

And the model m should have a non-zero size when the variable pane is sorted by size:

Screenshot 2024-09-17 at 11 32 44
@lionel- lionel- added area: variables Issues related to Variables category. lang: r area: kernels Issues related to Jupyter kernels and LSP servers labels Sep 17, 2024
@petetronic
Copy link
Collaborator

I was able to reproduce this issue, sending to Triage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: kernels Issues related to Jupyter kernels and LSP servers area: variables Issues related to Variables category. lang: r
Projects
None yet
Development

No branches or pull requests

2 participants