deepset-ai / deepset-ai/deepset-cloud-sdk
Store CLI logs in a logfile locally
Open
Nobody has claimed this yet.
enhancement
feature:upload
- Dominant language
- Python
- Stars
- 16
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
We want users to be able to investigate what went wrong during their upload. This can help to identify potential local or deepset Cloud issues also after "some files didn't show up in dC".
Therefore we want to:
- store logs locally (create logger to simultaneously dump to logfiles/tmp dir)
- print log to the path at the end of the process
Contributor guide
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 from the CLI upload process and trace how its logs are currently emitted. Add local logging under a logfiles/tmp directory and print the resulting logfile path when the process ends. Done means upload failures leave a local logfile that users can locate after the command completes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, observability
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100