Add a retry mechanism for communicating with the Foojay back-end

Open
  • Is something wrong?
#63 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start with the linked issue #47 and related pull request #62, then trace the Foojay back-end communication path in the plugin. Define the retry behavior around two or three attempts with increasing but bounded delays; done means transient communication failures are retried before resolution is handed back to other toolchain resolvers.

Written by the indexing model from the issue text.

Description

enhancement

See this issue and related PR.

It would be good if communication failures with the Foojay back-end wouldn't immediately make the plugin's resolving fail. It would be good if the plugin would retry a couple of times before giving up. I'm thinking 2-3 retries with increasing delays, not too long though, the Gradle build might have other toolchain resolvers configured, at some point we need to hand things over to those.

Dominant language
Kotlin
Stars
223
Forks
28
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 gradle/foojay-toolchains

All issues in gradle/foojay-toolchains

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.