Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix "Could not determine jdk version for project" error #980

Merged
merged 5 commits into from
Jan 22, 2024

Conversation

ash211
Copy link
Contributor

@ash211 ash211 commented Jan 13, 2024

Fixes #979

Before this PR

See linked issue.

I think this is happening because ProjectRootManager.getInstance(project).getProjectSdk() here is sometimes returning null. This is allowed by its method contract (there is a @Nullable marking on the method), so we need to handle it gracefully.

After this PR

==COMMIT_MSG==
Fix "Could not determine jdk version for project" error
==COMMIT_MSG==

With this PR, I intend for palantir-java-format to handle this situation by logging a warning and not performing any formatting.

Possible downsides?

If this state persists indefinitely, users may find that formatting no longer works and no longer have the warning in their IDE pointing in this direction. Users rarely view IDE warning logs (in fact I had to search for how to find them when researching for this PR).

@changelog-app
Copy link

changelog-app bot commented Jan 13, 2024

Generate changelog in changelog/@unreleased

What do the change types mean?
  • feature: A new feature of the service.
  • improvement: An incremental improvement in the functionality or operation of the service.
  • fix: Remedies the incorrect behaviour of a component of the service in a backwards-compatible way.
  • break: Has the potential to break consumers of this service's API, inclusive of both Palantir services
    and external consumers of the service's API (e.g. customer-written software or integrations).
  • deprecation: Advertises the intention to remove service functionality without any change to the
    operation of the service itself.
  • manualTask: Requires the possibility of manual intervention (running a script, eyeballing configuration,
    performing database surgery, ...) at the time of upgrade for it to succeed.
  • migration: A fully automatic upgrade migration task with no engineer input required.

Note: only one type should be chosen.

How are new versions calculated?
  • ❗The break and manual task changelog types will result in a major release!
  • 🐛 The fix changelog type will result in a minor release in most cases, and a patch release version for patch branches. This behaviour is configurable in autorelease.
  • ✨ All others will result in a minor version release.

Type

  • Feature
  • Improvement
  • Fix
  • Break
  • Deprecation
  • Manual task
  • Migration

Description

Fix "Could not determine jdk version for project" error

Check the box to generate changelog(s)

  • Generate changelog entry

@ash211 ash211 marked this pull request as ready for review January 13, 2024 00:28
@ash211 ash211 requested a review from fawind January 13, 2024 00:28
int indexOfVersionDelimiter = version.indexOf('.');
String normalizedVersion =
indexOfVersionDelimiter >= 0 ? version.substring(0, indexOfVersionDelimiter) : version;
normalizedVersion = normalizedVersion.replaceAll("-ea", "");
try {
return Integer.parseInt(normalizedVersion);
return OptionalInt.of(Integer.parseInt(normalizedVersion));
} catch (NumberFormatException e) {
log.error("Could not parse sdk version: {}", version, e);
return null;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Returning null for an OptionalInt here seems not ideal.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Whoops! Fixed, and filed #987 to enable baseline-null-away on this repo

@CRogers
Copy link
Contributor

CRogers commented Jan 22, 2024

👍

@bulldozer-bot bulldozer-bot bot merged commit 96267d3 into develop Jan 22, 2024
7 checks passed
@bulldozer-bot bulldozer-bot bot deleted the aash/fix-error branch January 22, 2024 12:58
@svc-autorelease
Copy link
Collaborator

Released 2.40.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

IllegalStateException: Could not determine jdk version for project
5 participants