syntax change in offelia scheduler #840
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Utilize newly allocated space in production(backup) #836
Actually I didnt find any mistake in the previous code logic .
In some commands ,there was missing space in the ending before closing of bracket .If there is no space before the closing bracket in a bash script, such as in a test expression like [ -d /path/to/directory], it will result in a syntax error. Bash expects a space before the closing bracket (]) to properly interpret the condition. Without this space, bash will fail to recognize the correct end of the condition, leading to a syntax error when the script is executed.