Stop saving failures to flush jobs in InMemoryConfigStorage to disk #2336
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've found several problems with this approach:
\Google\Cloud\Core\Batch\HandleFailureTrait::initFailureFile
leads to aRuntimeException
when constructing the class.in memory
in the name. This can lead to very unexpected situations, like the disk filling up.google-cloud-batch
is running. This is unexpected to users when theInMemoryConfigStorage
is used - which is a default in the\Google\Cloud\Trace\TraceClient
, for example.What do you think about removing the failure handling features from
InMemoryConfigStorage
?