tree 86260c88e3fc288fd9bba534a47728eadc0ef4bb
parent c54a302495a560d19fe0a9df1d78b3947c7aabcc
author Jens Johansen <jensj@google.com> 1528985169 +0000
committer commit-bot@chromium.org <commit-bot@chromium.org> 1528985169 +0000

Fix continue in invalidation logic

When invalidating changed files in frontend server, the state prior to
this CL was that a continue would jump to the next byte, not the next file
after it had seen that the file had changed. Thus it could possibly
invalidate the same file several times.

Change-Id: If6fb1042248d26a3ffe905b39fa3c3603198ca37
Reviewed-on: https://dart-review.googlesource.com/60245
Commit-Queue: Jens Johansen <jensj@google.com>
Reviewed-by: Aske Simon Christensen <askesc@google.com>