-
Notifications
You must be signed in to change notification settings - Fork 16
fix: directory detection with remote executor #60
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
Open
gilbsgilbs
wants to merge
1
commit into
snakemake:main
Choose a base branch
from
gilbsgilbs:fix-directories-detection
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
Verify boto3 error codes for
s3obj().load().The error code checks compare against
"400"and"404"strings. However, boto3'sClientError.response["Error"]["Code"]typically returns semantic error codes (e.g.,"NoSuchKey","BadRequest") rather than HTTP status codes. Please verify thats3obj().load()actually returns these numeric string codes, or update to check the appropriate error codes.🏁 Script executed:
Length of output: 610
🌐 Web query:
💡 Result:
404 Not Found: boto3 raises a botocore.exceptions.ClientError whose e.response['Error']['Code'] is usually "404" (and S3 may also return "NoSuchKey"). [1][2]
400 Bad Request: boto3 raises ClientError with e.response['Error']['Code'] equal to "400" (or a more specific S3 error code such as "BadRequest", "InvalidArgument", "AuthorizationHeaderMalformed", etc., depending on the exact problem). [2][3]
Sources:
[1] Stack Overflow: examples showing e.response['Error']['Code'] == '404' or 'NoSuchKey'.
[2] AWS S3 HeadObject / Error responses (lists 404/400 behaviors and NoSuchKey / various 4xx error codes).
[3] Boto3 head_object docs (HEAD can return generic 400/403/404 codes).
Handle "NoSuchKey" error code for missing S3 objects.
While boto3 does return "404" and "400" numeric strings as shown in the code, S3 also returns semantic error codes. Most critically, missing objects typically return
"NoSuchKey"instead of"404". The current code only checks for numeric codes, so it won't catch the"NoSuchKey"case and will incorrectly re-raise the exception when the object doesn't exist.Add a check for
"NoSuchKey"alongside the"404"check:Additionally, line 335 uses
raise ewhich should be justraiseto preserve the original traceback.🧰 Tools
🪛 Ruff (0.14.4)
326-331: Avoid specifying long messages outside the exception class
(TRY003)
335-335: Use
raisewithout specifying exception nameRemove exception name
(TRY201)
🤖 Prompt for AI Agents