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

exp: include all expected files #8972

Closed
9 tasks done
dberenbaum opened this issue Feb 6, 2023 · 10 comments
Closed
9 tasks done

exp: include all expected files #8972

dberenbaum opened this issue Feb 6, 2023 · 10 comments
Assignees
Labels
A: experiments Related to dvc exp p1-important Important, aka current backlog of things to do

Comments

@dberenbaum
Copy link
Collaborator

dberenbaum commented Feb 6, 2023

There are several issues where files/changes from the workspace end up not being reflected in the experiment. This is a meta-ticket to track those issues:

Tasks

Preview Give feedback
  1. A: experiments bug research
    daavoo
  2. A: experiments
    daavoo
  3. A: experiments p1-important
    daavoo
  4. A: experiments p1-important
    daavoo
  5. A: experiments p1-important
    daavoo
  6. A: dvc p1-important
    daavoo
  7. A: experiments bug p1-important
    daavoo
  8. A: experiments bug p1-important
    daavoo
  9. A: experiments feature request p3-nice-to-have
    daavoo

Edit: reordered to reflect priority

@dberenbaum
Copy link
Collaborator Author

Related: #9165 (comment)

@daavoo
Copy link
Contributor

daavoo commented Mar 24, 2023

Related: #9165 (comment)

Added #9238 to the list

@daavoo
Copy link
Contributor

daavoo commented Mar 30, 2023

Added iterative/dvclive#510 to the list (kind of extracted from #9165 )

@daavoo
Copy link
Contributor

daavoo commented Mar 31, 2023

@dberenbaum I think we are in good shape for getting this done in this sprint, except for #5800 .
I have tried to go through the discussion and its still unclear to me what is the request 😅 Do you recall anything in particular?

@dberenbaum
Copy link
Collaborator Author

Makes sense, thanks @daavoo! Now we are tracking everything that I can think of to reasonably track by default. If there are other files people expect to be included, we could:

  1. Add an option to specify files to copy over.
  2. Copy everything over from the workspace.

I'm torn on whether it's worth prioritizing anything else, but what do you think about including something like 1? Do you think it's easy to add?

@daavoo
Copy link
Contributor

daavoo commented Mar 31, 2023

what do you think about including something like 1?

Sounds good to give the option although it feels like if you have to know about that option + provide the right values you might as well do git add, right?

We could anyhow do something like the exp save --include-untracked

Do you think it's easy to add?

I think so, yes. 1 day.

@dberenbaum
Copy link
Collaborator Author

dberenbaum commented Mar 31, 2023

Sounds good to give the option although it feels like if you have to know about that option + provide the right values you might as well do git add, right?

We could anyhow do something like the exp save --include-untracked

Yeah, I'm not sure that exp save --include-untracked has an obvious use case. The use cases I have in mind are:

  1. Credentials or other sensitive info that shouldn't be tracked by Git (like the OP in term: replace 'DVC-file' and 'stage file' with correct terms (#3960) #5280)
  2. Large files that you don't want to track (for example, it's static or easy to regenerate; see https://github.com/iterative/cse/issues/99)

So I think it needs to be more like --copy-untracked where the files get copied to the tmp dir but remain untracked.

@daavoo
Copy link
Contributor

daavoo commented Mar 31, 2023

So I think it needs to be more like --copy-untracked where the files get copied to the tmp dir but remain untracked.

So, is it about the cases where --tmp / --queue fail because the experiment relies on something that is:

  • Not git tracked
  • Not defined as an absolute path

Correct?


For that, I am not sure about estimation without a clear scope.

@dberenbaum
Copy link
Collaborator Author

So, is it about the cases where --tmp / --queue fail because the experiment relies on something that is:

* Not git tracked

* Not defined as an absolute path

Correct?

Yes

For that, I am not sure about estimation without a clear scope.

I think you just defined the scope very well 😄. Do you still have questions, or you just would need to look closer to give a decent estimation?

@daavoo
Copy link
Contributor

daavoo commented Apr 4, 2023

I think you just defined the scope very well 😄. Do you still have questions, or you just would need to look closer to give a decent estimation?

Forgot to estimate. 1 day was right 😅
I left some questions on the P.R. #9302

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A: experiments Related to dvc exp p1-important Important, aka current backlog of things to do
Projects
None yet
Development

No branches or pull requests

2 participants