-
Notifications
You must be signed in to change notification settings - Fork 231
Showstopper Error in corporate environment under Win 7 #893
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
Comments
<img src="https://avatars.githubusercontent.com/u/5449880?v=3" align="left" width="48" height="48"hspace="10"> Comment by iposva-google cc @munificent. |
<img src="https://avatars.githubusercontent.com/u/8616782?v=3" align="left" width="48" height="48"hspace="10"> Comment by clayberg Set owner to @keertip. |
<img src="https://avatars.githubusercontent.com/u/2192312?v=3" align="left" width="48" height="48"hspace="10"> Comment by keertip @moru0011, Are you able to run pub from command line after setting the proxy vars? |
This comment was originally written by [email protected] No, it tells me "\rdev\DFSRoot$\home\moelrue\Application seems like the setup of the home drives confused pub. Maybe the project is confused (started with 1.0 and I upgraded 2014-03-04 23:27 GMT+01:00 <[email protected]>: |
<img src="https://avatars.githubusercontent.com/u/2192312?v=3" align="left" width="48" height="48"hspace="10"> Comment by keertip Bob, sorry to bounce this over, but it looks like a pub issue. Set owner to @munificent. |
<img src="https://avatars.githubusercontent.com/u/46275?v=3" align="left" width="48" height="48"hspace="10"> Comment by munificent Unfortunately, pub currently relies on creating symlinks. Windows doesn't support those on network shares, so the workaround is to move your pub cache to a local directory. You can configure that by setting a PUB_CACHE environment variable to point to the local directory where packages should be installed. We're actively working to move away from using symlinks at all, but there are a very large number of moving parts involved in that change so it will take a while. |
This comment was originally written by [email protected] Well, consider moving this to IDE options, so it gets visible to a user. I 2014-04-02 19:36 GMT+02:00 <[email protected]>: |
<img src="https://avatars.githubusercontent.com/u/188?v=3" align="left" width="48" height="48"hspace="10"> Comment by nex3 There's not really a good alternative option for a default place to put the cache. We need something that we can consistently find without any configuration, and it needs to be persistent, so TEMP doesn't work. It sounds like the home directory isn't a good fit for your environment, but that's why it's configurable. |
This comment was originally written by [email protected] agree its annoying. I have worked as a contractor in insurance and finance, 2014-04-02 20:41 GMT+02:00 <[email protected]>: |
<img src="https://avatars.githubusercontent.com/u/46275?v=3" align="left" width="48" height="48"hspace="10"> Comment by munificent Thank you for the feedback! |
Originally opened as dart-lang/sdk#17178
This issue was originally filed by [email protected]
What steps will reproduce the problem?
\rdev\DFSRoot$\home\moelrue\Application Data\Pub\Cache\hosted\pub.dartlang.org\browser-0.9.0\lib of Link.create on Windows cannot be converted to start with a drive letter. Unexpected error., path = ''
It seems like dart is ressolving the full path of a "virtual home" drive first and then cannot map back. However it acknoledges the proxy vars.
I cannot build/update from DartEditor, because it completely fails with proxy.
This is a serious issue, we cannot use Dart this way. Even worse, DartEditor additonally does not support our RH6.5 Linux boxes, so we are screwed on Windoze and Linux platforms.
The software setup as described is very standard to larger companies (at least here in europe) from what I have seen (i am a consultant).
Consider this much more important than adding fancy features. I could imagine this seriously hampers commercial use of Dart.
The text was updated successfully, but these errors were encountered: