Description: The allow_n_plus_one() function sets tags only on the span returned by get_current_span(). When this function is called within a nested span context, get_current_span() returns the child span, not the transaction. The tags are therefore not propagated to the containing transaction. Since the server-side N+1 detector checks for these tags at the transaction level, the feature will fail to ignore N+1 patterns in the common use case where database operations are wrapped in their own child spans.

Suggested fix: In allow_n_plus_one(), after setting the tag on the current span, check if span.containing_transaction exists. If it does, set the same tag on the transaction object to ensure the tag is propagated correctly for server-side detection.
_{severity: 0.7, confidence: 0.95}