Skip to content

fix: cloned material that exceeds limits #195

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

Merged
merged 2 commits into from
Aug 23, 2019

Conversation

seebees
Copy link
Contributor

@seebees seebees commented Aug 20, 2019

It is possible for material that is created in the caching CMM to immediately exceed the caching limits. In this case the materials clearly should not be cached, but also they should not be cloned.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Check any applicable:

  • Were any files moved? Moving files changes their URL, which breaks all hyperlinks to the files.

It is posible for material that is created in the caching CMM
to imidialy exced the caching limits.
In this case the materials clearly should not be cached,
but also they should not be cloned.
@seebees seebees requested a review from a team August 20, 2019 16:57
@seebees seebees merged commit cd002d5 into aws:master Aug 23, 2019
@seebees seebees deleted the caching-cmm-returning-cloned-material branch August 23, 2019 22:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants