Skip to content

Improve ClientIntent status & event reporting robustness by using LRU cache & caching only after successful report #2013

Improve ClientIntent status & event reporting robustness by using LRU cache & caching only after successful report

Improve ClientIntent status & event reporting robustness by using LRU cache & caching only after successful report #2013

Triggered via pull request September 12, 2024 11:28
@amitlichtamitlicht
opened #484
Status Success
Total duration 20s
Artifacts

cla.yaml

on: pull_request_target
CLAssistant  /  CLAssistant
7s
CLAssistant / CLAssistant
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
CLAssistant / CLAssistant
The following actions uses node12 which is deprecated and will be forced to run on node16: otterize/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
CLAssistant / CLAssistant
The following actions use a deprecated Node.js version and will be forced to run on node20: otterize/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/