-
Notifications
You must be signed in to change notification settings - Fork 72
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
feat(pegboard): add process monitoring, wip sqlite #1146
feat(pegboard): add process monitoring, wip sqlite #1146
Conversation
Your org requires the Graphite merge queue for merging into mainYou must have a Graphite account and log in to Graphite in order to use the merge queue. Sign up using this link. You can enable merging using labels in your Graphite merge queue settings. |
c3855c3
to
0d527ab
Compare
81dbbe7
to
d3132bc
Compare
0d527ab
to
9b3c0cd
Compare
d3132bc
to
92504c4
Compare
9b3c0cd
to
7920edb
Compare
92504c4
to
36cebf1
Compare
7920edb
to
c5a2d95
Compare
36cebf1
to
281896a
Compare
Ok((watcher, rx)) | ||
} | ||
|
||
pub async fn wait_for_creation<P: AsRef<Path>>(path: P) -> Result<()> { |
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.
make sure the systemd service has enough watchers configured. write the calculation in the comments (i.e. supports X containers * Y watchers per container
) and comment in this func to update the systemd watcher count too
use sqlx::Error::*; | ||
|
||
if i > MAX_QUERY_RETRIES { | ||
bail!("max sql retries: {err}"); |
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.
where do these errors get written & monitored? we need to be able to catch every tiny issue with pb monitors
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.
Was planning on having vector pick up the logs from the manager and stream them to the backend. Didn't get to it for MVP I don't think
} | ||
} | ||
|
||
async fn send_packet(&self, packet: protocol::ToServer) -> Result<()> { |
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.
what happens on failure? how are all socket close edge cases handled/
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.
the manager errors then restarts and reconnects to the ws
async fn write_event(&self, event: &protocol::Event) -> Result<()> { | ||
// Write event to db | ||
let event_json = serde_json::to_vec(event)?; | ||
utils::query(|| async { |
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 is this edge case failure handled?
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.
which failure? the serde_json::to_vec?
use client::Client; | ||
use ctx::Ctx; | ||
|
||
const PROTOCOL_VERSION: u16 = 1; | ||
|
||
#[tokio::main] |
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.
should we use a current threaded scheduler or limit the threads to 2? this is currently multithreaded, will spin up a lot of excess threads.
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.
we do the same in the toolchain
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.
idk how much parallelism we'll actually need
Merge activity
|
<!-- Please make sure there is an issue that this PR is correlated to. --> Fixes RVTEE-608 ## Changes <!-- If there are frontend changes, please include screenshots. -->
Fixes RVTEE-608
Changes