501 on catalog retrieval if OpenSanctions is not reachable#876
Closed
501 on catalog retrieval if OpenSanctions is not reachable#876
Conversation
apognu
added
enhancement
Pascal-Delange
approved these changes
Mar 7, 2025
Contributor
Author
|
@carere We will merge this after the release, did you handle the 501 response code from the frontend yet? |
Contributor
|
Good thing to tag me since I did not know that you implemented a 501 response code 😉 |
Contributor
|
@apognu shall we merge ? |
Contributor
Author
|
Well, I don't know if handling was implemented on the frontend, yet. :/ |
carere
force-pushed
the
feat/sanctions/unimplemented-on-dataset-error
branch
from
4969cd7 to
1f9efe0
Compare
Contributor
|
I handle this after new case manager is finished |
This file contains hidden or 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
3 participants
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.
No description provided.