[BUG] P2C LoadBalancer responseTrigger calculates wrong EWMA decay weight due to reversed get/set order

[hengyuss]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

In P2cLoadBalancer.responseTrigger(), the responseStamp is set before being read, causing the EWMA decay weight calculation to always produce 0 time difference:

Expected Behavior

No response

Steps To Reproduce

No response

Environment

ShenYu version(s):latest

Debug logs

No response

Anything else?

i will fix it

[github-actions]

👋 Hello @Aias00

A new issue has been opened by @hengyuss:

• Title: [BUG] P2C LoadBalancer responseTrigger calculates wrong EWMA decay weight due to reversed get/set order
• Link: [BUG] P2C LoadBalancer responseTrigger calculates wrong EWMA decay weight due to reversed get/set order #6427

Please review when you have time. Thank you! 🙏