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

In core:invalidate-report-data match segments by ID, name or definition ... #16994

Merged
merged 7 commits into from Mar 2, 2021

Conversation

diosmosis
Copy link
Member

Description:

.. and warn when a definition does not match any known segment. When invalidating segments, if it doesn't exactly match the encoding we want, the hash will be wrong and we won't invalidate what we want (and will trigger archiving of a segment we don't want). This change allows better matching and warns in case it doesn't match.

Review

  • Functional review done
  • Usability review done (is anything maybe unclear or think about anything that would cause people to reach out to support)
  • Security review done see checklist
  • Code review done
  • Tests were added if useful/possible
  • Reviewed for breaking changes
  • Developer changelog updated if needed
  • Documentation added if needed
  • Existing documentation updated if needed

@diosmosis diosmosis added the Needs Review PRs that need a code review label Dec 22, 2020
@tsteur tsteur modified the milestones: 4.1.0, 4.2.0 Dec 22, 2020
@diosmosis
Copy link
Member Author

Noticed this could potentially be a BC break for any automated uses of the command (since the user would have to add --yes in that case) so not merging just yet.

@sgiehl sgiehl force-pushed the segment-invalidation-command branch from d6c5ea9 to 50b7e4d Compare January 14, 2021 15:50
@@ -54,6 +62,7 @@ protected function configure()
$this->addOption('dry-run', null, InputOption::VALUE_NONE, 'For tests. Runs the command w/o actually '
. 'invalidating anything.');
$this->addOption('plugin', null, InputOption::VALUE_REQUIRED, 'To invalidate data for a specific plugin only.');
$this->addOption('yes', null, InputOption::VALUE_NONE, 'Assume yes if an unrecognized segment is given.');
Copy link
Member

Choose a reason for hiding this comment

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

Could we maybe clarify this help text as I don't quite get it? could the parameter name be maybe more clear?

Copy link
Member Author

Choose a reason for hiding this comment

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

--ignore-unrecognized-segment? or --quiet/--force?

Copy link
Member Author

@diosmosis diosmosis Feb 19, 2021

Choose a reason for hiding this comment

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

It'd probably be better to just remove the check or make it just print out a warning.

@mattab mattab modified the milestones: 4.2.0, 4.3.0 Feb 22, 2021
@diosmosis diosmosis merged commit 5b07a22 into 4.x-dev Mar 2, 2021
@diosmosis diosmosis deleted the segment-invalidation-command branch March 2, 2021 06:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs Review PRs that need a code review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants