Skip to content

#28802: Fix typo retires => retries #28816

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

Merged
merged 1 commit into from
Aug 24, 2020
Merged

#28802: Fix typo retires => retries #28816

merged 1 commit into from
Aug 24, 2020

Conversation

medigeek
Copy link
Member

@medigeek medigeek commented Jun 19, 2020

#28802: Fix typo retires => retries

Description (*)

#28802: Fix typo retires => retries

It would fix a typo of bin/magento command line setup:config:set argument/option

$ php bin/magento --help setup:config:set | grep retires
      --session-save-redis-sentinel-connect-retires=SESSION-SAVE-REDIS-SENTINEL-CONNECT-RETIRES  Redis Sentinel connect retries.

Related Pull Requests

Fixed Issues (if relevant)

  1. Fixes typo: setup:config:set --session-save-redis-sentinel-connect-retires (instead of retries) #28802

Manual testing scenarios (*)

Questions or comments

  1. checked for other "retires" occurences. not found.

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • All automated tests passed successfully (all builds are green)

#28802: Fix typo retires => retries
@m2-assistant
Copy link

m2-assistant bot commented Jun 19, 2020

Hi @medigeek. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

  • @magento give me test instance - deploy test instance based on PR changes
  • @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

  • @magento run all tests - run or re-run all required tests against the PR changes
  • @magento run <test-build(s)> - run or re-run specific test build(s)
    For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

  1. Database Compare
  2. Functional Tests CE
  3. Functional Tests EE,
  4. Functional Tests B2B
  5. Integration Tests
  6. Magento Health Index
  7. Sample Data Tests CE
  8. Sample Data Tests EE
  9. Sample Data Tests B2B
  10. Static Tests
  11. Unit Tests
  12. WebAPI Tests

You can find more information about the builds here

ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review.

For more details, please, review the Magento Contributor Guide documentation.

@medigeek
Copy link
Member Author

@magento run all tests

lbajsarowicz
lbajsarowicz previously approved these changes Jun 19, 2020
Copy link
Contributor

@lbajsarowicz lbajsarowicz left a comment

Choose a reason for hiding this comment

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

Thank you for your contribution!

@magento-engcom-team
Copy link
Contributor

Hi @lbajsarowicz, thank you for the review.
ENGCOM-7716 has been created to process this Pull Request
✳️ @lbajsarowicz, could you please add one of the following labels to the Pull Request?

Label Description
Auto-Tests: Covered All changes in Pull Request is covered by auto-tests
Auto-Tests: Not Covered Changes in Pull Request requires coverage by auto-tests
Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests

@magento-engcom-team
Copy link
Contributor

@medigeek thank you for contributing. Please accept Community Contributors team invitation here to gain extended permissions for this repository.

@engcom-Delta
Copy link
Contributor

✔️ QA passed
Before:

  • ❌ Match with incorrect word retires

#28819Main

After:

  • ✔️ No match with incorrect word retires
    #28816PRWithTypo

  • ✔️ Match with correct word retries
    #28816PRWithCorrect

@engcom-Charlie engcom-Charlie self-assigned this Jul 2, 2020
@engcom-Charlie engcom-Charlie added the QA: Ready to add to Regression Scope Should be analyzed and added to Regression Testing Scope(if applicable) label Jul 3, 2020
@engcom-Delta engcom-Delta added QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope and removed QA: Ready to add to Regression Scope Should be analyzed and added to Regression Testing Scope(if applicable) labels Jul 6, 2020
@engcom-Charlie engcom-Charlie added the Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests label Jul 7, 2020
@ghost ghost added Progress: accept Severity: S4 Affects aesthetics, professional look and feel, “quality” or “usability”. labels Jul 7, 2020
@ghost ghost added Priority: P3 May be fixed according to the position in the backlog. and removed Progress: extended testing labels Jul 15, 2020
@sdzhepa
Copy link
Contributor

sdzhepa commented Jul 15, 2020

It looks like BIC changes. Moved to "To Approve" column for review

@ghost ghost dismissed lbajsarowicz’s stale review July 15, 2020 17:08

Pull Request state was updated. Re-review required.

@ihor-sviziev
Copy link
Contributor

Seems like bot moved this PR to wrong status. moved back.

@sidolov
Copy link
Contributor

sidolov commented Aug 21, 2020

@sdzhepa , @ihor-sviziev changing of const value is backward compatible according to our policy:

Changing the value of a constant
Changing the value of a constant is itself a backward compatible change.

Even if client code saves the value in permanent storage or use it as input or output of a method, it is the responsibility of that code to ensure that it is a reliable implementation.

The client code should have enough control over the constant’s value. Do not rely on a value of a constant from another module or another vendor.

@ihor-sviziev
Copy link
Contributor

Fixed wrong status again

@magento-engcom-team
Copy link
Contributor

Hi @ihor-sviziev, thank you for the review.
ENGCOM-7716 has been created to process this Pull Request

@m2-assistant
Copy link

m2-assistant bot commented Aug 24, 2020

Hi @medigeek, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests Cleanup Component: Setup Priority: P3 May be fixed according to the position in the backlog. Progress: accept QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope Release Line: 2.4 Severity: S4 Affects aesthetics, professional look and feel, “quality” or “usability”.
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

typo: setup:config:set --session-save-redis-sentinel-connect-retires (instead of retries)
8 participants