Fix not throw exception #59
Open
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
Signed-off-by: Etienne LESOT <etienne.lesot@rte-france.com>
etiennehomer
changed the title
etiennehomer
approved these changes
Jan 16, 2025
EtienneLt
changed the title
EtienneLt
commented
Jan 17, 2025
| @@ -63,7 +63,7 @@ public class S3CaseService implements CaseService { | |||
| private static final Logger LOGGER = LoggerFactory.getLogger(S3CaseService.class); | |||
| public static final int MAX_SIZE = 500000000; | |||
| public static final List<String> COMPRESSION_FORMATS = List.of("bz2", "gz", "xz", "zst"); | |||
| public static final List<String> ARCHIVE_FORMATS = List.of("zip"); | |||
| public static final List<String> ARCHIVE_FORMATS = List.of("zip", "tar"); | |||
There was a problem hiding this comment.
to remove it is in another pr
Signed-off-by: Etienne LESOT <etienne.lesot@rte-france.com>
|
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.
Please check if the PR fulfills these requirements
Does this PR already have an issue describing the problem?
What kind of change does this PR introduce?
What is the current behavior?
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change or deprecate an API?
If yes, please check if the following requirements are fulfilled
What changes might users need to make in their application due to this PR? (migration steps)
Other information: