Skip to content
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

Unclear that pub build stopped because of conflict of files on disk #861

Closed
DartBot opened this issue Jun 5, 2015 · 2 comments
Closed
Labels
closed-duplicate Closed in favor of an existing report type-enhancement A request for a change that isn't a bug

Comments

@DartBot
Copy link

DartBot commented Jun 5, 2015

<img src="https://avatars.githubusercontent.com/u/5479?v=3" align="left" width="96" height="96"hspace="10"> Issue by sethladd
Originally opened as dart-lang/sdk#16748


Hi,

I tried running pub build, and it stopped before overwriting files. (In my case, I was running dart2js manually to test lazy loading, so my web/ dir had compiled files in it)

Pub build did the right thing, however it's a bit unclear what the error is. I'm wondering if developers new to Dart will understand how to take action. I'd like to propose a strawman for your consideration, in order to help new developers address the issue.

Actual:

Build error:
Transforms {Dart2JS on lazyloadtest|web/lazyloadtest.dart} all emitted asset lazyloadtest|web/lazyloadtest.dart.js.map.
Build error:
Transforms {Dart2JS on lazyloadtest|web/lazyloadtest.dart} all emitted asset lazyloadtest|web/lazyloadtest.dart.precompiled.js.
Build failed.

Can we add:

", but asset was also found on filesystem at [path]. Skipping transform to avoid overwriting file."

(just a strawman)

If you like the idea, I can submit the patch for your consideration. Suggestions for better message very welcome.

Thanks!

@DartBot
Copy link
Author

DartBot commented Jun 5, 2015

<img src="https://avatars.githubusercontent.com/u/188?v=3" align="left" width="48" height="48"hspace="10"> Comment by nex3


Seth, you've been filing a fair number of duplicate issues. This is the second time you've filed an issue for this, for example (see issue #783). Could you try to be more vigilant about searching for existing issues before filing new ones?


Added Duplicate label.
Marked as being merged into dart-archive/barback#18.

@DartBot
Copy link
Author

DartBot commented Jun 5, 2015

<img src="https://avatars.githubusercontent.com/u/5479?v=3" align="left" width="48" height="48"hspace="10"> Comment by sethladd


Apologies. You are correct, I should search for issues before filing them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-duplicate Closed in favor of an existing report type-enhancement A request for a change that isn't a bug
Projects
None yet
Development

No branches or pull requests

1 participant