Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

"RPC timed out" followed by complete session freeze after attempting to unfold large sf data.frame object #5869

Closed
dblodgett-usgs opened this issue Jan 2, 2025 · 3 comments
Assignees
Labels
area: variables Issues related to Variables category. bug Something isn't working lang: r support

Comments

@dblodgett-usgs
Copy link

System details:

Positron and OS details:

Positron Version: 2024.12.0 (user setup) build 96
Code - OSS Version: 1.93.0
Commit: c5ce275
Date: 2024-11-28T02:53:40.010Z
Electron: 30.4.0
Chromium: 124.0.6367.243
Node.js: 20.15.1
V8: 12.4.254.20-electron.0
OS: Windows_NT x64 10.0.22631

Interpreter details:

R 4.4.2

Describe the issue:

Working with very large sf data.frame objects, where there is a special list column containing spatial geometry in the variables pane is currently not scaling well.

Steps to reproduce the issue:

Create a too-large data.frame:

nc <- sf::read_sf(system.file("shape/nc.shp", package="sf"))

big_nc <- sf::st_sf(data.table::rbindlist(lapply(1:10000, \(x) nc)))

Attempt to unroll big_nc in the variables pane to see names and types.

Observe the following:

Image

Once I get that error, the session remains unresponsive until I kill the session and restart.

NOTE: If I create a 100k row table, this work but are sluggish -- somewhere between 100k and 1M rows, things go sideways.

Expected or desired behavior:

If an object is too large to function with the variables pane, functionality that may not complete should not be called at all.

@juliasilge juliasilge added bug Something isn't working area: variables Issues related to Variables category. lang: r support labels Jan 6, 2025
@juliasilge
Copy link
Contributor

juliasilge commented Jan 6, 2025

Thanks for this report @dblodgett-usgs! 🙌 We did some recent work improving the behavior of the Variables pane but apparently it did not address this category of problem. I also observe an error related to the kernel supervisor:

Image

From:

Positron Version: 2025.01.0 (Universal) build 147
Code - OSS Version: 1.95.0
Commit: 4c10da4
Date: 2025-01-03T02:45:49.456Z
Electron: 32.2.1
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Darwin arm64 24.2.0

@dfalbel
Copy link
Contributor

dfalbel commented Feb 11, 2025

This has been fixed with posit-dev/ark#702. See also #6220

@testlabauto
Copy link
Contributor

Verified Fixed

Positron Version(s) : 2025.03.0-24
OS Version          : OSX

Test scenario(s)

Found what I hope is shape/nc.shp with a google search. Tried to repro with original filing instructions and things look good.

Link(s) to TestRail test cases run or created:

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
area: variables Issues related to Variables category. bug Something isn't working lang: r support
Projects
None yet
Development

No branches or pull requests

4 participants