-
-
Notifications
You must be signed in to change notification settings - Fork 70
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
double sync #57
Comments
@lsanders the log you provided is showing the two steps used to sync, so that is expected. If you've changed the bucket prefix, then the files may still be in place from a previous deploy. Can you please verify that you've deleted the files from the root and then re-sync. If the problem persists either @k1LoW or I can try to replicate it and then work out the bug. |
I have the same issue as the OP. With the below configuration I get the contents of
|
@k1LoW It does indeed appear this is a real issue. If |
Thank you all !! Now I'm lowering the development priority of this library. If you are able to resolve this, we would encourage you to send a pull request. |
This looks closed by the merge of #94 |
I have just a single budket/prefix defined, but end up the the files from build in both the root AND the bucketPrefix and have the following log in serverless deploy
Here's the relevant config:
This deployed via bitbucket pipelines but I don't think that matters.
The text was updated successfully, but these errors were encountered: