Skip to content

fix: score plugin now affects the path without global beam - #168

Merged
eiennohito merged 2 commits into
masterfrom
fix/full-beam-plugin
Oct 13, 2026
Merged

eiennohito merged 2 commits into
masterfrom
fix/full-beam-plugin

Conversation

@eiennohito

Copy link
Copy Markdown
Contributor

Without the global beam, computeScoresFull stored the beam scores before applyPluginToFullBeam changed them. makeBeams reads the stored scores, so the plugin (for example, partial-annotation input) never changed the result. The global-beam path, which is the default, applies the plugin in its own places and was not affected.

The fix swaps the order. A new test in analyzer_impl_test.cc checks that a penalizing plugin changes the best path both with and without the global beam. Before the fix, the case without the global beam fails.

🤖 Generated with Claude Code

computeScoresFull stored the beam scores before the plugin adjusted them,
and makeBeams reads the stored scores, so plugin adjustments never
changed the path when the global beam was off.
The protobuf check expanded the variables inside if(), so an unset
Protobuf_VERSION left VERSION_LESS without its left operand and
configuration failed (the Windows CI runner has no protobuf).
@eiennohito
eiennohito merged commit c946317 into master Oct 13, 2026
4 checks passed
@eiennohito
eiennohito deleted the fix/full-beam-plugin branch October 13, 2026 23:32
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