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

[v2int/7.0] Port #17841 (GC: Do not throw when loading a DDS that is Inactive or Tombstoned) #17984

Merged

Conversation

markfields
Copy link
Member

Port #17841 to release/v2int/7.0

…icrosoft#17841)

Some early adopters of GC are utilizing the `allowTombstone` header (and
something similar for InactiveObject) to take control of how they
interact with Tombstoned objects.

They found that while this technique allows them to get at a
DataStore-level object, there are some flows where that triggers the
load of a DDS via handle.get, which fails.

And since GC Mark happens at DataStore granularity, we are no longer
going to enforce Tombstone (or Inactive) state when directly loading a
DDS. (Implication is that an app trying to leverage Tombstone state will
miss out on this detection if ever a DDS is loaded directly before its
DataStore was loaded).
@markfields markfields requested review from a team as code owners October 25, 2023 20:26
@msfluid-bot
Copy link
Collaborator

Could not find a usable baseline build with search starting at CI 42f7dab

Generated by 🚫 dangerJS against 48a5eaa

@markfields markfields merged commit c943983 into microsoft:release/v2int/7.0 Oct 25, 2023
@markfields markfields deleted the v2int/7.0/gc/allow-ts-dds branch October 25, 2023 21:07
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.

3 participants