-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[agent-smith] Enable egress monitoring #8742
Conversation
Codecov Report
@@ Coverage Diff @@
## main #8742 +/- ##
==========================================
+ Coverage 12.31% 18.31% +6.00%
==========================================
Files 20 39 +19
Lines 1161 3401 +2240
==========================================
+ Hits 143 623 +480
- Misses 1014 2740 +1726
- Partials 4 38 +34
Flags with carried forward coverage won't be shown. Click here to find out more.
📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more |
2d6e8fd
to
127a7ab
Compare
127a7ab
to
17abe73
Compare
/werft run 👍 started the job as gitpod-build-prs-agent-smith.8 |
Hey @princerachit , really cool to see this, thank you! Can you think if we'll need to update any configuration for the related deploy of |
No. The config already exists and should work. |
// the workspaces map. This is because we do not lock before reading from the map. | ||
// So, if multiple processes written to the cli chan are | ||
// read in parallel, all of them will get inside the below if check. | ||
if _, ok := workspaces[i.Workspace.PID]; !ok { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about acquiring the lock before reading from the map? Currently it would be possible that one thread is reading from the map while another is currently modifying the internal data structures of the map.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would not make any difference as the if
block will only overwrite the existing entry with the same content. i.e. even if the data in the map is updated we do not care as we just want to make sure that the key exists in the map.
Introducing a lock for reads will block the subsequent classification steps as the number of reads are going to be too many.
8b26d15
to
c529537
Compare
/werft run 👍 started the job as gitpod-build-prs-agent-smith.11 |
/werft run 👍 started the job as gitpod-build-prs-agent-smith.14 |
Description
Related Issue(s)
Fixes https://github.com/gitpod-io/ops/issues/1383
How to test
gpctl debug logs agent-smith
Logs
Release Notes
Documentation