unioslo / unioslo/tsd-api-client
Handle upload sync passed for initial transfers
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 17
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Currently tacl will fail on attempted tacl --upload-sync if the base directory doesn't exist remotely.
$ tacl p11 --env test --upload-sync dist
uploading directory dist
fetching information about directory: dist
405 Client Error: Method not allowed for url: https://test.api.tsd.usit.no/v1/p11/files/stream/p11-member-group/dist?per_page=10000
The request was unsuccesful. Exiting.
I think 405 method not allowed for upload sync should be interpreted as a signal to try switching to normal uploading (we could also create the remote base directory and "sync", but I don't think there's any point in using the sync code path for an initial upload).
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 by tracing the tacl --upload-sync command handling and how a 405 response is processed when the remote base directory is missing. Done means an initial upload no longer fails on this response and instead proceeds through normal uploading; verify with the command shown in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100