keybase / keybase/client

Rename update process.

Open
#7,551 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

This is quite literally the first bug I've ever submitted on Git and I am not even sure it qualifies as a bug or if I'm even doing any of this right...

After investigating some issues on my PC I found upd.exe in Resource Monitor (Win 10 Pro), didn't know what it was or what app was using it so I used the built-in "Search Online" option in Resource Monitor which opened Chrome/Google and many of the first pages of Google results show upd.exe as a PuP.

I dunno if ultimately this matters, but I would think if the updater was being listed as a false positive that might be problematic at some point.

Keybase GUI Version: 1.0.24-20170619074027+91a6943

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no source file, test, or entry point; it only identifies upd.exe in the Windows Keybase GUI updater. Start by locating the updater build entry point and verify how its executable name is assigned. Done means the updater has a less misleading name and the Windows build still works.

Written by the indexing model from the issue text.

Assessment

Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.