[
https://issues.apache.org/jira/browse/MAHOUT-743?focusedWorklogId=998194&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-998194
]
ASF GitHub Bot logged work on MAHOUT-743:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 30/Dec/25 09:52
Start Date: 30/Dec/25 09:52
Worklog Time Spent: 10m
Work Description: Rutuja123-dos opened a new pull request, #773:
URL: https://github.com/apache/mahout/pull/773
### Purpose of PR
Adds a regression test to ensure async amplitude encoding respects
'chunk_len'
instead of writing the full 'state_len', preventing out-of-bounds writes for
non-first chunks.
### Related Issues or PRs
- Fixes #743
### Changes Made
<!
Issue Time Tracking
-------------------
Worklog Id: (was: 998194)
Remaining Estimate: 0h
Time Spent: 10m
> Allow use of random seeds during unit tests
> -------------------------------------------
>
> Key: MAHOUT-743
> URL: https://issues.apache.org/jira/browse/MAHOUT-743
> Project: Mahout
> Issue Type: Improvement
> Reporter: Lance Norskog
> Assignee: Sean R. Owen
> Priority: Major
> Fix For: 0.6
>
> Attachments: MAHOUT-743.patch, RandomWrapper.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The RandomUtils package has a trick for running unit tests repeatably. All
> random generators created with RandomUtils.getRandom() are started with seed
> 0. Unfortunately, all random generators started with
> RandomUtils.getRandom(seed) effectively run from a seed of 0. Thus, code
> which deliberately creates Random objects with seeds does not work correctly
> under unit tests.
> The problem is that the logic in RandomWrapper tests for unit test mode and
> settable seed mode in the wrong order.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
