Updated cloud index 404 error #248
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
pandu-k
had a problem deploying
to
py-marqo-test-suite
GitHub Actions
Failure
farshidz
approved these changes
Aug 16, 2024
pandu-k
temporarily deployed
to
py-marqo-test-suite
GitHub Actions
Inactive
Mehul-Porwal
approved these changes
Aug 18, 2024
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.
Tests for the changes have been added (for bug fixes/features)Docs have been added / updated (for bug fixes / features)What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Updating error message
What is the current behavior? (You can also link to an open issue here)
Existing error doesn't take into consideration users may have multiple cloud accounts
What is the new behavior (if this is a feature change)?
New error message asks users to check if the API key matches their index
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No
Other information: