You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While attempting to retrieve details for this package (https://repo.packagist.org/p2/letraceursnork/wordpress-security-advisories~dev.json), I encountered significant performance issues due to the sheer volume of conflict data. The last successful request I managed to execute returned a response exceeding 5 million lines, making the request nearly impossible to complete efficiently. To improve accessibility and performance, I suggest removing conflict information from the main endpoint and introducing a dedicated endpoint specifically for fetching this data.
The text was updated successfully, but these errors were encountered:
Those p2 endpoints are the ones used by Composer to read the metadata it needs to resolve dependencies. Removing the conflict data from them would break things, because it would effectively remove the conflicts from the package definition.
this package specifically has a huge file here, because it has tons of conflicts while also having 470 branches included in this file (and the composer-specific minification does not help a lot, because those conflict rules are changing between versions, and the branches don't even have name that sort them in a relevant order minimizing back and forth changes)
While attempting to retrieve details for this package (https://repo.packagist.org/p2/letraceursnork/wordpress-security-advisories~dev.json), I encountered significant performance issues due to the sheer volume of conflict data. The last successful request I managed to execute returned a response exceeding 5 million lines, making the request nearly impossible to complete efficiently. To improve accessibility and performance, I suggest removing conflict information from the main endpoint and introducing a dedicated endpoint specifically for fetching this data.
The text was updated successfully, but these errors were encountered: