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

Deterministic Order in Notices Generator #1833

Closed
3 tasks done
radeusgd opened this issue Jul 7, 2021 · 0 comments · Fixed by #1891
Closed
3 tasks done

Deterministic Order in Notices Generator #1833

radeusgd opened this issue Jul 7, 2021 · 0 comments · Fixed by #1891
Labels
d-easy Difficulty: little prior knowledge required p-lowest Should be completed at some point

Comments

@radeusgd
Copy link
Member

radeusgd commented Jul 7, 2021

Summary

The legal review tool generates notices summarizing all copyright mentions from our dependencies.

Currently, the order in which these mentions end up in the summary is unspecified and it seems to differ depending on some unknown variables.

This task would consist of ensuring that the order is actually deterministic.

The fact that the order varies is not at all a problem from the perspective of validity of the report - it just must contain all the mentions. However, as the order sometimes changes after running the legal review tool, it pollutes PRs with meaningles changes (reordering of the entries in the summary).

Value

  • The deterministic order will mean PRs will not be polluted with meaningles changes to the legal review report.

Specification

  • Ensure that the order of copyright mentions in the report is deterministic. Probably can be achieved just by sorting the mentions lexicographically.

Acceptance Criteria & Test Cases

  • Regenerate and commit the 'determinized' legal review report.
  • Make sure that the change did not introduce errors into the report generator.
@radeusgd radeusgd added Category: Build d-easy Difficulty: little prior knowledge required p-lowest Should be completed at some point labels Jul 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
d-easy Difficulty: little prior knowledge required p-lowest Should be completed at some point
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant