Open s2504s opened 2 years ago
I have the same issue if the json file is invalid, composer fails. In my case, it happens when I request a nonexistent package neither in nexus nor in packagist.
Have the same problem :C
In my case, the files for composer2 did not generate correctly and showed deleted packages. I had to manually remove the asset from db and restart nexus. Now the packages index correctly, but the error still remained.
In my case, the files for composer2 did not generate correctly and showed deleted packages. I had to manually remove the asset from db and restart nexus. Now the packages index correctly, but the error still remained.
@ByJacob What steps did you carry out to do this exactly?
In my case, the files for composer2 did not generate correctly and showed deleted packages. I had to manually remove the asset from db and restart nexus. Now the packages index correctly, but the error still remained.
@ByJacob What steps did you carry out to do this exactly?
Unfortunately, it was so long ago that I don't remember.
After some package is removed from Nexus composer repo - the search index for v2 is broken (v1 works well) and Nexus trows such message to the logs: