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

Runtime cache input simply does not work #30170

Open
1 of 4 tasks
PowerSupply opened this issue Feb 25, 2025 · 0 comments
Open
1 of 4 tasks

Runtime cache input simply does not work #30170

PowerSupply opened this issue Feb 25, 2025 · 0 comments

Comments

@PowerSupply
Copy link
Contributor

PowerSupply commented Feb 25, 2025

Current Behavior

When configuring a runtime cache input according to the documentation it fails to invalidate the cache when it changes. See example in "Steps to Reproduce". Running it several times will result in the output being cached and used when it should not.

Expected Behavior

When the output of the runtime command changes, the cache should be invalidated.

GitHub Repo

No response

Steps to Reproduce

Task config:

"time": {
    "executor": "nx:run-commands",
    "options": {
        "command": "time"
    }
}

nx.json targetDefaults config:

"time": {
    "cache": true,
    "inputs": [
        {
            "runtime": "time"
        }
    ]
}

Nx Report

Node           : 22.10.0
OS             : darwin-arm64
Native Target  : aarch64-macos
npm            : 10.9.0

nx                 : 20.0.3
@nx/js             : 20.0.3
@nx/jest           : 20.0.3
@nx/eslint         : 20.0.3
@nx/workspace      : 20.0.3
@nx/angular        : 20.0.3
@nx/cypress        : 20.0.3
@nx/devkit         : 20.0.3
@nx/eslint-plugin  : 20.0.3
@nx/playwright     : 20.0.3
@nx/plugin         : 20.0.3
@nx/vite           : 20.0.3
@nx/web            : 20.0.3
@nx/webpack        : 20.0.3
typescript         : 5.5.4
---------------------------------------

Failure Logs

Package Manager Version

10.9.0

Operating System

  • macOS
  • Linux
  • Windows
  • Other (Please specify)

Additional Information

This is a problem that has persisted for a long time. I have never seen it work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant