Skip to content
No Response

[1.56.0] JDT LS re-initializes every ~20s and spawns a Gradle daemon each time (204 in one day vs. max 2/day under 1.55.0) #3901

Sign in to view logs

[1.56.0] JDT LS re-initializes every ~20s and spawns a Gradle daemon each time (204 in one day vs. max 2/day under 1.55.0)

[1.56.0] JDT LS re-initializes every ~20s and spawns a Gradle daemon each time (204 in one day vs. max 2/day under 1.55.0) #3901

Workflow file for this run

.github/workflows/no-response.yml at 9b9665d
name: No Response
# **What it does**: Closes issues where the original author doesn't respond to a request for information.
# **Why we have it**: To remove the need for maintainers to remember to check back on issues periodically to see if contributors have responded.
on:
issue_comment:
types: [created]
schedule:
- cron: '0 10 * * *'
jobs:
noResponse:
runs-on: ubuntu-latest
steps:
- uses: lee-dohm/no-response@9bb0a4b5e6a45046f00353d5de7d90fb8bd773bb #v0.5.0
with:
token: ${{ github.token }}
daysUntilClose: 30 # Number of days of inactivity before an Issue is closed for lack of response
responseRequiredLabel: "need info" # Label indicating that a response from the original author is required
closeComment: >
This issue has been closed automatically because it needs more information and has not had recent activity. Please reach out if you have or find the answers we need so that we can investigate further.