No `latest_build_available":true` results for `semeru_certified` JDK

Open
#152 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
52/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
java
Domain
api

Research direction

Reproduce the report with the linked Disco API query and the jq grouping command, then trace how latest_build_available is calculated for semeru_certified packages. Done means the endpoint accurately reports whether a latest build is available for these packages, with regression coverage for the observed case if the repository provides a suitable test location.

Written by the indexing model from the issue text.

Description

When you query for semeru_certified JDKs, apparently none are latest_build_available.

 % curl -s 'https://api.foojay.io/disco/v3.0/packages?distro=semeru_certified' \
   | jq '.result
      | group_by(.latest_build_available)
      | map({latest_build_available: .[0].latest_build_available, count: length})'
[
  {
    "latest_build_available": false,
    "count": 560
  }
]
Dominant language
Java
Stars
154
Forks
18
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from foojayio/discoapi

All issues in foojayio/discoapi

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.