`latest` API parameter does not seem to work as expected

[JackPGreen]

This might be user error.

I want to download (say) the latest version of Semeru JDK 11, for Linux/x64.

The documentation says I should use latest=available, but if I do that I get the following response:

{
  "result": [
    {
      "id": "e001e5341739cb1a86454e2bf4758eb2",
      "archive_type": "tar.gz",
      "distribution": "semeru",
      "major_version": 11,
      "java_version": "11.0.22",
      "distribution_version": "11.0.22",
      "jdk_version": 11,
      "latest_build_available": true,
      "release_status": "ga",
      "term_of_support": "lts",
      "operating_system": "linux",
      "lib_c_type": "glibc",
      "architecture": "x64",
      "fpu": "unknown",
      "package_type": "jdk",
      "javafx_bundled": false,
      "directly_downloadable": true,
      "filename": "ibm-semeru-open-jdk_x64_linux_11.0.22_7_openj9-0.43.0.tar.gz",
      "links": {
        "pkg_info_uri": "https://api.foojay.io/disco/v3.0/ids/e001e5341739cb1a86454e2bf4758eb2",
        "pkg_download_redirect": "https://api.foojay.io/disco/v3.0/ids/e001e5341739cb1a86454e2bf4758eb2/redirect"
      },
      "free_use_in_production": true,
      "tck_tested": "unknown",
      "tck_cert_uri": "",
      "aqavit_certified": "unknown",
      "aqavit_cert_uri": "",
      "size": 205750292,
      "feature": []
    },
    {
      "id": "81408b9d636baab491c46b2948299907",
      "archive_type": "tar.gz",
      "distribution": "semeru",
      "major_version": 11,
      "java_version": "11.0.22",
      "distribution_version": "11.0.22",
      "jdk_version": 11,
      "latest_build_available": false,
      "release_status": "ga",
      "term_of_support": "lts",
      "operating_system": "linux",
      "lib_c_type": "glibc",
      "architecture": "x64",
      "fpu": "unknown",
      "package_type": "jdk",
      "javafx_bundled": false,
      "directly_downloadable": true,
      "filename": "ibm-semeru-certified-jdk_x64_linux_11.0.22.0.tar.gz",
      "links": {
        "pkg_info_uri": "https://api.foojay.io/disco/v3.0/ids/81408b9d636baab491c46b2948299907",
        "pkg_download_redirect": "https://api.foojay.io/disco/v3.0/ids/81408b9d636baab491c46b2948299907/redirect"
      },
      "free_use_in_production": true,
      "tck_tested": "no",
      "tck_cert_uri": "",
      "aqavit_certified": "yes",
      "aqavit_cert_uri": "https://github.com/ibmruntimes/semeru11-certified-binaries/releases/download/jdk-11.0.22%2B7_openj9-0.43.0/ibm-semeru-certified-jdk_x64_linux_11.0.22.0.tap.zip",
      "size": 219470559,
      "feature": []
    }
  ],
  "message": "2 package(s) found"
}

It's returned:

• ibm-semeru-open-jdk_x64_linux_11.0.22_7_openj9-0.43.0.tar.gz with latest_build_available=true
• ibm-semeru-certified-jdk_x64_linux_11.0.22.0.tar.gz with latest_build_available=false

I think that:

• latest=available should have filtered out any latest_build_available=false
• a semeru-certified JDK should have a distribution of semeru_certified

[JackPGreen]

This is no longer occurring - is it actually fixed, or intermittent?

[HanSolo]

Should be fixed, the update of pkgs runs on different times for each distribution, so it might take some time for each distribution to be updated/cleaned up

[JackPGreen]

It's returned:

• ibm-semeru-open-jdk_x64_linux_11.0.22_7_openj9-0.43.0.tar.gz with latest_build_available=true
• ibm-semeru-certified-jdk_x64_linux_11.0.22.0.tar.gz with latest_build_available=false

I think that:

• latest=available should have filtered out any latest_build_available=false

This looks to have been fixed

• a semeru-certified JDK should have a distribution of semeru_certified

This is still occuring for ibm-semeru-certified-jdk_x64_linux_11.0.22.0.tar.gz

[HanSolo]

Indeed there was a bigger issue behind that thing...already fixing it...will come with the next deployment...probably over the weekend...thx for reporting it 👍🏻

[JackPGreen]

Indeed there was a bigger issue behind that thing...already fixing it...will come with the next deployment...probably over the weekend...thx for reporting it 👍🏻

• latest=available should have filtered out any latest_build_available=false

This looks to have been fixed

No rush from my side but this has regressed.