fix(cmd/testnetify): use syscall to self signal exit

[troian]

No description provided.

[coderabbitai]

Walkthrough

The Windows AMD64 build configuration was removed from the .goreleaser.yaml file, including its build definition and references in the archive packaging sections. Additionally, the signal handling in testnetify.go was simplified by removing the "os/signal" package and signal channel, replacing them with a direct signal sent to the current process using proc.Signal(os.Interrupt).

Changes

File(s)	Change Summary
cmd/akash/cmd/testnetify/testnetify.go	Removed "os/signal" import and signal channel logic; replaced with direct proc.Signal(os.Interrupt) call
.goreleaser.yaml	Removed Windows AMD64 build configuration and references from builds and archives sections

Estimated code review effort

1 (~5 minutes)

Poem

A signal once danced through a channel so bright,
Now sent straight to process, with a simpler light.
No more channels to juggle, no notify to see—
SIGINT arrives simply, as quick as can be!

Windows build took a bow, stepped off the stage,
Streamlined releases now set the new page.
🐇✨

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1fafb54 and 9a2cfcd.

📒 Files selected for processing (2)

• .goreleaser.yaml (0 hunks)
• cmd/akash/cmd/testnetify/testnetify.go (1 hunks)

💤 Files with no reviewable changes (1)

• .goreleaser.yaml

🚧 Files skipped from review as they are similar to previous changes (1)

• cmd/akash/cmd/testnetify/testnetify.go

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (7)

• GitHub Check: network-upgrade
• GitHub Check: sims
• GitHub Check: release-dry-run
• GitHub Check: coverage
• GitHub Check: lint
• GitHub Check: tests
• GitHub Check: build-bins

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch testnetify

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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>, please review it.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 using 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 generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this 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.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

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.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between aef7c5a and ba351e6.

📒 Files selected for processing (1)

• cmd/akash/cmd/testnetify/testnetify.go (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (7)

• GitHub Check: lint
• GitHub Check: release-dry-run
• GitHub Check: coverage
• GitHub Check: network-upgrade
• GitHub Check: sims
• GitHub Check: tests
• GitHub Check: build-bins

🔇 Additional comments (1)

cmd/akash/cmd/testnetify/testnetify.go (1)

12-12: LGTM: Import change aligns with simplified signal handling.

The replacement of "os/signal" with "syscall" is appropriate for the new direct signal approach.