chocolatey / chocolatey/ChocolateyGUI

Provide a way to ignore HttpCache when retrieving packages

Open
#1,027 0 comments 0 reactions 0 assignees View on GitHub
0 - Triaging Customer Enhancement
Dominant language
C#
Stars
1.8k
Forks
272
Avg merge
4d 13h
Merged PRs (30d)
1

Description

### Checklist

- [X] I have verified this is the correct repository for opening this issue.
- [X] I have verified no other issues exist related to my request.

### Is Your Feature Request Related To A Problem? Please describe.

The HttpCache added in 2.x of Chocolatey CLI causes confusing behavior when using Chocolatey GUI. When a new package is made available in a repository, it may not show up in Chocolatey GUI until the cache is rebuilt (Up to 30 minutes by default).

We should provide a way (a button for example) for Chocolatey GUI to skip the cache when retrieving package data from remote sources.

### Describe The Solution. Why is it needed?

Reduces customer confusion and increases user experience.

### Additional Context

We shouldn't provide a toggle for this so that it always fetches from the cache or always skips the cache. Provide the button to allow the user to select it at the time.

This will prevent the user forgetting they have toggled on it and then experiencing slow performance from the updating.

### Related Issues

- [Zendesk Ticket](https://chocolatey.zendesk.com/agent/tickets/20109).

Contributor guide

Open the contributing guide

Research direction

Start by tracing how Chocolatey GUI retrieves package data from remote sources and where the HttpCache affects that flow. The work is done when the GUI offers a one-time action to skip the cache for a retrieval, without adding a persistent toggle or changing the default caching behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.