feature: remove semaphores, add go 1.23 support

[rustatian]

Reason for This PR

• Go 1.23

Description of Changes

• Remove semaphores, replace with just a wait group.
• Update go to 1.23

License Acceptance

By submitting this pull request, I confirm that my contribution is made under
the terms of the MIT license.

PR Checklist

[Author TODO: Meet these criteria.]
[Reviewer TODO: Verify that these criteria are met. Request changes if not]

• All commits in this PR are signed (git commit -s).
• The reason for this PR is clearly provided (issue no. or explanation).
• The description of changes is clear and encompassing.
• Any required documentation changes (code and docs) are included in this PR.
• Any user-facing changes are mentioned in CHANGELOG.md.
• All added/changed functionality is tested.

Summary by CodeRabbit

• Chores

  • Updated GitHub Actions workflow job name for clarity.
  • Streamlined dependency declarations in the go.mod file.
  • Introduced a new go.mod file for the testing module.

• Refactor

  • Improved concurrency control in the stop method by switching to a wait group approach.

• Tests

  • Modified test functions to use manual failure checks instead of an assertion library, enhancing clarity in test reporting.

[coderabbitai]

Warning

Rate limit exceeded

@rustatian has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 22 minutes and 38 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

Commits

Files that changed from the base of the PR and between 3abcbc4 and e21a413.

Walkthrough

The changes involve modifications to various files in the codebase, including updates to GitHub Actions workflows, test functions, and dependency management in the Go module files. Key alterations include renaming a job in the workflow, shifting from assertion libraries to manual failure handling in tests, and simplifying dependency declarations. Additionally, concurrency control in the stop method was improved by replacing a semaphore with a wait group for better goroutine management.

Changes

File(s)	Change Summary
.github/workflows/linters.yml	Renamed job from golangci-lint to linters in the GitHub Actions workflow.
dep/in_test.go, dep/out_test.go	Replaced assertions using assert.Equal with manual failure checks and removed assert imports.
go.mod	Simplified dependency declarations by condensing require blocks and removing unnecessary entries.
stop.go	Changed concurrency control from a semaphore to a wait group for managing goroutines.
tests/go.mod	Introduced a new go.mod file for the tests, specifying dependencies and module path.

Sequence Diagram(s)

sequenceDiagram
    participant Test
    participant Function
    participant WaitGroup

    Test->>Function: Call Test Function
    Function->>WaitGroup: Initialize WaitGroup
    Function->>Function: Execute Goroutines
    Function->>WaitGroup: wg.Done() for each completion
    WaitGroup->>Test: Wait for all goroutines to finish

Loading

🐰 "In the code, changes abound,
Jobs renamed, new paths are found.
Tests now check with careful eyes,
Dependencies trimmed, oh what a prize!
With wait groups, we hop along,
In a world of code, where we belong!" 🐇

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.