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

Index was outside the bounds of the array #120

Closed
gep13 opened this issue Feb 24, 2014 · 10 comments
Closed

Index was outside the bounds of the array #120

gep13 opened this issue Feb 24, 2014 · 10 comments
Labels
Bug Issues where something has happened which was not expected or intended
Milestone

Comments

@gep13
Copy link
Member

gep13 commented Feb 24, 2014

image

Haven't looked into this yet, just generated it, and walked away, I will do some digging

@gep13 gep13 added bug labels Feb 24, 2014
@RichiCoder1
Copy link
Member

That's vague enough that I couldn't be much help without a debugger.

@gep13
Copy link
Member Author

gep13 commented Feb 24, 2014

Agreed. I will do some debugging at lunch time and see if I can trace what is going on. It could be environmental as well. Will let you know what I turn up.

@RichiCoder1
Copy link
Member

If I had to guess, it's probably going to be in GetInstalledPackages in ChocolateyService. Bug me if you need anything.

@gep13 gep13 removed the TaskItem Non-bug, non-feature related things. Could be refactoring. Sometimes non-code related things. label Sep 16, 2014
@gep13 gep13 added this to the 0.12 milestone Sep 16, 2014
@gep13 gep13 changed the title [BUG] Index was outside the bounds of the array Index was outside the bounds of the array Sep 16, 2014
@RichiCoder1
Copy link
Member

This exact issue is making me doubt the wisdom of sticking with .Net 4.0. The async stack traces are gibberish and the only way to fix it is to make the code less readable.

@gep13
Copy link
Member Author

gep13 commented Sep 22, 2014

What are you thinking? Upping to use 4.5.1/4.5.2?

@ferventcoder
Copy link
Member

Only issue I have there is it moves it out of 2003, but there is less than a year left of support for it. Choco CLI supports it, perhaps that becomes the only way you can use choco on 2003. Thoughts?

@gep13
Copy link
Member Author

gep13 commented Sep 22, 2014

Oh, I didn't realise that you can't put .Net 4,5 on a Windows Server 2003 machine. Hmm....

@RichiCoder1
Copy link
Member

I would be targeting 4.5.0, unless there's a good reason to explictly target a higer 4.5.x. I would argue that the merits of moving to 4.5 outweigh the drawbacks of losing support for 2003 and XP. Technically, having CLI as the primary, if only, way to use Choco on a server distribution is not all that bad all things considered. It is a server environment after all.

@gep13
Copy link
Member Author

gep13 commented Sep 23, 2014

I think I am of the same opinion. If people want it, they can always use an earlier version of ChocolateyGUI, leaving us free to roll with the latest and greatest version.

@gep13 gep13 removed the 0 - Backlog label Feb 10, 2015
@gep13
Copy link
Member Author

gep13 commented Feb 10, 2015

From what I can see, targetting 4.5.0 has been implemented, and I am not able to reproduce this error message again, so happy to close this issue for now.

@gep13 gep13 closed this as completed Feb 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Issues where something has happened which was not expected or intended
Projects
None yet
Development

No branches or pull requests

3 participants