Drupal.org JSON API modules endpoint returns a 400 error when requested by the Project browser

I was testing Drupal CMS with project browser and got it working. Testing project browser itself on a Drupal 11 site freshly installed fails with a bad request because of securty_coverage filter. If I exclude the filter I get this exact error described here.

Changing and saving project browser settings does not help in my setup.

Hello!

Same happened to me while testing a fresh instalation of Drupal CMS. I investigated a bit the project browser code, and seems that the relationship included here is not permitted in the Drupal.org API.

After removing the field_supporting_organizations,field_supporting_organizations.field_supporting_organization from the include it worked fine again.

So the question is: should project browser remove these relationships? Or maybe Drupal.org changed something that needs to be adjusted?

Thanks @lluvigne , that is the question, indeed. I quickly checked the project_browser module code and haven't found any trace of using the data from field_supporting_organizations, so it seems to me it is not critical for the module to work, but leaving it to project maintainers to comment on it.

If you need this as a patch in your composer download it from thhis url https://git.drupalcode.org/project/project_browser/-/merge_requests/682....

This is likely due to migrations on the new.drupal.org site, which is still very much unstable. They should be resolved next week, although data for this field may take some time to migrate again.

field_supporting_organizations is a paragraph field and the paragraphs migration got jumbled enough to justify deleting all data for the field and starting a fresh migration.

The Drupal.org APIs that project browser uses should still be considered unstable. There was a plan to mitigate this and improve error handling in project browser, but that apparently didn't happen.

I haven't found an issue to improve the error handling around Drupal.org responses that should have been opened. Drupal.org will make breaking changes to the API over time, and 4xx errors should be handled better. The usual recommendation will be to upgrade project browser, although in this case it is likely an unplanned API change.

✨ Display warnings/errors from DrupalOrgJsonApi backend Active was done, so we can set up that warning soon.

field_supporting_organizations was a field not used by Project Browser and that should not have been in the filter.

I knew that it wasn't used in the front-end but totally forgot that it was still in the code. The MR by @rogerpfaff fixed the immediate issue (thanks!), I'm now just trying to fix the tests.

I've manually tested the MR in Drupalpod and it works (commenting out line DrupalDotOrgJsonApi.php:295 as we've temporary put a warning error on the d.o endpoint until this is merged).

Tests are also green (that's the part I just updated).
This is RTBC and ready to be merged. A new release should probably be created after this.

thanks for the work, weekend warriors!

Automatically closed - issue fixed for 2 weeks with no activity.