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

chore: update node to 18 lts #310

Merged
merged 5 commits into from
Oct 25, 2023
Merged

Conversation

stevenh
Copy link
Collaborator

@stevenh stevenh commented Oct 24, 2023

Update to the node 18 LTS so we're on a supported version.

Also updating a bunch of logging to help investigate the random failures occurring in workflows, including switching CodeNarcServer to use java logging instead of prints.

Update to the node 18 lts so we're on a supported version.
Enable debug on all test workflows so we can understand any failures.
Reduce the amount of output in the log when running in debug.
@nvuillam
Copy link
Owner

@stevenh can it be merged ? :)

Please remove the "draft" status of the PRs you consider ready ;) (i think this one is ^^ )

Add slf4j logging to CodeNarcServer so that we can control the log
level.
@@ -32,13 +32,21 @@ import org.apache.tools.ant.types.Commandline
// CodeNarc main class
import org.codenarc.CodeNarc

// Logging
Copy link
Owner

Choose a reason for hiding this comment

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

such an elegant rewriting ;)

@stevenh
Copy link
Collaborator Author

stevenh commented Oct 24, 2023

@stevenh can it be merged ? :)

Please remove the "draft" status of the PRs you consider ready ;) (i think this one is ^^ )

Will do, was just fixing the spelling issues.

I do wish we wouldn't keep getting random failures on some of the platforms.

@stevenh stevenh force-pushed the chore/node-18 branch 2 times, most recently from 991bd17 to a5b9dbe Compare October 24, 2023 20:40
@nvuillam
Copy link
Owner

are the failures so random ? ^^

Add support for trace level debugging so we can reduce the spam while
investigating issues for the log entries which are particularly large.

Trace level logging can be enabled by add npm-groovy-lint-trace to the
DEBUG environment variable.
@stevenh
Copy link
Collaborator Author

stevenh commented Oct 24, 2023

are the failures so random ? ^^

Yes it seems so, I'd say they currently fail more than succeed, from what I've seen while pushing up incremental fixes.

@stevenh stevenh marked this pull request as ready for review October 24, 2023 21:27
@stevenh
Copy link
Collaborator Author

stevenh commented Oct 24, 2023

There's a few ready for review now, will rebase the others when this is in as that will help identify any flaky behaviour.

Copy link
Owner

@nvuillam nvuillam left a comment

Choose a reason for hiding this comment

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

Great 🔥🔥🔥🔥

@nvuillam nvuillam merged commit 16d349f into nvuillam:master Oct 25, 2023
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants