-
Notifications
You must be signed in to change notification settings - Fork 7
Fix Aspera key filename to match actual key file #72
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
Conversation
The code was looking for 'aspera_tokenauth_id_rsa' but the actual key file is named 'asperaweb_id_dsa.openssh'. This caused authentication failures when downloading files via Aspera protocol. Fixes authentication prompt issue when using aspera protocol.
WalkthroughThe Aspera private key file path reference was updated from Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches
🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
🔇 Additional comments (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
PR Compliance Guide 🔍Below is a summary of compliance checks for this PR:
Compliance status legend🟢 - Fully Compliant🟡 - Partial Compliant 🔴 - Not Compliant ⚪ - Requires Further Human Verification 🏷️ - Compliance label |
||||||||||||||||||
PR Code Suggestions ✨Explore these optional code suggestions:
|
|||||||||
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.
Pull Request Overview
This PR fixes a critical bug in the Aspera authentication configuration where the code referenced an incorrect key filename, causing authentication failures during file downloads.
Key Changes:
- Corrected the Aspera SSH key filename from
aspera_tokenauth_id_rsatoasperaweb_id_dsa.opensshto match the actual key file in the repository - This resolves password/passphrase prompts that prevented successful Aspera protocol downloads
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
User description
Problem
The code in
files.pywas looking for a key file namedaspera_tokenauth_id_rsa, but the actual key file in the repository is namedasperaweb_id_dsa.openssh.This mismatch caused authentication failures when users tried to download files using the Aspera protocol, resulting in password/passphrase prompts.
Solution
Updated both occurrences in
files.py(lines ~9 and ~172) to use the correct key filename:asperaweb_id_dsa.opensshTesting
pridepy download-file-by-name -a PXD004683 -f 20150820_Haura-Pilot-TMT2-bRPLC06-2.raw -o ~/pride_data/ -p asperaFiles Changed
pridepy/files/files.py: Changed key filename fromaspera_tokenauth_id_rsatoasperaweb_id_dsa.openssh(2 locations)PR Type
Bug fix
Description
Fixed Aspera key filename mismatch causing authentication failures
Updated key path from
aspera_tokenauth_id_rsatoasperaweb_id_dsa.opensshResolves password/passphrase prompts during Aspera protocol downloads
Diagram Walkthrough
File Walkthrough
files.py
Correct Aspera key filename in download methodpridepy/files/files.py
download_files_from_asperamethodaspera_tokenauth_id_rsatoasperaweb_id_dsa.opensshprotocol
Summary by CodeRabbit