Skip to content

org.eclipse.jdt.core.compiler.problem.potentialNullReference preference not taken into account #3471

org.eclipse.jdt.core.compiler.problem.potentialNullReference preference not taken into account

org.eclipse.jdt.core.compiler.problem.potentialNullReference preference not taken into account #3471

Triggered via issue April 6, 2026 13:08
@rubensarubensa
commented on #4388 c4a1cd6
Status Success
Total duration 9s
Artifacts

no-response.yml

on: issue_comment
noResponse
4s
noResponse
Fit to window
Zoom out
Zoom in

Annotations

1 warning
noResponse
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: lee-dohm/no-response@9bb0a4b5e6a45046f00353d5de7d90fb8bd773bb. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/