Removed the next pointer offset condition to set data size

[mohammedzakikochargi]

IMPORTANT: All PRs must be linked to an issue (except for extremely trivial and straightforward changes).

Description

Fixed the issue of data size not getting set for the 2nd time due to nextPtrOffset (condition where we were checking if the value is same is declared value) variable getting initialized while setting data size for the first time.

Alternative(s) considered

Have you considered any alternatives? And if so, why have you chosen the approach in this PR?

Type

Type Choose one: (Bug fix)

Screenshots (if applicable)

Checklist

• I have read the Contribution Guidelines
• I have written Unit Tests
• I have discussed my proposed solution with code owners in the linked issue(s) and we have agreed upon the general approach

[github-actions]

Test Results Linux_ARM64

  1 files  ±0    1 suites  ±0   10m 42s ⏱️ -1s
426 tests ±0  261 ✅  - 1  164 💤 ±0  1 ❌ +1 
262 runs  ±0   97 ✅  - 1  164 💤 ±0  1 ❌ +1 

For more details on these failures, see this check.

Results for commit f52055d. ± Comparison against base commit 110a2e2.

♻️ This comment has been updated with latest results.

[github-actions]

Test Results Linux

  1 files  ±0    1 suites  ±0   10m 12s ⏱️ ±0s
308 tests ±0  226 ✅  - 1  81 💤 ±0  1 ❌ +1 
227 runs  ±0  145 ✅  - 1  81 💤 ±0  1 ❌ +1 

For more details on these failures, see this check.

Results for commit 2867824. ± Comparison against base commit 53157e2.

♻️ This comment has been updated with latest results.

[github-actions]

Test Results Linux-CudaT

  1 files  ±0    1 suites  ±0   10m 29s ⏱️ -1s
408 tests ±0  240 ✅  - 1  167 💤 ±0  1 ❌ +1 
241 runs  ±0   73 ✅  - 1  167 💤 ±0  1 ❌ +1 

For more details on these failures, see this check.

Results for commit d488909. ± Comparison against base commit ba0f2ff.

♻️ This comment has been updated with latest results.

[joiskash]

Great job!