Skip to content

Conversation

@labkey-jeckels
Copy link
Contributor

Rationale

We should give equal handling to Runnables and Jobs

Changes

  • Wrap all Runnables with a Job
  • Unit tests

_executor.shutdown();
}

public boolean awaitTermination(long timeout, @NotNull TimeUnit unit) throws InterruptedException
Copy link
Contributor

Choose a reason for hiding this comment

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

Now that waitForCompletion() works for Runnables, isn't awaitTermination() redundant?

Copy link
Contributor

Choose a reason for hiding this comment

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

Regardless, a comment on these methods about use would be helpful.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I consolidated. They had different semantics but the distinction wasn't important.

@labkey-jeckels labkey-jeckels merged commit bda416e into develop Dec 21, 2025
9 checks passed
@labkey-jeckels labkey-jeckels deleted the fb_jobRunner branch December 21, 2025 16:34
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.

3 participants