-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Outputs as target supporting for dvc status
#4433
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we push this to
Stage::status()
orStage::_status_outs
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, we should keep
{stage_name: stage_status}
format, to make it in line with--show-json
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We give misinformation that there is only one output "alice" in stage "alice_bob", here we need more emphasis on outputs than stages.
Maybe we can discuss the output format more in #2180?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@karajan1001, better to be consistent here. If we need better CLI output, we can handle that in
dvc/commands
. But, let's wait for others, let's see what they'll say.Regarding
status
, we could addfilter_info
to it so that you could just doBut this would make sense if we made result consistent.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@skshetry
The question is
dvc/commands
didn't know targets are stages or outputs.Actually I think the most elegant way is that
collect_granular
returns a list ofoutputs
orstages
orfiles
, and they share the same API.status()
which returns the result. But we need another objectFilePathSlot
which is at a finer granularity than outputs to get rid offilter_info
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would agree with @skshetry here,
In that case we inform user that only one out has changed, but that does not mean that this particular stage has only this output. I would say that
status
primary function is to inform about changes, and there is no need to list all of its outputs, if they did not change.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pared Thank you.
How about the
status -c
? Do they also need to follow this format, or just keep the current one?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@karajan1001 This is a good question.
So in case of our current test, if we commit modified
alice
we will getData and pipelines up to date
ondvc status
and we will get
new: alice
ondvc status -c
. As this issue is about filtering thestatus
I would keep output ofdvc status -c
as is and create issue discussing whether we should have consistent output format for bothdvc status
anddvc status -c
.