-
Notifications
You must be signed in to change notification settings - Fork 205
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
"Cannot overwrite inputs" #175
Comments
That is definitely weird, but I can't seem to reproduce it (using the example in the built_json package). I tried switching back and forth between both the build and watch options as well. Do you know of any consistent repro steps? |
fwiw, you might be able to just delete your |
I just got to a repro, I think. And it's on a clean clone of the repo, so I assume deleting
Edit pubspec.yaml: delete the dependency on
Then:
Wait for initial source gen to finish. Then open Add new field to the
Save. Then immediately after that, add another field:
Save. The build process should go into an infinite loop, complaining about |
Hmm, I tried doing that but it doesn't seem to be reproing for me :(. Maybe its a mac/windows issue? Are you on one of those platforms? |
Yes, this is on a Mac.
…On Jan 25, 2017 09:42, "Jacob MacDonald" ***@***.***> wrote:
Hmm, I tried doing that but it seems to be reproing for me :(. Maybe its a
mac/windows issue? Are you on one of those platforms?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#175 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA4Ipcw-urGNW4M-PWwDiWRF5g7Ibakgks5rV4mGgaJpZM4LrSWA>
.
|
Ok, I will try it out on my mac later tonight then and see if I can get a repro going. |
Can I run it in some kind of verbose mode that would help you? |
You can pass a custom log If you pipe the output to a file it will also be a bit better since when its logging to a terminal it overwrites info messages to keep down on the spam. |
Ok, I can definitely reproduce this on my mac, taking a look. |
Thanks! Let me know if you want me to proceed with the logging.Level.ALL approach. (I assume you can get more useful info yourself since you can reproduce.) |
Ya I can take it from here, will let you know if I need anything else. |
…#185) As a part of a normal build, invalidated outputs are deleted at the start, causing a `delete` event to be captured by the watcher. This ensures that those delete events are not tracked as real edits, and don't cause an infinite loop of builds. In practice on linux the add events for the files being recreated were coming through fast enough that we were ignoring the delete events anyways, but on mac it was consistently not happening that way (the add event came through to late for some files, after we started the next build).
This should be resolved, but you will need to update to build_runner version |
When running the watcher for a while, it starts failing with "Cannot overwrite inputs."
The thing is that this file (
actor.g.dart
) is generated. It's not an input, at least not to my understanding. Here's my setup.This did not happen when I had a Watcher set up in IntelliJ (that watcher just ran build instead of watch). That worked well but it was also way too slow. So I thought I'd rather run build's watcher in a terminal. That's when I started encountering the problem.
The text was updated successfully, but these errors were encountered: