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.

Sign up for GitHub

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

Jump to bottom

"Value cannot be null" running choco outdated #1383

Closed
SaintGimp opened this issue Aug 14, 2017 · 3 comments
Closed

"Value cannot be null" running choco outdated #1383

SaintGimp opened this issue Aug 14, 2017 · 3 comments
Assignees
@ferventcoder
Labels
5 - Released Bug Customer Priority_HIGH
Milestone
0.10.8

Comments

@SaintGimp
Copy link

SaintGimp commented Aug 14, 2017 •
edited

What You Are Seeing?

When I run "choco outdated", it always lists the first outdated package then exits with a "value cannot be null" error.

What is Expected?

It should list all of my outdated packages.

How Did You Get This To Happen? (Steps to Reproduce)

The command was working fine, then I removed and reinstalled a particular package (notepadplusplus with the -x86 option, if I recall correctly) and then this error began happening. Note that it always errors out after listing the first outdated package. It was erroring out after listing the "fiddler4" package, then I upgraded that one and now still it's erroring after listing the "lastpass" package.

Output Log

This is with Chocolatey v0.10.7
https://gist.github.com/SaintGimp/4387a3415e40f36ced6118c8f3b9bb60
@SaintGimp
Copy link
Author

The error is actually caused by enabling useRememberedArgumentsForUpgrades. When I disable that feature the error goes away. At a guess, I think it's because I have packages that were installed with Chocolatey 0.10.3 and don't have a .arguments file.

@ferventcoder ferventcoder self-assigned this Aug 20, 2017
@ferventcoder ferventcoder added this to the 0.10.8 milestone Aug 20, 2017
@ferventcoder
Copy link
Member

@SaintGimp thanks for that - I think we have a good place to look for this issue.

@ferventcoder
Copy link
Member

ferventcoder commented Aug 20, 2017 •
edited

This is fixed for 0.10.8.

ferventcoder added a commit that referenced this issue Aug 21, 2017
@ferventcoder
(GH-1383) Fix - no pkg args cause "value cannot be null"
dfc9c40 
When there are packages that do not have a saved .arguments file, if
someone has useRememberedArgumentsForUpgrades turned on, it can cause
"Value cannot be null" issues when running outdated or upgrade for the
packages that do not have these files. This is seen for packages that
were installed or last upgraded before Chocolatey v0.10.4.
ferventcoder added a commit to ferventcoder/choco that referenced this issue Aug 21, 2017
@ferventcoder
Merge branch 'stable'
1c5e62b 
* stable:
  (chocolateyGH-1386) Default Template - Overall help and todo
  (chocolateyGH-1257) AutoUninstaller: package opt-out
  (maint) tab - add pro list options
  (chocolateyGH-1383) Fix - no pkg args cause "value cannot be null"
  (chocolateyGH-1385) Template - do not treat binary as text file
  (maint) typo
  (maint) Do not package pdb w/exe
  (doc) update generated docs
@ferventcoder ferventcoder mentioned this issue Feb 6, 2018
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ferventcoder ferventcoder

Labels
5 - Released Bug Customer Priority_HIGH
Projects
None yet
Milestone
0.10.8
Development

No branches or pull requests
3 participants
@ferventcoder @SaintGimp @gep13