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

Catch lack of increment before calling next step in filter1d #8035

Merged
merged 2 commits into from
Nov 13, 2023

Conversation

PaulWessel
Copy link
Member

See #8029 for some background. Problem was our example left out an actual increment and also did not catch the error, leading to many meaningless error message. Now, with -Tk+a (no increment) we get the clean error:

filter1d [ERROR]: No distance argument given, only unit.
gmt [ERROR]: Error parsing filter1d options

See #8029 for some background.  Problem was our example left out an actual increment and also did not catch the error, leading to many meaningless error message.  Now, with -Tk+a (no increment) we get the clean error:

filter1d [ERROR]: No distance argument given, only unit.
gmt [ERROR]: Error parsing filter1d options
@PaulWessel PaulWessel added the bug Something isn't working label Nov 13, 2023
@PaulWessel PaulWessel added this to the 6.5.0 milestone Nov 13, 2023
@PaulWessel PaulWessel self-assigned this Nov 13, 2023
@PaulWessel PaulWessel merged commit a9e2f39 into master Nov 13, 2023
6 checks passed
@PaulWessel PaulWessel deleted the array-inc-check branch November 13, 2023 12:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants