-
Notifications
You must be signed in to change notification settings - Fork 72
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
FileAlreadyExistsException when worker tries to save scenario .json from S3 #483
Comments
Perhaps this is related to the new In the previous release (v4.1.1), scenario application was blocking. For example,
|
Just discussed this with @ansoncfit and we found the source of the problem: I had added a line to resolveScenario (current line 444) which used Files.copy() instead of ByteStreams.copy, but didn't remove ByteStreams.copy. So the file was being copied twice. I am putting it back the way it was before - the Files.copy change is probably a good idea but will need to be done in a release that will be fully tested. |
🎉 This issue has been resolved in version 4.5.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Note that this error will not occur if a worker has used the scenario for a single-point analysis (and therefore already has the scenario-applied network cached). Completing a regional task with one worker that ran a single-point analysis, and a second worker that was launched subsequently, can lead to striped scenario/non-scenario accessibility results:
The text was updated successfully, but these errors were encountered: