Skip to content
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

[FEATURE]: "Improve dlp-cli Debugging with Directory Check Warning" #1149

Open
codingwithsurya opened this issue Mar 16, 2024 · 2 comments
Open
Labels
enhancement New feature or request

Comments

@codingwithsurya
Copy link
Contributor

Feature Name

Add pre-installation check logging to dlp-cli to advise on removing the existing miniforge3/envs/dlp directory to prevent conflicts.

Your Name

Surya Subramanian

Description

When attempting to reinstall or update the backend using dlp-cli backend install, if the miniforge3/envs/dlp directory already exists, it can lead to issues that are not immediately apparent to the user. This scenario can cause confusion and slow down the debugging process.

It would be beneficial for the dlp-cli tool to include a logging statement before attempting the installation or update process that checks for the existence of the miniforge3/envs/dlp directory. If found, the tool should log a clear message advising the user to remove or rename the existing directory to prevent potential conflicts. A suggested message could be:

  • [WARNING] The 'miniforge3/envs/dlp' directory already exists. To avoid potential conflicts, please consider removing this directory before reinstalling the backend.

Adding this feature would improve user experience by making the debugging process more straightforward and reducing the time spent identifying common installation issues.

@codingwithsurya codingwithsurya added the enhancement New feature or request label Mar 16, 2024
Copy link
Contributor

Hello @codingwithsurya! Thank you for submitting the Feature Request Form. We appreciate your contribution. 👋

We will look into it and provide a response as soon as possible.

To work on this feature request, you can follow these branch setup instructions:

  1. Checkout the main branch:
```
 git checkout nextjs
```
  1. Pull the latest changes from the remote main branch:
```
 git pull origin nextjs
```
  1. Create a new branch specific to this feature request using the issue number:
```
 git checkout -b feature-1149
```

Feel free to make the necessary changes in this branch and submit a pull request when you're ready.

Best regards,
Deep Learning Playground (DLP) Team

@karkir0003
Copy link
Member

@codingwithsurya update on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Backlog
Development

No branches or pull requests

2 participants