[bounty] windows update should properly terminate all the running processes before triggering the update

[louis030195]

i think we had this issue before and had put a bounty on it and thought it was solved but saw someone having issue again with this

definition of done:

• when windows user receive update of screenpipe it should properly CLOSE both screenpipe backend and any embedded AI running (llm_sidecar.rs)

bonus:

• something to improve the update UX and not spamming users with a dialog or something better UX (check how screen studio or other app do it)

/bounty 100

[linear[bot]]

MED-339 [bounty] windows update should properly terminate all the running processes before triggering the update

[algora-pbc[bot]]

💎 $100 bounty • Screenpi.pe

Steps to solve:

1. Start working: Comment /attempt #774 with your implementation plan
2. Submit work: Create a pull request including /claim #774 in the PR body to claim the bounty
3. Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts

Thank you for contributing to mediar-ai/screenpipe!

Add a bounty • Share on socials

[RichardGrant-93]

I have the solution for this @louis030195

ERROR: Permission to mediar-ai/screenpipe.git denied to RichardGrant-93. fatal: Could not read from remote repository.

[RichardGrant-93]

/claim #774 PR: https://github.com/mediar-ai/screenpipe/pull/777

[tribhuwan-kumar]

something to improve the update UX and > not spamming users with a dialog or > > > something better UX (check how screen > studio or other app do it)

@louis030195 if dialogs are feeling spammy, what about a update button in app status? when update is available it'll notify user with a app notification or a toast and user can start downloading update from the status ui?