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

cached params files don't get collected #9478

Closed
Tracked by #9722
dberenbaum opened this issue May 18, 2023 · 5 comments · Fixed by #9909
Closed
Tracked by #9722

cached params files don't get collected #9478

dberenbaum opened this issue May 18, 2023 · 5 comments · Fixed by #9909
Assignees
Labels
bug Did we break something? p1-important Important, aka current backlog of things to do

Comments

@dberenbaum
Copy link
Collaborator

dberenbaum commented May 18, 2023

Bug Report

Description

Top-level params files that are saved to the cache don't get collected in params/exp show.

First reported by @slevang in #7224.

Reproduce

From a fresh Git/DVC repo, add this dvc.yaml:

stages:
  dump_params:
    cmd: 'echo "param: 1" > my_params.yaml'
    outs:
      - my_params.yaml
params:
  - my_params.yaml

Then run this:

$ dvc exp run
$ dvc exp show
 ─────────────────────────────────────────────
  Experiment                 Created    param
 ─────────────────────────────────────────────
  workspace                  -          1
  main                       01:18 PM   -
  └── 5d93ec0 [zinky-sled]   01:25 PM   !
 ─────────────────────────────────────────────

Expected

The experiment row should show 1 instead of ! under the param column.

Environment information

$ dvc doctor
DVC version: 2.57.1
-------------------
Platform: Python 3.10.10 on macOS-13.3.1-arm64-arm-64bit
Subprojects:
        dvc_data = 0.51.0
        dvc_objects = 0.22.0
        dvc_render = 0.5.2
        dvc_task = 0.2.1
        scmrepo = 1.0.3
Supports:
        azure (adlfs = 2023.1.0, knack = 0.10.1, azure-identity = 1.12.0),
        gdrive (pydrive2 = 1.15.3),
        gs (gcsfs = 2022.11.0),
        hdfs (fsspec = 2022.11.0, pyarrow = 11.0.0),
        http (aiohttp = 3.8.4, aiohttp-retry = 2.8.3),
        https (aiohttp = 3.8.4, aiohttp-retry = 2.8.3),
        oss (ossfs = 2021.8.0),
        s3 (s3fs = 2022.11.0, boto3 = 1.24.59),
        ssh (sshfs = 2023.4.1),
        webdav (webdav4 = 0.9.8),
        webdavs (webdav4 = 0.9.8),
        webhdfs (fsspec = 2022.11.0)
Config:
        Global: /Users/dave/Library/Application Support/dvc
        System: /Library/Application Support/dvc
Cache types: reflink, hardlink, symlink
Cache directory: apfs on /dev/disk3s1s1
Caches: local
Remotes: local
Workspace directory: apfs on /dev/disk3s1s1
Repo: dvc, git
Repo.site_cache_dir: /Library/Caches/dvc/repo/6414c2ff59800d13bb7dc40946807396
@dberenbaum dberenbaum added bug Did we break something? p1-important Important, aka current backlog of things to do labels May 18, 2023
@dberenbaum dberenbaum added this to DVC May 18, 2023
@github-project-automation github-project-automation bot moved this to Backlog in DVC May 18, 2023
@dberenbaum
Copy link
Collaborator Author

It's important to be able to track params as outputs. In most cases, they don't need to be cached, but since that's the default behavior for outputs, it will often break when users try it.

@slevang
Copy link

slevang commented Sep 15, 2023

@dberenbaum should I expect these changes to work on the Studio side now that this is released, or is there a delay there? When I try this in my dvc.yaml on 3.20.0, the params do show up in dvc params diff or dvc exp show but they don't seem to load into Studio when I push an experiment.

@shcheklein
Copy link
Member

@slevang yes, it's not released / fixed on the Studio side. I'll try to update it soon.

@slevang
Copy link

slevang commented Sep 15, 2023

That's what I figured, thanks. No rush, just wanted to make sure I wasn't missing something.

@shcheklein
Copy link
Member

@slevang I think it should be now released and deployed to Studio. Could you please give it a try when you have time and confirm if everything works fine for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Did we break something? p1-important Important, aka current backlog of things to do
Projects
No open projects
Archived in project
4 participants