runGist in Windows about shiny HOT 14 CLOSED

Hmmm, I didn't think it would be necessary. Unfortunately I don't have a
Windows XP setup handy to test on. Can you set options(error=recover) and
then try calling runGist again, and when it errors, go to the innermost
frame and see what the value of appDir is? And whether that path exists or
not?

Thanks.

from shiny.

appDir is getting redirected somehow through my user temp folder and cygwin warning is getting appended:

appdir
"C:/DOCUME~1/knowlje/LOCALS~1/Temp/RtmpAbFJAs/cygwin warning:"
dirname
"cygwin warning:"

I also tried on Windows 7 and got the same error.

I have Rtools installed in both cases, and I am wondering if there is a problem somehow with compatibility with the Rtools toolchain and shiny.

I tried an older version of R without the devtools configured and it didn't work, but maybe I need to completely remove Rtools first, and see if that clears up the issue?

from shiny.

I don't think the Rtools copy of untar would issue that warning. Is it possible that you have Cygwin's bin directory appearing before Rtools' bin directory in your path? If so, can you define an environment variable TAR that points to the Rtools' copy of tar.exe?

from shiny.

I don't think so. The XP machine does not have Cygwin installed--just
Rtools. But I could try to define an environment variable that explicitly
points to "tar.exe" and see if that works. Not quite sure how to do that to
make sure I am getting it right.

On Tue, Nov 13, 2012 at 5:42 PM, Joe Cheng [email protected] wrote:

I don't think the Rtools copy of untar would issue that warning. Is it
possible that you have Cygwin's bin directory appearing before Rtools' bin
directory in your path? If so, can you define an environment variable TAR
that points to the Rtools' copy of tar.exe?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/38#issuecomment-10349090.

from shiny.

Can you try this command?

system("where tar")

Does that give you the rtools version of tar?

On Tue, Nov 13, 2012 at 3:44 PM, Jared Knowles [email protected]:

I don't think so. The XP machine does not have Cygwin installed--just
Rtools. But I could try to define an environment variable that explicitly
points to "tar.exe" and see if that works. Not quite sure how to do that
to
make sure I am getting it right.

On Tue, Nov 13, 2012 at 5:42 PM, Joe Cheng [email protected]
wrote:

I don't think the Rtools copy of untar would issue that warning. Is it
possible that you have Cygwin's bin directory appearing before Rtools'
bin
directory in your path? If so, can you define an environment variable
TAR
that points to the Rtools' copy of tar.exe?

—
Reply to this email directly or view it on GitHub<
https://github.com/rstudio/shiny/issues/38#issuecomment-10349090>.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/38#issuecomment-10349150.

from shiny.

Windows XP doesn't seem to support system("where tar"), but
Sys.getenv("TAR") comes up with an empty directory...

On Tue, Nov 13, 2012 at 5:50 PM, Joe Cheng [email protected] wrote:

Can you try this command?

system("where tar")

Does that give you the rtools version of tar?

On Tue, Nov 13, 2012 at 3:44 PM, Jared Knowles [email protected]:

I don't think so. The XP machine does not have Cygwin installed--just
Rtools. But I could try to define an environment variable that
explicitly
points to "tar.exe" and see if that works. Not quite sure how to do that
to
make sure I am getting it right.

On Tue, Nov 13, 2012 at 5:42 PM, Joe Cheng [email protected]
wrote:

I don't think the Rtools copy of untar would issue that warning. Is it
possible that you have Cygwin's bin directory appearing before Rtools'
bin
directory in your path? If so, can you define an environment variable
TAR
that points to the Rtools' copy of tar.exe?

—
Reply to this email directly or view it on GitHub<
https://github.com/rstudio/shiny/issues/38#issuecomment-10349090>.

—
Reply to this email directly or view it on GitHub<
https://github.com/rstudio/shiny/issues/38#issuecomment-10349150>.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/38#issuecomment-10349338.

from shiny.

Interesting. How about system("tar --version") ?

from shiny.

That returns the Rtools version of TAR.

On Tue, Nov 13, 2012 at 6:02 PM, Joe Cheng [email protected] wrote:

Interesting. How about system("tar --version") ?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/38#issuecomment-10349665.

from shiny.

Wow. Well, I'm stumped. Let me see if I can get my hands on a Win XP setup
to test it for myself.

from shiny.

I'll keep tweaking as well. Between my Win7 rig and my XP rig maybe I can
isolate the problem. Curious if others see this issue too.

from shiny.

I played around with it by trying to step through the runGist function myself (the beauty of open source) and it seems like even if I change the way filePath is specified and don't use tempfile (which on some Windows boxes might go to a folder without write access sometimes I think), untar still failed with the error message above. I hope that helps to narrow it down. Let me know what else I can do!

from shiny.

Is untar just broken on your machine? Can you try untar-ing any old .tar.gz
file? For example,
http://www.rstudio.org/_packages/src/contrib/shiny_0.1.9.tar.gz

from shiny.

No, that works just fine on both the Win7 and WinXP machines. It has something to do with the the way tarfile is passed to untar I think.

from shiny.

This is fixed in Shiny 0.1.12. Thanks!

from shiny.