Skip to content

Improve rails6-shoryuken and remove shoryuken#374

Merged
unflxw merged 2 commits into
mainfrom
remove-shoryuken-port-batched
Jul 13, 2026
Merged

Improve rails6-shoryuken and remove shoryuken#374
unflxw merged 2 commits into
mainfrom
remove-shoryuken-port-batched

Conversation

@unflxw

@unflxw unflxw commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Add a batched Shoryuken worker to rails6-shoryuken

Shoryuken can deliver a group of SQS messages to a single worker
perform call when the worker sets :batch => true. AppSignal
instruments that batch case differently from a single message. It tags
the transaction with batch => true, records each message's body as a
separate parameter keyed by its message ID, and does not link the
transaction back to an enqueuer, because a batch can mix messages from
several traces.

Until now that path was only exercised by the standalone ruby/shoryuken
app, which is being removed. Add a native batched worker on its own
queue, enqueued from a web request, so rails6-shoryuken keeps covering
it.

Remove the standalone Shoryuken test app

The ruby/shoryuken app was the only setup exercising Shoryuken used
natively, rather than as an Active Job queue adapter. That coverage now
lives in rails6-shoryuken: PR #371 added a native worker there, and the
previous commit added a batched one. So the two native paths the
standalone app covered are covered again.

The app was also never in the CI matrix, so it was untested surface. Its
removal leaves nothing behind but a smaller maintenance footprint. The
README is regenerated to drop it.

unflxw added 2 commits July 13, 2026 15:31
Shoryuken can deliver a group of SQS messages to a single worker
`perform` call when the worker sets `:batch => true`. AppSignal
instruments that batch case differently from a single message. It tags
the transaction with `batch => true`, records each message's body as a
separate parameter keyed by its message ID, and does not link the
transaction back to an enqueuer, because a batch can mix messages from
several traces.

Until now that path was only exercised by the standalone ruby/shoryuken
app, which is being removed. Add a native batched worker on its own
queue, enqueued from a web request, so rails6-shoryuken keeps covering
it.
The ruby/shoryuken app was the only setup exercising Shoryuken used
natively, rather than as an Active Job queue adapter. That coverage now
lives in rails6-shoryuken: PR #371 added a native worker there, and the
previous commit added a batched one. So the two native paths the
standalone app covered are covered again.

The app was also never in the CI matrix, so it was untested surface. Its
removal leaves nothing behind but a smaller maintenance footprint. The
README is regenerated to drop it.
@backlog-helper

Copy link
Copy Markdown

Hi @unflxw,

We've found some issues with your Pull Request.

  • This Pull Request is missing labels. Please add labels to help identify types of Pull Requests. - (More info)
  • This Pull Request is missing reviewers. Either convert this Pull Request into a draft or ignore this rule by adding [skip review] to your Pull Request body. - (More info)

New issue guide | Backlog management | Rules | Feedback

@unflxw unflxw changed the title Fold native Shoryuken coverage into rails6-shoryuken, remove standalone app Improve rails6-shoryuken and remove shoryuken Jul 13, 2026
@unflxw
unflxw merged commit a821f7a into main Jul 13, 2026
76 checks passed
@unflxw
unflxw deleted the remove-shoryuken-port-batched branch July 13, 2026 13:40
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.

1 participant