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

Backfill linkset links to version metadata #4047

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

segiddins
Copy link
Member

So we can complete the migration off of linkset entirely

Next step after this merges & the backfill is run is to completely stop reading/writing linksets

See #1815 for context

@codecov
Copy link

codecov bot commented Sep 5, 2023

Codecov Report

Merging #4047 (e3a07e7) into master (64be113) will increase coverage by 0.00%.
The diff coverage is 100.00%.

❗ Current head e3a07e7 differs from pull request most recent head 6162cec. Consider uploading reports for the commit 6162cec to get more accurate results

@@           Coverage Diff           @@
##           master    #4047   +/-   ##
=======================================
  Coverage   99.01%   99.01%           
=======================================
  Files         268      269    +1     
  Lines        6168     6182   +14     
=======================================
+ Hits         6107     6121   +14     
  Misses         61       61           
Files Changed Coverage Δ
app/models/rubygem.rb 98.71% <100.00%> (ø)
...backfill_linkset_links_to_version_metadata_task.rb 100.00% <100.00%> (ø)

... and 3 files with indirect coverage changes

Copy link
Member

@martinemde martinemde left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Look good. Just curious about only doing home and not every matching link?

"wiki" => "https://example.com/wiki")
end

should "only update the home uri" do
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why only home?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because in the Links model we only use the home uri from the link set when version metadata has uris defined, and ignore all the other links in the link set

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So the home link is the only one that currently falls back, and if there are any URIs already in metadata, they are being ignored right now, so we don't bother to copy them. Then after this we remove that fallback and remove linkset entirely?

Makes sense, thanks for explaining.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah, it's confusing. which is why i think it would be nice to get rid of link set entirely, because of the "sometimes but not always used" situation

So we can complete the migration off of linkset entirely

Next step after this merges & the backfill is run is to completely stop reading/writing linksets
@segiddins segiddins force-pushed the segiddins/backfill-linkset-to-version-metadata branch from e3a07e7 to 6162cec Compare September 11, 2023 18:08
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.

None yet

3 participants