Skip to content

Conversation

@sudo-suhas
Copy link
Contributor

If 0 retry is specified via configuration file, do not override it with
default of 5. Only if the configuration is skipped, default to 5.

Example 1 - meteor.yml:

LOG_LEVEL: info
MAX_RETRIES: 5

retries = 5.

Example 2 - meteor.yml:

LOG_LEVEL: info
MAX_RETRIES: 0

retries = 0.

Example 3 - meteor.yml:

LOG_LEVEL: info

retries = 5.

If 0 retry is specified via configuration file, do not override it with
default of 5. Only if the configuration is skipped, default to 5.

Example 1 - meteor.yml:

    LOG_LEVEL: info
    MAX_RETRIES: 5

retries = 5.

Example 2 - meteor.yml:

    LOG_LEVEL: info
    MAX_RETRIES: 0

retries = 0.

Example 3 - meteor.yml:

    LOG_LEVEL: info

retries = 5.
@StewartJingga StewartJingga merged commit 45073e7 into main Aug 29, 2022
@StewartJingga StewartJingga deleted the allow-0-retry branch August 29, 2022 07:24
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.

fix: sink retry log not showing unit of time and the correct level

3 participants