Repository navigation
What is the issue linked to change in calculate_tb_size in v1.2.1 #1033
|
Diff shows only a one-line change between It is not clear what the removal of this one line accomplishes or which previously reported or unreported issue it fixes. Please clarify.
|
Answered by
lollodealma
Oct 27, 2025
Replies: 1 comment 1 reply
|
Hi @naperman, I believe your diff does not consider indentation differences (please compare lines 167-onwards on the left vs lines 170-onwards on the right). The main difference is that we now apply the Best regards |
1 reply
Answer selected by
naperman
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Hi @naperman,
I believe your diff does not consider indentation differences (please compare lines 167-onwards on the left vs lines 170-onwards on the right).
You can find the full diff log here: v1.2.0...v1.2.1
The main difference is that we now apply the
target_tb_sizequantization in both cases (i.e., whethertarget_tb_sizeis provided as input or not) which ensures that the function complies with 3GPP standards also whentarget_tb_sizeis user-provided.Best regards