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

chore(nat): Fix typo in Nat error message #2300

Merged
merged 1 commit into from
May 25, 2024

Conversation

gibson042
Copy link
Contributor

Description

Adds a missing "is" to an error message from Nat.

Security Considerations

None.

Scaling Considerations

n/a

Documentation Considerations

n/a

Testing Considerations

None.

Compatibility Considerations

n/a

Upgrade Considerations

We expect error messages to change over time and require code to be tolerant of this.

@gibson042 gibson042 requested review from kriskowal and erights May 24, 2024 16:18
Copy link
Contributor

@erights erights left a comment

Choose a reason for hiding this comment

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

LGTM thanks.

@erights
Copy link
Contributor

erights commented May 24, 2024

We expect error messages to change over time and require code to be tolerant of this.

Just grepped for "not a safe integer" and verified that none of our endo or agoric-sdk code should have a problem with this change. This change also makes the error more consistent with other errors in agoric-sdk https://github.com/Agoric/agoric-sdk/blob/cc2bf0bb431aa64c601628f53cf191fcc84c5750/packages/ERTP/src/displayInfo.js#L26

@gibson042 gibson042 force-pushed the 2024-05-fix-nat-error-message branch from 9b8be33 to e432313 Compare May 25, 2024 04:28
@gibson042 gibson042 merged commit 8f14465 into master May 25, 2024
17 checks passed
@gibson042 gibson042 deleted the 2024-05-fix-nat-error-message branch May 25, 2024 04:40
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.

2 participants