jeffdaily commented on PR #1399:
URL: https://github.com/apache/mahout/pull/1399#issuecomment-5320133772

   > @jeffdaily any updates?
   
   Sorry for the delay, sincerely.  This PR was prepared by our new MOAT 
project when it was still a prototype under my jeffdaily github org in June.  
It graduated to a supported AMD product last week after a brief outage.  I've 
been trying to follow up with open PRs like yours as soon as I can, using 
MOAT's agent flow to address review comments, rerun all builds and tests across 
sufficient AMD hardware hosted on various servers, babysitting (agentsitting?) 
results, etc.
   
   Also, this PR was opened before it would have gotten the (now usual) 
disclosure:
   
   > This pull request was prepared with the help of an AI assistant acting as 
a coding agent and was read and approved by a person before it was opened. It 
comes from an ongoing effort to add AMD GPU support to widely used CUDA 
projects, one repository at a time: https://github.com/AMD-Ecosystem/moat -- 
that repository describes how the work is done and what a person checks before 
anything is submitted.                                                          
                                                 
   >
   > If you would rather not receive pull requests from this effort, say so 
here or open an issue at 
https://github.com/AMD-Ecosystem/moat/issues/new/choose and we will close this 
and stop. That can cover this repository alone or everything you own, whichever 
you prefer.
   
   Some of the comments I made above were done with AI assistance and weren't 
disclosed, sorry.  Like I said, you caught me between prototype and release of 
MOAT, and we've refined our human-in-the-loop policy since then.  This is 
actually me responding to you, to all of you reviewers, and I greatly 
appreciate your time on this PR review.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to