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

Sync in Stateless mode #575

Closed
antonkorotkov opened this issue Oct 12, 2020 · 2 comments
Closed

Sync in Stateless mode #575

antonkorotkov opened this issue Oct 12, 2020 · 2 comments
Assignees
Milestone

Comments

@antonkorotkov
Copy link
Contributor

While developing background sync we've noticed that Stateless mode works partially. Some files were processed but the whole process has stopped because of the similar error:

[09-Oct-2020 16:20:31 UTC] Background Sync - Media Library Images: Stopped due to error - Unable to open gs://edmstadium-bluehost-temp4/2020/10/2020/10/2020-1003-baytown-houstonraceway-julianbajsel-processed-006.jpg using mode w+: fopen(gs://edmstadium-bluehost-temp4/2020/10/2020/10/2020-1003-baytown-houstonraceway-julianbajsel-processed-006.jpg): failed to open stream: "wpCloud\StatelessMedia\StreamWrapper::stream_open" call failed

I think this is because this specific file was not found on the server and was requested from GCS in order to regenerate metadata.

@antonkorotkov antonkorotkov added this to the v3.1.1 milestone Oct 12, 2020
planv added a commit that referenced this issue Oct 13, 2020
@planv planv modified the milestones: v3.1.1, v3.1.0 Oct 13, 2020
planv added a commit that referenced this issue Oct 13, 2020
planv added a commit that referenced this issue Oct 13, 2020
@antonkorotkov antonkorotkov modified the milestones: v3.1.0, v3.1.1 Oct 14, 2020
planv added a commit that referenced this issue Oct 16, 2020
@planv planv mentioned this issue Oct 20, 2020
planv added a commit that referenced this issue Oct 20, 2020
@antonkorotkov
Copy link
Contributor Author

@planv I see commits tied to this issue but I don't remember whether they fix the exact problem I described in the issue or something else?

@planv
Copy link
Contributor

planv commented Dec 17, 2020

@antonkorotkov Yes, current problem is fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants