[{"id":"36943160390","type":"IssueCommentEvent","actor":{"id":5660346,"login":"jutley","display_login":"jutley","gravatar_id":"","url":"https://api.github.com/users/jutley","avatar_url":"https://avatars.githubusercontent.com/u/5660346?"},"repo":{"id":489865430,"name":"aquasecurity/trivy-operator","url":"https://api.github.com/repos/aquasecurity/trivy-operator"},"payload":{"action":"created","issue":{"url":"https://api.github.com/repos/aquasecurity/trivy-operator/issues/1745","repository_url":"https://api.github.com/repos/aquasecurity/trivy-operator","labels_url":"https://api.github.com/repos/aquasecurity/trivy-operator/issues/1745/labels{/name}","comments_url":"https://api.github.com/repos/aquasecurity/trivy-operator/issues/1745/comments","events_url":"https://api.github.com/repos/aquasecurity/trivy-operator/issues/1745/events","html_url":"https://github.com/aquasecurity/trivy-operator/issues/1745","id":2067360413,"node_id":"I_kwDOHTLA1s57OWqd","number":1745,"title":"Trivy operator behaviour when containers are injected into deployment pod by admissions controllers","user":{"login":"andriktr","id":25537180,"node_id":"MDQ6VXNlcjI1NTM3MTgw","avatar_url":"https://avatars.githubusercontent.com/u/25537180?v=4","gravatar_id":"","url":"https://api.github.com/users/andriktr","html_url":"https://github.com/andriktr","followers_url":"https://api.github.com/users/andriktr/followers","following_url":"https://api.github.com/users/andriktr/following{/other_user}","gists_url":"https://api.github.com/users/andriktr/gists{/gist_id}","starred_url":"https://api.github.com/users/andriktr/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/andriktr/subscriptions","organizations_url":"https://api.github.com/users/andriktr/orgs","repos_url":"https://api.github.com/users/andriktr/repos","events_url":"https://api.github.com/users/andriktr/events{/privacy}","received_events_url":"https://api.github.com/users/andriktr/received_events","type":"User","site_admin":false},"labels":[{"id":4194470735,"node_id":"LA_kwDOHTLA1s76AotP","url":"https://api.github.com/repos/aquasecurity/trivy-operator/labels/kind/feature","name":"kind/feature","color":"c7def8","default":false,"description":"Categorizes issue or PR as related to a new feature."},{"id":4194470882,"node_id":"LA_kwDOHTLA1s76Aovi","url":"https://api.github.com/repos/aquasecurity/trivy-operator/labels/priority/backlog","name":"priority/backlog","color":"fbca04","default":false,"description":"Higher priority than priority/awaiting-more-evidence."},{"id":4194471064,"node_id":"LA_kwDOHTLA1s76AoyY","url":"https://api.github.com/repos/aquasecurity/trivy-operator/labels/target/kubernetes","name":"target/kubernetes","color":"0ebdb0","default":false,"description":"Issues relating to kubernetes cluster scanning"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":14,"created_at":"2024-01-05T13:34:02Z","updated_at":"2024-03-27T19:00:58Z","closed_at":null,"author_association":"NONE","active_lock_reason":null,"body":"Hello,\r\nWhen we run a deployment in k8s trivy-operator looks into the replica set get the images for vulnerability scanning. The problem I see here is in case it's not covers cases when mutating admission controller injects container into the pod. Good example here is a case when we inject service mesh sidecars into our application. Usually then 1 or more containers being added into the pod however replica set normally remains unchanged and contains only the application image in the definition. As result in reality we have pods with application containers + containers injected by admission controllers and as trivy look on replicaset only the application container will be scanned. \r\n\r\nHere is the image grep for the replica set:\r\n\r\n\r\n\r\nAs you can see we have only 1 image\r\n\r\nAnd here we grep image from the pods controlled by this replica set \r\n\r\n\r\nAs u can see we have 2 additional images there `consul-dataplane:1.2.3` is consul service mesh sidecar container image and `consul-k8s-control-plane:1.2.3` is an init container image both these images are injected into pod by admission controller and they are not scanned by trivy-operator. \r\n\r\nAny suggestions, opinions ?\r\n\r\nThank you. \r\n","reactions":{"url":"https://api.github.com/repos/aquasecurity/trivy-operator/issues/1745/reactions","total_count":0,"+1":0,"-1":0,"laugh":0,"hooray":0,"confused":0,"heart":0,"rocket":0,"eyes":0},"timeline_url":"https://api.github.com/repos/aquasecurity/trivy-operator/issues/1745/timeline","performed_via_github_app":null,"state_reason":null},"comment":{"url":"https://api.github.com/repos/aquasecurity/trivy-operator/issues/comments/2023735531","html_url":"https://github.com/aquasecurity/trivy-operator/issues/1745#issuecomment-2023735531","issue_url":"https://api.github.com/repos/aquasecurity/trivy-operator/issues/1745","id":2023735531,"node_id":"IC_kwDOHTLA1s54n8Dr","user":{"login":"jutley","id":5660346,"node_id":"MDQ6VXNlcjU2NjAzNDY=","avatar_url":"https://avatars.githubusercontent.com/u/5660346?v=4","gravatar_id":"","url":"https://api.github.com/users/jutley","html_url":"https://github.com/jutley","followers_url":"https://api.github.com/users/jutley/followers","following_url":"https://api.github.com/users/jutley/following{/other_user}","gists_url":"https://api.github.com/users/jutley/gists{/gist_id}","starred_url":"https://api.github.com/users/jutley/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jutley/subscriptions","organizations_url":"https://api.github.com/users/jutley/orgs","repos_url":"https://api.github.com/users/jutley/repos","events_url":"https://api.github.com/users/jutley/events{/privacy}","received_events_url":"https://api.github.com/users/jutley/received_events","type":"User","site_admin":false},"created_at":"2024-03-27T19:00:58Z","updated_at":"2024-03-27T19:00:58Z","author_association":"NONE","body":"I have a couple thoughts on how this could potentially be handled. Like @andriktr, I am also missing scans on some images which only get added to pods via mutations.\r\n\r\nThe brute force approach would be to watch all pods (I think this is already happening) and getting the set of images in them, and then comparing that set to the controller (the replicaset, for example). If there are additional images in the pod's set, then add these into the scan.\r\n\r\nA slightly more elegant (but still incomplete) approach would be to leverage Kubernetes v1.28's support for [sidecar containers](https://kubernetes.io/blog/2023/08/25/native-sidecar-containers/). The mechanism here is to run sidecar containers as init containers which set `restartPolicy` to `Always`. This capability is protected by a feature flag and is enabled by default in v1.29. However, many clusters won't have this capability, and even when they do, many mutating webhooks will not use it. This may be a good approach a year from now, but not for today.","reactions":{"url":"https://api.github.com/repos/aquasecurity/trivy-operator/issues/comments/2023735531/reactions","total_count":0,"+1":0,"-1":0,"laugh":0,"hooray":0,"confused":0,"heart":0,"rocket":0,"eyes":0},"performed_via_github_app":null}},"public":true,"created_at":"2024-03-27T19:00:59Z","org":{"id":12783832,"login":"aquasecurity","gravatar_id":"","url":"https://api.github.com/orgs/aquasecurity","avatar_url":"https://avatars.githubusercontent.com/u/12783832?"}},{"id":"35745423555","type":"IssuesEvent","actor":{"id":5660346,"login":"jutley","display_login":"jutley","gravatar_id":"","url":"https://api.github.com/users/jutley","avatar_url":"https://avatars.githubusercontent.com/u/5660346?"},"repo":{"id":597093715,"name":"WTFender/aws-sso-extender","url":"https://api.github.com/repos/WTFender/aws-sso-extender"},"payload":{"action":"opened","issue":{"url":"https://api.github.com/repos/WTFender/aws-sso-extender/issues/113","repository_url":"https://api.github.com/repos/WTFender/aws-sso-extender","labels_url":"https://api.github.com/repos/WTFender/aws-sso-extender/issues/113/labels{/name}","comments_url":"https://api.github.com/repos/WTFender/aws-sso-extender/issues/113/comments","events_url":"https://api.github.com/repos/WTFender/aws-sso-extender/issues/113/events","html_url":"https://github.com/WTFender/aws-sso-extender/issues/113","id":2139025894,"node_id":"I_kwDOI5btU85_fvHm","number":113,"title":"Tab switch prevents sessions from refreshing","user":{"login":"jutley","id":5660346,"node_id":"MDQ6VXNlcjU2NjAzNDY=","avatar_url":"https://avatars.githubusercontent.com/u/5660346?v=4","gravatar_id":"","url":"https://api.github.com/users/jutley","html_url":"https://github.com/jutley","followers_url":"https://api.github.com/users/jutley/followers","following_url":"https://api.github.com/users/jutley/following{/other_user}","gists_url":"https://api.github.com/users/jutley/gists{/gist_id}","starred_url":"https://api.github.com/users/jutley/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jutley/subscriptions","organizations_url":"https://api.github.com/users/jutley/orgs","repos_url":"https://api.github.com/users/jutley/repos","events_url":"https://api.github.com/users/jutley/events{/privacy}","received_events_url":"https://api.github.com/users/jutley/received_events","type":"User","site_admin":false},"labels":[{"id":5112822365,"node_id":"LA_kwDOI5btU88AAAABML96XQ","url":"https://api.github.com/repos/WTFender/aws-sso-extender/labels/bug","name":"bug","color":"d73a4a","default":true,"description":"Something isn't working"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2024-02-16T17:09:08Z","updated_at":"2024-02-16T17:09:08Z","closed_at":null,"author_association":"NONE","active_lock_reason":null,"body":"### Extension Version\n\n1.8.2\n\n### Description\n\nI previously used this plugin with AWS SSO Containers. I disabled that to try using this plugin's built-in container support, but it is breaking some pretty basic use cases for me.\r\n\r\nI often have a handful of tabs open for an SSO profile for many days. Today is my second day using the container support in this plugin, and I can't seem to keep those existing tabs and refresh my SSO session.\r\n\r\nEvery time I click on the profile, it brings me to an existing tab, and this tab says that I need to re-authenticate. That totally makes sense, but I don't know how I can refresh that session! Every time I try to log in via this plugin, it just takes me back to that tab without logging in.\r\n\r\nWhen using both plugins, there is no tab switching capability. Signing in would open a new tab in the container, which would refresh the session. Then I can close that tab, go to my existing tabs, refresh, and I can pick up where I left off the previous day. This plugin doesn't seem to have any way to disable the tab switching functionality. Being able to turn it off entirely or just for a single usage of the plugin's UI would do the trick.\n\n### Browsers\n\nFirefox\n\n### OS\n\nMac","reactions":{"url":"https://api.github.com/repos/WTFender/aws-sso-extender/issues/113/reactions","total_count":0,"+1":0,"-1":0,"laugh":0,"hooray":0,"confused":0,"heart":0,"rocket":0,"eyes":0},"timeline_url":"https://api.github.com/repos/WTFender/aws-sso-extender/issues/113/timeline","performed_via_github_app":null,"state_reason":null}},"public":true,"created_at":"2024-02-16T17:09:09Z"},{"id":"35714506569","type":"IssueCommentEvent","actor":{"id":5660346,"login":"jutley","display_login":"jutley","gravatar_id":"","url":"https://api.github.com/users/jutley","avatar_url":"https://avatars.githubusercontent.com/u/5660346?"},"repo":{"id":597093715,"name":"WTFender/aws-sso-extender","url":"https://api.github.com/repos/WTFender/aws-sso-extender"},"payload":{"action":"created","issue":{"url":"https://api.github.com/repos/WTFender/aws-sso-extender/issues/102","repository_url":"https://api.github.com/repos/WTFender/aws-sso-extender","labels_url":"https://api.github.com/repos/WTFender/aws-sso-extender/issues/102/labels{/name}","comments_url":"https://api.github.com/repos/WTFender/aws-sso-extender/issues/102/comments","events_url":"https://api.github.com/repos/WTFender/aws-sso-extender/issues/102/events","html_url":"https://github.com/WTFender/aws-sso-extender/issues/102","id":2113568858,"node_id":"I_kwDOI5btU859-oBa","number":102,"title":"All SSO sessions open in same container `name Profile`","user":{"login":"kiyose","id":45911,"node_id":"MDQ6VXNlcjQ1OTEx","avatar_url":"https://avatars.githubusercontent.com/u/45911?v=4","gravatar_id":"","url":"https://api.github.com/users/kiyose","html_url":"https://github.com/kiyose","followers_url":"https://api.github.com/users/kiyose/followers","following_url":"https://api.github.com/users/kiyose/following{/other_user}","gists_url":"https://api.github.com/users/kiyose/gists{/gist_id}","starred_url":"https://api.github.com/users/kiyose/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kiyose/subscriptions","organizations_url":"https://api.github.com/users/kiyose/orgs","repos_url":"https://api.github.com/users/kiyose/repos","events_url":"https://api.github.com/users/kiyose/events{/privacy}","received_events_url":"https://api.github.com/users/kiyose/received_events","type":"User","site_admin":false},"labels":[{"id":5112822365,"node_id":"LA_kwDOI5btU88AAAABML96XQ","url":"https://api.github.com/repos/WTFender/aws-sso-extender/labels/bug","name":"bug","color":"d73a4a","default":true,"description":"Something isn't working"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2024-02-01T21:57:47Z","updated_at":"2024-02-15T18:32:06Z","closed_at":null,"author_association":"NONE","active_lock_reason":null,"body":"### Extension Version\n\n1.7.7\n\n### Description\n\nAll sso sessions are being opened into the same container `name Profile` where name is a constant `name` and Profile is interpolated correctly.\r\n\r\n![Screenshot 2024-02-01 at 1 56 36 PM](https://github.com/WTFender/aws-sso-extender/assets/45911/eeed33e9-0a54-45fe-92ca-6a4fe6308704)\r\n\n\n### Browsers\n\nFirefox\n\n### OS\n\nMac","reactions":{"url":"https://api.github.com/repos/WTFender/aws-sso-extender/issues/102/reactions","total_count":1,"+1":0,"-1":0,"laugh":0,"hooray":0,"confused":0,"heart":0,"rocket":0,"eyes":1},"timeline_url":"https://api.github.com/repos/WTFender/aws-sso-extender/issues/102/timeline","performed_via_github_app":null,"state_reason":"reopened"},"comment":{"url":"https://api.github.com/repos/WTFender/aws-sso-extender/issues/comments/1946890396","html_url":"https://github.com/WTFender/aws-sso-extender/issues/102#issuecomment-1946890396","issue_url":"https://api.github.com/repos/WTFender/aws-sso-extender/issues/102","id":1946890396,"node_id":"IC_kwDOI5btU850CzCc","user":{"login":"jutley","id":5660346,"node_id":"MDQ6VXNlcjU2NjAzNDY=","avatar_url":"https://avatars.githubusercontent.com/u/5660346?v=4","gravatar_id":"","url":"https://api.github.com/users/jutley","html_url":"https://github.com/jutley","followers_url":"https://api.github.com/users/jutley/followers","following_url":"https://api.github.com/users/jutley/following{/other_user}","gists_url":"https://api.github.com/users/jutley/gists{/gist_id}","starred_url":"https://api.github.com/users/jutley/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jutley/subscriptions","organizations_url":"https://api.github.com/users/jutley/orgs","repos_url":"https://api.github.com/users/jutley/repos","events_url":"https://api.github.com/users/jutley/events{/privacy}","received_events_url":"https://api.github.com/users/jutley/received_events","type":"User","site_admin":false},"created_at":"2024-02-15T18:32:05Z","updated_at":"2024-02-15T18:32:05Z","author_association":"NONE","body":"I got this error, but in my case the issue seemed to be tied to AWS SSO Containers. I didn't realize that this plugin could open in containers, so I used both plugins in conjunction.\r\n\r\nTo resolve the error with AWS SSO Containers, I had to open the AWS SSO homepage, and that seemed to somehow refresh AWS SSO Container's understanding of the different account names. Maybe that is the same issue as what happened in this extension.","reactions":{"url":"https://api.github.com/repos/WTFender/aws-sso-extender/issues/comments/1946890396/reactions","total_count":0,"+1":0,"-1":0,"laugh":0,"hooray":0,"confused":0,"heart":0,"rocket":0,"eyes":0},"performed_via_github_app":null}},"public":true,"created_at":"2024-02-15T18:32:07Z"},{"id":"34945599920","type":"IssueCommentEvent","actor":{"id":5660346,"login":"jutley","display_login":"jutley","gravatar_id":"","url":"https://api.github.com/users/jutley","avatar_url":"https://avatars.githubusercontent.com/u/5660346?"},"repo":{"id":130756831,"name":"nerdswords/yet-another-cloudwatch-exporter","url":"https://api.github.com/repos/nerdswords/yet-another-cloudwatch-exporter"},"payload":{"action":"created","issue":{"url":"https://api.github.com/repos/nerdswords/yet-another-cloudwatch-exporter/issues/1138","repository_url":"https://api.github.com/repos/nerdswords/yet-another-cloudwatch-exporter","labels_url":"https://api.github.com/repos/nerdswords/yet-another-cloudwatch-exporter/issues/1138/labels{/name}","comments_url":"https://api.github.com/repos/nerdswords/yet-another-cloudwatch-exporter/issues/1138/comments","events_url":"https://api.github.com/repos/nerdswords/yet-another-cloudwatch-exporter/issues/1138/events","html_url":"https://github.com/nerdswords/yet-another-cloudwatch-exporter/issues/1138","id":1882596274,"node_id":"I_kwDOB8sw385wNiOy","number":1138,"title":"[BUG] Invalid timestamps on metrics with addCloudwatchTimestamp after upgrading from 0.53.0 to 0.54.1","user":{"login":"doris-zhou","id":53917499,"node_id":"MDQ6VXNlcjUzOTE3NDk5","avatar_url":"https://avatars.githubusercontent.com/u/53917499?v=4","gravatar_id":"","url":"https://api.github.com/users/doris-zhou","html_url":"https://github.com/doris-zhou","followers_url":"https://api.github.com/users/doris-zhou/followers","following_url":"https://api.github.com/users/doris-zhou/following{/other_user}","gists_url":"https://api.github.com/users/doris-zhou/gists{/gist_id}","starred_url":"https://api.github.com/users/doris-zhou/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/doris-zhou/subscriptions","organizations_url":"https://api.github.com/users/doris-zhou/orgs","repos_url":"https://api.github.com/users/doris-zhou/repos","events_url":"https://api.github.com/users/doris-zhou/events{/privacy}","received_events_url":"https://api.github.com/users/doris-zhou/received_events","type":"User","site_admin":false},"labels":[{"id":911603738,"node_id":"MDU6TGFiZWw5MTE2MDM3Mzg=","url":"https://api.github.com/repos/nerdswords/yet-another-cloudwatch-exporter/labels/bug","name":"bug","color":"d73a4a","default":true,"description":"Something isn't working"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2023-09-05T19:25:36Z","updated_at":"2024-01-18T23:50:33Z","closed_at":null,"author_association":"NONE","active_lock_reason":null,"body":"### Is there an existing issue for this?\n\n- [X] I have searched the existing issues\n\n### YACE version\n\n0.54.1\n\n### Config file\n\nConfiguration of the affected job:\r\n\r\n```\r\napiVersion: v1alpha1\r\ndiscovery:\r\n jobs:\r\n - type: firehose\r\n regions:\r\n - us-east-1\r\n period: 300\r\n length: 300\r\n addCloudwatchTimestamp: true\r\n metrics:\r\n - name: DeliveryToS3.Success\r\n statistics: [Average]\r\n - name: DeliveryToS3.DataFreshness\r\n statistics: [Maximum]\r\n - name: IncomingBytes\r\n statistics: [Sum]\r\n```\n\n### Current Behavior\n\nWe upgraded from version 0.53.0 to 0.54.1 with no changes in YACE config between versions. Prometheus started failing to scrape YACE with the message:\r\n\r\n`expected timestamp or new record, got \"INVALID\"`\r\n\r\nPrometheus logs include errors like:\r\n```\r\nts=2023-09-05T15:11:17.245Z caller=scrape.go:1697 level=warn component=\"scrape manager\" scrape_pool= target= msg=\"Error on ingesting samples with different value but same timestamp\" num_dropped=1\r\n```\r\n\r\nand in a separate Prometheus instance:\r\n```\r\nts=2023-09-05T17:55:01.215Z caller=scrape.go:1700 level=warn component=\"scrape manager\" scrape_pool= target= msg=\"Error on ingesting samples that are too old or are too far into the future\" num_dropped=33\r\nts=2023-09-05T18:03:35.763Z caller=scrape.go:1694 level=warn component=\"scrape manager\" scrape_pool= target= msg=\"Error on ingesting out-of-order samples\" num_dropped=42\r\n```\r\n\r\nI've checked YACE's metrics output and compared them between two versions. It seems that some metrics are getting a negative value for the timestamp.\r\n\r\nWith 0.53.0:\r\n\r\n`aws_firehose_delivery_to_s3_success_average{} 1 1693939800000`\r\n\r\nWith 0.54.1:\r\n\r\n`aws_firehose_delivery_to_s3_success_average{} 0 -62135596800000`\r\n\r\nWe have observed this only on the Firehose metrics so far. What could be causing the negative timestamp?\n\n### Expected Behavior\n\nI expect to be able to scrape metrics with the `addCloudwatchTimestamp` option as in previous versions of YACE.\n\n### Steps To Reproduce\n\n_No response_\n\n### Anything else?\n\n_No response_","reactions":{"url":"https://api.github.com/repos/nerdswords/yet-another-cloudwatch-exporter/issues/1138/reactions","total_count":6,"+1":6,"-1":0,"laugh":0,"hooray":0,"confused":0,"heart":0,"rocket":0,"eyes":0},"timeline_url":"https://api.github.com/repos/nerdswords/yet-another-cloudwatch-exporter/issues/1138/timeline","performed_via_github_app":null,"state_reason":null},"comment":{"url":"https://api.github.com/repos/nerdswords/yet-another-cloudwatch-exporter/issues/comments/1899399181","html_url":"https://github.com/nerdswords/yet-another-cloudwatch-exporter/issues/1138#issuecomment-1899399181","issue_url":"https://api.github.com/repos/nerdswords/yet-another-cloudwatch-exporter/issues/1138","id":1899399181,"node_id":"IC_kwDOB8sw385xNogN","user":{"login":"jutley","id":5660346,"node_id":"MDQ6VXNlcjU2NjAzNDY=","avatar_url":"https://avatars.githubusercontent.com/u/5660346?v=4","gravatar_id":"","url":"https://api.github.com/users/jutley","html_url":"https://github.com/jutley","followers_url":"https://api.github.com/users/jutley/followers","following_url":"https://api.github.com/users/jutley/following{/other_user}","gists_url":"https://api.github.com/users/jutley/gists{/gist_id}","starred_url":"https://api.github.com/users/jutley/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jutley/subscriptions","organizations_url":"https://api.github.com/users/jutley/orgs","repos_url":"https://api.github.com/users/jutley/repos","events_url":"https://api.github.com/users/jutley/events{/privacy}","received_events_url":"https://api.github.com/users/jutley/received_events","type":"User","site_admin":false},"created_at":"2024-01-18T23:50:32Z","updated_at":"2024-01-18T23:50:32Z","author_association":"CONTRIBUTOR","body":"I ran into this same error. Same negative timestamp. The metric value is reported as zero, and I do have `nilToZero` and `addCloudwatchTimestamp` set to `true.","reactions":{"url":"https://api.github.com/repos/nerdswords/yet-another-cloudwatch-exporter/issues/comments/1899399181/reactions","total_count":0,"+1":0,"-1":0,"laugh":0,"hooray":0,"confused":0,"heart":0,"rocket":0,"eyes":0},"performed_via_github_app":null}},"public":true,"created_at":"2024-01-18T23:50:34Z","org":{"id":89839079,"login":"nerdswords","gravatar_id":"","url":"https://api.github.com/orgs/nerdswords","avatar_url":"https://avatars.githubusercontent.com/u/89839079?"}},{"id":"34814211962","type":"WatchEvent","actor":{"id":5660346,"login":"jutley","display_login":"jutley","gravatar_id":"","url":"https://api.github.com/users/jutley","avatar_url":"https://avatars.githubusercontent.com/u/5660346?"},"repo":{"id":254987890,"name":"wsun/multibuzzer","url":"https://api.github.com/repos/wsun/multibuzzer"},"payload":{"action":"started"},"public":true,"created_at":"2024-01-14T20:14:11Z"}]