is ngc file still a valid way to copy over controlled files within aws?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 31
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
It is giving me an error about JWT.
I am hoping to use an ngc token instead, since jwt carts expire every hour.
[ec2-user@ip-10-1-0-193 ~]$ sracp --token ~/prj_10324.ngc -a "SRR4307426" /docker_scratch/
SDL API returned error: 500: decode:276 - Invalid JWT - parse:608 - Expected: '{'
List of accessions that failed in this batch:
[SRR4307426]
It seems like none of the accessions were successful, fusera is shutting down.
[ec2-user@ip-10-1-0-193 ~]$
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the sracp entry point that handles the --token argument and follow the request producing the SDL API JWT error. Check whether an NGC token is supported for this AWS file-copy path; done means the reported command works with the token or the supported authentication method is clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go
- Domain
- authentication, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100