The GitHub Actions job "Fory CI" on fory.git/main has succeeded. Run started by GitHub user chaokunyang (triggered by chaokunyang).
Head commit for run: b2d41923ee768f7a711c1c6b5cd78e862a1cb034 / Ayush Kumar <[email protected]> fix(go): added pre-allocation bounds checks for slices and strings (#3618) ## Why? The code immediately allocated bytes based on the untrusted size. If any user sent a size of 2 billion but only actually sent 5 bytes of data, the server would instantly try to allocate 2GB of RAM. If many such requests were sent, the server would run out of memory (OOM) and crash. ## What does this PR do? Add check which ensures we never allocate memory for data that hasn't actually arrived yet. It forces the allocation to be bounded by the physical size of the data we have already received and verified. ## Related issues Closes #3617 ## AI Contribution Checklist - [ ] Substantial AI assistance was used in this PR: `yes` / `no` - [ ] If `yes`, I included a completed [AI Contribution Checklist](https://github.com/apache/fory/blob/main/AI_POLICY.md#9-contributor-checklist-for-ai-assisted-prs) in this PR description and the required `AI Usage Disclosure`. - [ ] If `yes`, my PR description includes the required `ai_review` summary and screenshot evidence of the final clean AI review results from both fresh reviewers on the current PR diff or current HEAD after the latest code changes. ## Does this PR introduce any user-facing change? - [ ] Does this PR introduce any public API change? - [ ] Does this PR introduce any binary protocol compatibility change? ## Benchmark Report URL: https://github.com/apache/fory/actions/runs/24930390595 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
