Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Feb 14 07:37
    gep13 closed #734
  • Feb 14 07:37
    gep13 commented #734
  • Feb 14 07:37
    gep13 labeled #734
  • Feb 14 05:53
    xmha97 opened #734
  • Feb 12 10:08
    gustavohenac opened #733
  • Feb 11 00:19
    AdmiringWorm commented #685
  • Feb 08 18:12
    opusforlife2 commented #595
  • Feb 08 01:41
    JesFEREM commented #685
  • Feb 08 00:33
    vertigo220 opened #732
  • Feb 07 21:44
    VideoPlayerCode edited #731
  • Feb 07 21:43
    VideoPlayerCode commented #731
  • Feb 07 21:38
    VideoPlayerCode commented #731
  • Feb 07 21:37
    VideoPlayerCode opened #731
  • Feb 07 21:14
    VideoPlayerCode commented #595
  • Feb 07 21:14
    VideoPlayerCode commented #595
  • Feb 07 21:12
    VideoPlayerCode commented #595
  • Feb 07 21:08
    VideoPlayerCode commented #595
  • Feb 07 17:54
    PowerPCx86 commented #725
  • Feb 05 05:01
    vertigo220 commented #545
  • Feb 04 21:26
    vertigo220 commented #595
Manfred Wallner
@mwallner
image.png
can you reproduce this / is this actually a bug?
Manfred Wallner
@mwallner
  • not the current, but the latest available ...
Manfred Wallner
@mwallner
the "latestVersion" got from chocolateyService is null ...
image.png
Manfred Wallner
@mwallner
(couldn't debug into the service contract - maybe @RichiCoder1 or @gep13 could take a look? :-))
Richard Simpson
@RichiCoder1
@mwallner If you set VS's Startup to start both Subprocess & GUI (In that order), you can debug into subprocess where all the logic is hapenning
That being said, it must have just broke. Was working literally yesterday
Manfred Wallner
@mwallner
do you think you can fix it soon (like, today :D) - I'd have the chance to 'hand out' a beta to a couple of collegues tomorrow to play with/ QA the thing before we do a 0.15 release ;-)
Richard Simpson
@RichiCoder1
Workin fine here :|
Manfred Wallner
@mwallner
hm ..
oh: I think I broke the AppVeyor build - but it seems to be Nuget/Cake related ...
Richard Simpson
@RichiCoder1
xD
Manfred Wallner
@mwallner
image.png
Richard Simpson
@RichiCoder1
Hmm. Looks like we're hitting out MyGet quota or something. @gep13 ?
Kim J. Nordmo
@AdmiringWorm
@RichiCoder1 probably used up the 500MB quota, I suggest perhaps deleting older versions on myget (Possibly enable Package Retention cleanup)
Richard Simpson
@RichiCoder1
I think that's what I'll do. I can't configure cleanup as I'm only a contributer, not an admin
Will consult w/ @gep13 but will probably just nuke all but latest prerelease and just start only keeping 10 or so pre. We should probably also look into applying for OSS license
Manfred Wallner
@mwallner
uh, this might help @RichiCoder1 - it only fetches the latest version from the public feed (if I enable chocolatey.org/api/v2) I get following
image.png
Kim J. Nordmo
@AdmiringWorm
@RichiCoder1 yeah, I think keeping the latest 10 would be a good choice there.
Richard Simpson
@RichiCoder1
Hmmm. We do some custom logic as choco outdated doesn't provide a convenient list logic we can use. Still confused, though, as I could swear the logic we're using takes into account multiple feeds.
Let me check something
Manfred Wallner
@mwallner
chocolatey/ChocolateyGUI#445 -> @RichiCoder1
Richard Simpson
@RichiCoder1
@mwallner I think I may already have a fix
Random question for room: Do you like that GUI only shows latest for packages that have updates, or would you prefer to see the latest version of a packages regardless?
Manfred Wallner
@mwallner
@RichiCoder1 great!
and: I don't get your question x_x
Richard Simpson
@RichiCoder1
or
Manfred Wallner
@mwallner
hm .. good point, I think the one where only those with a newer version are displayed is pretty intuitive
Richard Simpson
@RichiCoder1
Agreed.
Manfred Wallner
@mwallner
but it should work for any feeds :D (internal also ;-))
Richard Simpson
@RichiCoder1
@mwallner You can pull down source right? Mind if a create a PR and then have you pull it down and test?
Manfred Wallner
@mwallner
of course, let's fix this :-)
Kim J. Nordmo
@AdmiringWorm
Regarding the show only if new version is available or not, I think it looks better when it only shows when there is an update available.
With that said though, trying to look at it from a different perspective.
Let's say the user doesn't know that it only shows for versions with an update available, they would possibly think that there is something wrong and chocolatey gui is unable to grab the latest version for those packages.
Manfred Wallner
@mwallner
in this case, would you prefer newer versions to be highlighted, or 'same' version numbers to be grayed-out ..?
Kim J. Nordmo
@AdmiringWorm
Personally I would think same version to be grayed-out
Manfred Wallner
@mwallner
I think this is a nice feature request, at least worth submitting an issue (don't think it should be mixed with #445)
Richard Simpson
@RichiCoder1
@mwallner chocolatey/ChocolateyGUI#446
Let me know how that works for you
Richard Simpson
@RichiCoder1
Also went ahead and killed all pres that had < 5 downloads. Will kill the rest later.
Manfred Wallner
@mwallner
works great @RichiCoder1 - will review changes and merge into develop - ok?
Richard Simpson
@RichiCoder1
:+1:
Richard Simpson
@RichiCoder1
Random: Just improved the way we handle scaling. If you have a high dpi setup, markdown should (should) render much cleaner. Also, package icons should be much pretty. Apparently I wasn't handling scaling properly, so they'd get rendered at 65px and then upscaled to something like 100px (poorly)
Now they render at the correct size. Especially noticable for packages w/ SVG icons.
Manfred Wallner
@mwallner
@RichiCoder1 ++
sadly the bot doesn't listen to me :D