Displaying 20 results from an estimated 2000 matches similar to: "normalizePath is sometimes very slow for nonexistent UNC paths"
2020 Mar 23
2
Inconsistant result for normalizePath on Windows
Hi all,
I saw a quite surprising result in the devel R when using the function
*normalizePath*. If the input is a path to a folder, the function returns
an absolute path with/without a slash at the end depending on the existence
of the folder. I know both results are valid on Windows but this behavior
is different than R3.6, I do not know if the change in the devel version is
made on purpose.
2015 Mar 11
1
normalizePath output depends on existence of directory
Dear all,
I'm not sure whether this is intended behaviour or a bug. The path returns
from normalizePath is different when the directory doesn't exist. I have
included a reproducible example.
path <- tempfile()
missing.dir <- normalizePath(path, winslash = "/", mustWork = FALSE)
dir.create(path)
existing.dir <- normalizePath(path, winslash = "/", mustWork =
2017 May 17
3
problem running test on a system without /etc/localtime
Hi all,
A problem with tests while building R.
I'm packaging R for Sisyphus repository and package build environment,
by design, doesn't have /etc/localtime file present. This causes failure
with Sys.timeone during test run:
[builder at localhost tests]$ ../bin/R --vanilla < reg-tests-1d.R
> ## PR#17186 - Sys.timezone() on some Debian-derived platforms
> (S.t <-
2017 May 17
1
problem running test on a system without /etc/localtime
>>>>> Henrik Bengtsson <henrik.bengtsson at gmail.com>
>>>>> on Tue, 16 May 2017 20:49:02 -0700 writes:
> On Tue, May 16, 2017 at 5:35 PM, Kirill Maslinsky <kirill at altlinux.org> wrote:
>> Hi all,
>>
>> A problem with tests while building R.
>>
>> I'm packaging R for Sisyphus repository
2011 Aug 11
2
UNC windows path beginning with backslashes: normalizePath bug??
Hi,
Back in June I posted the message below, but had no replies. I've made a
little progress since then so this is to update anyone interested (!) and to
ask for comments.
Brief problem statement:
Under Windows, some parts of R don't handle UNC paths beginning with
backslashes. Specifically
a) Sys.glob() fails to find some files breaking (e.g.) Rcmdr plugins
2019 Jan 24
1
Bug or undocumented behavior in normalizePath() with file system links on windows
Hello,
I discovered a bug or undocumented behavior in normalizePath
steps to reproduce:
execute normalizePath on a folder link on windows. When you are on a
non-english windows box, you likely have links in place for windows'
default folders, e.g. "C:\Programme" linking to "C:\Program Files" on
german windows boxes.
Thus executing
2020 Mar 23
0
Inconsistant result for normalizePath on Windows
Hi Jiefei,
the change in handling trailing path separators is not on purpose, but
is a byproduct of a new implementation of normalizePath, which now
handles symbolic links and normalizes case in long path names. It is not
documented what happens to trailing separators, and hence portable
programs should not depend on it. I don't think it is a property that
should be documented/specified.
2023 Feb 27
1
Undocumented change of dirname("C:/") on R-devel on Windows
Hi Tomas,
There has been an R CMD check error with xfun and r-devel on Windows for a
while:
https://www.r-project.org/nosvn/R.check/r-devel-windows-x86_64/xfun-00check.html
Basically it means that the following would return TRUE before:
normalizePath('a/b', mustWork = FALSE) == normalizePath('./a/b', mustWork
= FALSE)
but it became FALSE at some point in r-devel. I think
2011 Sep 14
3
normalizePath
Hi,
I update R from 2.10 to 2.13.
Then I find soma problems when I start R.
Warning infos as below:
#####
Warning message:
In normalizePath(c(new, .Library.site, .Library), "/") :
path[1]="": No such file or directory
R version 2.13.1 (2011-07-08)
Copyright (C) 2011 The R Foundation for Statistical Computing
ISBN 3-900051-07-0
Platform: x86_64-pc-linux-gnu (64-bit)
R is
2013 Jul 02
2
cache most-recent dispatch
Hi,
S4 method dispatch can be very slow. Would it be reasonable to cache the
most
recent dispatch, anticipating the next invocation will be on the same
type? This
would be very helpful in loops.
fun0 <- function(x)
sapply(x, paste, collapse="+")
fun1 <- function(x) {
paste <- selectMethod(paste, class(x[[1]]))
sapply(x, paste,
2016 Nov 17
2
problem with normalizePath()
The packages "readxl" and "haven" (and possibly others) no longer access files on shared network drives. The problem appears to be in the normalizePath() function. The file can be read from a local drive or by functions that don't call normalizePath(). The error thrown is
Error: path[1]="\\Hzndhhsvf2/data/OCPH/EPI/BHSDM/Group/17.xls": The system cannot find the
2013 Apr 27
3
path reference problems in R 3.0.0
Hi-
I just upgraded R to 3.0.0 from 2.15.1 (which worked fine). When I started
trying to install updated versions of the libraries, I saw the following
error:
> install.packages("lme4")
Installing package into 'c:/Docume~1/melissa/R/win-library/3.0'
(as 'lib' is unspecified)
Warning in install.packages :
Suggestion/opinions: add a `absolute` param to `normalizePath()` to force returning an absolute path
2020 Apr 14
4
Suggestion/opinions: add a `absolute` param to `normalizePath()` to force returning an absolute path
This request stems off a bug report I posted
https://bugs.r-project.org/bugzilla/show_bug.cgi?id=17757 where it was
determined the current behaviour is as expected.
To recap: when given a real file, normalizePath() always* returns the full
absolute path. When given a non-existent file, normalizePath() returns a
full path on Windows but it returns the input on other systems*. I'd argue
that
2016 Nov 30
1
problem with normalizePath()
I found this as well. At our institution, our home directories are on
network shares that are mapped to local drives. The default, it appears, is
to set the location for libraries (etc) to the network share name
(//computer//share/director/a/b/user) rather than the local drive mapping
(H:/). Given the issue with dir.create(), this means it's impossible to
install packages (since it tries to
2016 Nov 18
2
problem with normalizePath()
>>>>> Evan Cortens <ecortens at mtroyal.ca>
>>>>> on Thu, 17 Nov 2016 15:51:03 -0700 writes:
> I wonder if this could be related to the issue that I
> submitted to bugzilla about two months ago? (
> https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=17159)
> That is to say, could it be that it's treating the first
>
2011 May 02
1
Problems with Rterm 2.13.0 - but not RGui
Hi all,
I have just installed R 2.13.0 and I am experiencing problems with the terminal, but not the with the GUI interface.
I am Windows 7.
When running "R" or "Rterm" from a commandline I receive the following:
Warning message:
In normalizePath(path.expand(path), winslash, mustWork) :
path[3]="C:/Programmer/R/R-2.13.0/library": Adgang n?gtet
R version 2.13.0
2010 Sep 09
1
Error in normalizePath(path) : with McAfee
Dear R People:
I keep getting the "Error in normalizePath(path) :" while trying to
obtain the necessary packages to use with the "Applied Spatial
Statistics with R" book.
I turned off the Firewall (from McAfee) but am still getting the same message.
Does anyone have any idea on a solution please?
> sessionInfo()
R version 2.11.1 (2010-05-31)
i386-pc-mingw32
locale:
[1]
2006 Jun 12
1
normalizePath() warning
I've been getting the following warning after running 'install.packages()' recently:
Warning message:
insufficient OS support on this platform in: normalizePath(path)
Does anyone know what this means? And does anyone know how I can get rid of the
warning? I've just installed R on a fresh FC5 system so I feel I might have
forgotten to install a package/library or something.
2008 Oct 23
1
normalizePath bug (PR#13199)
Full_Name: Joseph Haykov
Version: 2.8.0
OS: Windows
Submission from: (NULL) (216.189.177.202)
normalizePath("C:\\DOCUME~1\\JOSEPH~1\\LOCALS~1\\Temp\\RtmpolZ4Vy\\file72ae2cd6.txt")
returns: "\0354xl|\a\001?$v\001?y8"
instead of returning:
"C:\\Documents and Settings\\Joseph Haykov\\Local
Settings\\Temp\\RtmpolZ4Vy\\file72ae2cd6.txt"
By the way, this
2011 May 31
1
how to tell if two file paths refer to the same file
Does R have a standard function that takes two file paths
(e.g., "./myDirectory/file" and "myDirectory/file")
and returns TRUE if those paths refer to the same file?
The paths make take different routes ("absolute" or
relative paths or via different symbolic or hard links)
to the same file or may use different naming conventions
(Windows or DOS 8.3 on Windows). If