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

Set lineage and lineage_hash simultaneously #861

Merged
merged 2 commits into from
Aug 2, 2024
Merged

Conversation

dachengx
Copy link
Collaborator

@dachengx dachengx commented Aug 1, 2024

What is the problem / what does the code in this PR do

It is very dangerous to change the lineage attribute of DataKey because it will make lineage and lineage_hash inconsistent.

So this PR makes sure they are assigned at the same time.

Can you briefly describe how it works?

Can you give a minimal working example (or illustrate with a figure)?

Please include the following if applicable:

  • Update the docstring(s)
  • Update the documentation
  • Tests to check the (new) code is working as desired.
  • Does it solve one of the open issues on github?

Please make sure that all automated tests have passed before asking for a review (you can save the PR as a draft otherwise).

@dachengx dachengx changed the title Make sure lineage of DataKey can not be directly changed Set lineage and lineage_hash simultaneously Aug 1, 2024
@coveralls
Copy link

coveralls commented Aug 1, 2024

Coverage Status

coverage: 90.445% (+0.008%) from 90.437%
when pulling 7b8a72e on static_datakey
into 63100f5 on master.

@dachengx dachengx marked this pull request as ready for review August 2, 2024 07:12
@dachengx dachengx merged commit a58cd5d into master Aug 2, 2024
9 checks passed
@dachengx dachengx deleted the static_datakey branch August 2, 2024 07:12
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