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

Story: Add basic DVC data files support #2

Closed
shcheklein opened this issue Sep 28, 2020 · 2 comments
Closed

Story: Add basic DVC data files support #2

shcheklein opened this issue Sep 28, 2020 · 2 comments
Labels
priority-p1 Regular product backlog story Product feature aka epic. Discussion, progress, checkboxes for implementation, etc

Comments

@shcheklein
Copy link
Member

shcheklein commented Sep 28, 2020

Tickets

TBD

Description

DVC-tracked files are not visible in the tree. Do git clone https://github.com/iterative/example-get-started open it as a project. You won’t see model.plk (defined in the dvc.yaml), you won’t see (data/data.xml) which is defined in the (data/data.dvc)

You need to go into the command line to do basic operations, see status, etc since files are Git ignored.

Steps/features:

  • Make a virtual tree with DVC-tracked files
  • Assign actions per DVC metafiles/DVC-tracked files- pull/push/etc
  • Global actions related to the data management- run dvc pull, dvc checkout, dvc push
@shcheklein shcheklein added story Product feature aka epic. Discussion, progress, checkboxes for implementation, etc priority-p1 Regular product backlog labels Sep 28, 2020
@RandomFractals
Copy link

RandomFractals commented Dec 26, 2020

Guys, I started detailing some of those features in separate tickets:

I also created #43 for us to add dvc extension settings we'd like to add and change per user or vscode workspace.

I think ideally, we want to create custom dvc vscode commands that allow data scientists use dvc via vscode UI without touching a terminal window. Pretty much what gitlens adds for git & since dvc is just git for data we can borrow a lot of commands and tree view setup from that extension to make git and dvc integration similar and seamless in vscode.

I believe those few tickets touch on the major vscode dvc integration points and I can fill in the blanks in the next few days for us to start prototyping them next week.

@mattseddon
Copy link
Member

Replaced by #137

rogermparent added a commit that referenced this issue Apr 14, 2021
* Add "Run Queued Experiments" command

* Add test for "runQueuedExperiments"

* Experiment Commands #3: Add command for `exp gc` with selectable flags (#269)

* Add command for GC

* Change gc to exp gc, and add leading `--` to enum flags

* Add GC command tests and export GC QuickPickItem interface

* Rename exp gc enum entry and reader command

* Change gcExperiments to experimentGarbageCollect

* Replace test() with it() for consistency

* Experiment Commands #4: Addressing comments from 1-3 (#271)

* Change execCommand to resolve to stdout and simplify its consumers

* runDvcCommand => runCommand

* Reorganize command enum to distinguish exp commands with a prefix

* DvcGc => Gc
rogermparent added a commit that referenced this issue Apr 14, 2021
* Add a "Queue Experiments" command

No tests yet, but there is info message functionality which seems to work well.

* Try to make a test for the new queue command

* Re-add failing test

* Move individual test file into index test file

* Use commands enum for queue experiment

* Rename `queue_experiment` enum to follow new allcaps convention

* Experiments Commands #2: Add "Run All Queued Experiments" Command (#268)

* Add "Run Queued Experiments" command

* Add test for "runQueuedExperiments"

* Experiment Commands #3: Add command for `exp gc` with selectable flags (#269)

* Add command for GC

* Change gc to exp gc, and add leading `--` to enum flags

* Add GC command tests and export GC QuickPickItem interface

* Rename exp gc enum entry and reader command

* Change gcExperiments to experimentGarbageCollect

* Replace test() with it() for consistency

* Experiment Commands #4: Addressing comments from 1-3 (#271)

* Change execCommand to resolve to stdout and simplify its consumers

* runDvcCommand => runCommand

* Reorganize command enum to distinguish exp commands with a prefix

* DvcGc => Gc

Co-authored-by: mattseddon <37993418+mattseddon@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority-p1 Regular product backlog story Product feature aka epic. Discussion, progress, checkboxes for implementation, etc
Projects
None yet
Development

No branches or pull requests

3 participants