You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
R version 4.4.0 (2024-04-24 ucrt) -- "Puppy Cup"
Copyright (C) 2024 The R Foundation for Statistical Computing
Platform: x86_64-w64-mingw32/x64
Describe the issue:
If I select a bunch of lines and submit them at once, the result reported in the console doesn't always follow the same sequence as the lines submitted. This is different than the behavior in RStudio. "Source file" does follow the sequence. Possibly related to #4068 ?
Steps to reproduce the issue:
this script consistently does it for me. Select all then submit as a single chunk (ctrl-enter if using RStudio shortcuts).
print("end block")
[1] "start block"
[1] "mid block"
Reading layer nc' from data source F:\softwareInstalls\R_packages\sf\shape\nc.shp' using driver `ESRI Shapefile'
Simple feature collection with 100 features and 14 fields
Geometry type: MULTIPOLYGON
Dimension: XY
Bounding box: xmin: -84.32385 ymin: 33.88199 xmax: -75.45698 ymax: 36.58965
Geodetic CRS: NAD27
[1] "end block"
Driver: ESRI Shapefile
Available layers:
layer_name geometry_type features fields crs_name
1 nc Polygon 100 14 NAD27
2 olinda1 Polygon 470 6 GRS 1980(IUGG, 1980)
3 storms_xyz 3D Line String 71 0
4 storms_xyzm Measured Line String 71 0
5 storms_xyzm_feature Measured Line String 71 1
6 storms_xyz_feature 3D Line String 71 1
[1] 4
Which shows the "st_layers" and "2+2" lines reporting back from the Console last.
Expected or desired behavior:
I would have expected "st_layers" result to show before the results from the commands that come after it. This is the way it behaves in RStudio and when the file is sourced.
Were there any error messages in the UI, Output panel, or Developer Tools console?
no errors that I see, but I didn't look far.
The text was updated successfully, but these errors were encountered:
Related to #1762 and #1326. I think the right fix here is to submit these as individual statements and wait for each one to run to completion before running the next one. That will remove any possibility of their output getting tangled up.
System details:
Positron and OS details:
Positron Version: 2024.08.0 (system setup) build 5
Code - OSS Version: 1.91.0
Commit: Unknown
Date: 2024-08-06T16:06:18.274Z
Electron: 29.4.0
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Windows_NT x64 10.0.19045
Interpreter details:
R version 4.4.0 (2024-04-24 ucrt) -- "Puppy Cup"
Copyright (C) 2024 The R Foundation for Statistical Computing
Platform: x86_64-w64-mingw32/x64
Describe the issue:
If I select a bunch of lines and submit them at once, the result reported in the console doesn't always follow the same sequence as the lines submitted. This is different than the behavior in RStudio. "Source file" does follow the sequence. Possibly related to #4068 ?
Steps to reproduce the issue:
this script consistently does it for me. Select all then submit as a single chunk (ctrl-enter if using RStudio shortcuts).
This is what I get:
text version of output:
[1] "start block"
[1] "mid block"
Reading layer
nc' from data source
F:\softwareInstalls\R_packages\sf\shape\nc.shp' using driver `ESRI Shapefile'Simple feature collection with 100 features and 14 fields
Geometry type: MULTIPOLYGON
Dimension: XY
Bounding box: xmin: -84.32385 ymin: 33.88199 xmax: -75.45698 ymax: 36.58965
Geodetic CRS: NAD27
[1] "end block"
Driver: ESRI Shapefile
Available layers:
layer_name geometry_type features fields crs_name
1 nc Polygon 100 14 NAD27
2 olinda1 Polygon 470 6 GRS 1980(IUGG, 1980)
3 storms_xyz 3D Line String 71 0
4 storms_xyzm Measured Line String 71 0
5 storms_xyzm_feature Measured Line String 71 1
6 storms_xyz_feature 3D Line String 71 1
[1] 4
Which shows the "st_layers" and "2+2" lines reporting back from the Console last.
Expected or desired behavior:
I would have expected "st_layers" result to show before the results from the commands that come after it. This is the way it behaves in RStudio and when the file is sourced.
Were there any error messages in the UI, Output panel, or Developer Tools console?
no errors that I see, but I didn't look far.
The text was updated successfully, but these errors were encountered: