Closed AjkayAlan closed 8 months ago
@AjkayAlan sorry to hear that you are having issues.
In order to best understand what is going on here, we are going to need to understand what requests/responses are being made between Chocolatey CLI and the Chocolatey Community Repository?
Are you familiar with a tool called Fiddler? Using this tool would help us capture the requests/responses, to then allow us to debug further into what is going on.
A while back, I created a short video on Fiddler, and how it can be used for this type of debugging.
https://youtu.be/z4CwJ-MF7ik?si=HmU8g781D70eeOPr
If you can, can you capture all the requests/responses for Chocolatey CLI, when running one of the commands that you are attempting?
No worries @gep13! I have gone ahead and gotten a capture with Fiddler for you. I did so using my personal computer (Windows 11 instead of Windows 10), and it has nothing installed via choco, so its more of a clean machine. Here is a gif so you can see what I am seeing - along with so you can take a peek if the Fiddler capture looks good.
If everything looks like I captured things correctly, i'd be happy to send you (or others on your team) the saved Fiddler session. I've added you to a private repo at https://github.com/AjkayAlan/choco-home-issue-308 which has a link to the file in OneDrive on the readme.
@AjkayAlan thank you for the Fiddler export, this has been very useful!
We have been able to reproduce the problem, and will be working on a fix. I will ping you here once that is released, and I would ask if you could confirm it is working for you.
I see this is marked as completed by the sync bot - but wanted to note that I still am seeing the same issue.
I am going to assume the actual work is done, but there still needs to be an infrastructure rollout before the fix is actually active.
@AjkayAlan the necessary code has been implemented, and it gets automatically closed at that point.
It hasn't yet been released to production. We'll leave a comment here once it has been released.
EDIT: So yes, your assumption is correct.
@AjkayAlan we use the 5 - Released
label to indicate that this has made its way out to Production.
@AjkayAlan the modifications have now been deployed.
Can you please re-test, and let us know if you are still running into problems? Thanks
@gep13 Good news and bad news.
Good news first - the fix seems to have corrected some packages. Notably, git --version 2.44.0
and python --version 3.12.2
are now looking good and work as expected.
Bad news - some other packages still aren't working. I tested choco install winscp --version 6.3.2
on both my work device and personal device and am still getting Unable to resolve dependency 'winscp.install (=6.3.2)'
. Another package that came up with issues with internal users (and I have also repeated on my end) is choco install notepadplusplus --version 8.6.4
.
Here is a gif showing what git
did (which worked), and what winscp
did (which failed). The gif is slightly edited to reduce excess wait times.
I have also added a new fiddler capture in https://github.com/AjkayAlan/choco-home-issue-308 in the readme in case it helps, and also added AdmiringWorm as a collaborator to the repo.
@AjkayAlan this is not unexpected 😄
We are now into the realm of caching causing problems with the responses that you are getting back.
If you can provide a complete list of packages that aren't working for you, we should be able to get those taken care of, or the cached results should eventually expire, to be replaced with the correct result from the API.
Apologies again for the inconvenience here!
@AjkayAlan if you try the notepadplusplus and winscp packages again, they should hopefully work for you now.
If there are any others, post them here, and I will try to get to them when I can, otherwise, as I mentioned, the cache should expire naturally as well.
notepadplusplus
and winscp
are confirmed working now 🥳 - glad to know its just a caching thing at this point!
I have not been able to find any other packages that are still cached bad. Notably, I have tried a few other virtual packages with child .install
packages which must have recached, including:
nodejs-lts
python
ruby
Everything is looking good and I can confirm the root cause is resolved. Thank you again for the help and continued work towards keeping Chocolatey awesome 🥇 !
@AjkayAlan woo hoo!
Thank you for confirming, much appreciated! I am very glad to hear that things are working now! I will be able to sleep a little bit easier tonight! 😄
Checklist
What You Are Seeing?
When attempting to install virtual packages, I am having issues with some resolving correctly, and can't explain why, as they worked last week (potentially related to #306?).
Three examples I have seen this behavior is:
git --version 2.44.0
winscp --version 6.3.2
python --version 3.12.2
In all cases, if I use the virtual package, it fails with an
Unable to resolve dependency
error. However, if I directly reference the.install
package via a choco install, it works without issue.What is Expected?
Virtual packages should correctly pull their dependencies.
How Did You Get This To Happen?
$env:chocolateyVersion = 1.4.0
then running the installer:Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString("https://community.chocolatey.org/install.ps1"))
choco list --local-only
choco install winscp --version 6.3.2 --verbose --debug
orchoco install git --version 2.44.0 --verbose --debug
System Details
Installed Packages
Additional Context
This was not an issue last week. Our internal telemetry shows the last successful request on 2024-03-21 at 9AM CDT, and the first failing attempt on 2024-03-25 at 4:50AM CDT. I see 5 unique users today that have encountered this issue, and all failures encountered in our automation today were due to this issue.
┆Issue is synchronized with this Gitlab issue by Unito