Re: [compute-pressure] Fix penalty algorithm (#230)

The only issue here is that :

"Set observer.[[LastRecordMap]][source] to record" is happening in [queue a pressurerecord step] (https://www.w3.org/TR/compute-pressure/#queue-a-pressurerecord) and above step is happening on the delayed penalty callback.
So when we are reaching the change count threshold, [LastRecordMap]][source] will be updated after the penalty is carried, which will let 1 new update to be processed fully, because it will pass:
- "has change in data" because LastRecordMap is not up to date.
- "passes rate obfuscation test" because the count was set back to 0.
So we will call queue this record, though we shouldn't.

It s easier to understand when seeing the implementation.

-- 
GitHub Notification of comment by arskama
Please view or discuss this issue at https://github.com/w3c/compute-pressure/pull/230#issuecomment-1695316458 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 28 August 2023 09:03:49 UTC