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

Don't log installed engines and runtimes in prod #5900

Merged
merged 4 commits into from
Mar 16, 2023

Conversation

hubertp
Copy link
Contributor

@hubertp hubertp commented Mar 13, 2023

Pull Request Description

The logAvailableComponentsForDebugging will check and install all necessary components of GraalVM for every mentioned version. While not harmful, it adds up to startup time.
Additionally added an option in language server startup to skip installation of GraalVM components. The latter is already performed by project-manager when opening the project and it is unnecessary to do it twice. Due to LS' architecture this configuration has to be passed around via multiple configs.

Finally, skipped the attempt to install Python component on Windows - this is not supported by GraalVM atm.

Closes #5749.

Important Notes

The impact of this problem could be really felt the more versions of Enso and GraalVM one had since it would go through all of them.

Checklist

Please ensure that the following checklist has been satisfied before submitting the PR:

  • The documentation has been updated, if necessary.
  • Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
  • All code follows the
    Scala,
    Java,
    and
    Rust
    style guides. In case you are using a language not listed above, follow the Rust style guide.
  • All code has been tested:
    • Unit tests have been written where possible.
    • If GUI codebase was changed, the GUI was tested when built using ./run ide build.

@@ -339,7 +339,7 @@ class RuntimeVersionManager(
result match {
case (path, Failure(exception)) =>
logger.warn(
"{} at [{}] has been skipped due to the following error: {}",
Copy link
Member

Choose a reason for hiding this comment

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

Why not print this error?

Copy link
Contributor Author

@hubertp hubertp Mar 13, 2023

Choose a reason for hiding this comment

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

it will actually skip it because of the way the last argument is treated if it is an exception. So it would always be empty from what I saw. This way it should included the stacktrace.

Copy link
Contributor Author

@hubertp hubertp Mar 13, 2023

Choose a reason for hiding this comment

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

The action will check and install all necessary components of GraalVM
for every mentioned version. While not harmful, it adds up to startup
time.
Additionally added an option in language server startup to skip
installation of GraalVM components. The latter is already performed by
project-manager when opening the project and it is unnecessary to do it
twice. Due to LS' architecture this configuration has to be passed
around via multiple configs.

Finally, skipped the attempt to install Python component on Windows -
this is not supported by GraalVM atm.

Closes #5749.
@hubertp hubertp force-pushed the wip/hubert/5749-graalvm-updater branch from c2739ce to accd63a Compare March 15, 2023 16:24
@hubertp hubertp added the CI: Ready to merge This PR is eligible for automatic merge label Mar 16, 2023
@mergify mergify bot merged commit a6487e5 into develop Mar 16, 2023
@mergify mergify bot deleted the wip/hubert/5749-graalvm-updater branch March 16, 2023 10:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI: Ready to merge This PR is eligible for automatic merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

GraalVM updater attempts to install component multiple times
3 participants