Modified cache location (config setting "cacheLocation") not used about choco

[gep13]

Can I ask what you have set for the feature useRememberedArgumentsForUpgrades?

[mu88]

The feature useRememberedArgumentsForUpgrades is enabled

[github-actions]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
This issue will be closed in 14 days if it continues to be inactive.

[mu88]

yes, still relevant

[pauby]

@mu88 The ``Output Log section of the issue does not contain the log in the format we need.

When creating the issue, the Output Log section has these comments:

---

Please include the log given by Chocolatey CLI when running in debugging and verbose mode. You can run Chocolatey CLI in debugging and verbose mode using the flags --debug --verbose. Alternatively, you can find the log file in the following default location: C:\ProgramData\chocolatey\logs\chocolatey.log.

Before including the output log, make sure of the following:

• There is no sensitive data shared in the log.
• We need ALL OUTPUT, not just what you may believe is relevant.
• We need ALL OUTPUT (including the configuration information). See https://gist.github.com/ferventcoder/b1300b91c167c8ac8205#file-error-txt-L1-L41 for what we need.
• If it is hard to reproduce with debug/verbose, the log file already logs with those parameters. Just grab the relevant section from the log file.
• Preferably link to a gist instead of pasting the entire log in the issue. You can create a new gist here: https://gist.github.com/ (see https://docs.github.com/en/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists).

---

Please provide that information by editing and adding it in the first comment (please don't post it in any other comment).

Without the full log we are unable to progress this issue.

[github-actions]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
This issue will be closed in 14 days if it continues to be inactive.

[github-actions]

Dear contributor,

As this issue seems to have been inactive for quite some time now, it has been automatically closed.
If you feel this is a valid issue, please feel free to re-open the issue if / when a pull request
has been added.
Thank you for your contribution.