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

Clean up address errors #2087

Merged
merged 1 commit into from
Sep 4, 2024

Conversation

wizeguyy
Copy link
Member

@wizeguyy wizeguyy commented Sep 3, 2024

Resolves #1994

@jdowning100
Copy link
Contributor

when data is requested for an address that is not in the correct shard, indicate which shard the address is in, and which shard you are requesting data from

Is this supposed to be in this PR?

@wizeguyy
Copy link
Member Author

wizeguyy commented Sep 4, 2024

@jdowning100 no. We decided against it. Elsewhere in the codebase we switch on that error message. Making the error message dynamic would break those places.

Refactoring those places to switch on some other logic also isn't trivial, because they did not have access to the operating context, etc. Spoke with @Juuddi about it and decided that error message was not worth the effort.

@wizeguyy wizeguyy merged commit 15de623 into dominant-strategies:main Sep 4, 2024
@wizeguyy wizeguyy deleted the address-scope-errors branch September 4, 2024 15:00
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.

Make address not in scope error more verbose
4 participants