processing / processing/processing4

Updates requiring a reboot give the false impression that they failed (in the updates tab)

Open
#647 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

has attachment
Dominant language
Java
Stars
494
Forks
183
Avg merge
4h 39m
Merged PRs (30d)
3

Description

Created by: SableRaf

Description

Updating contributions that require a reboot from the updates tab makes it look like the update silently failed (especially when successful update just disappear from the list). It doesn't show the message "Please restart Processing to update this item" making it look like the update failed. The message can be seen when opening the modes tab and selecting the mode in question.

Expected Behavior

Give the user some indication that they need to reboot.

Current Behavior

No indications that the download succeeded, or that the update requires a reboot of Processing, are given.

Steps to Reproduce

  1. Open PDE
  2. Click on "Updates" at the bottom-right. This assumes there are updates available and that some of them require a reboot (Processing for Android going from 4.5.0b2 to 4.5.0b4 in my case)
  3. Click Update All
  4. Select the mode that was just updated.

Your Environment

  • Processing version: 4.1.2
  • Operating System and OS version: Windows 10

Screenshot

Image

Contributor guide

Open the contributing guide

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

Start by reproducing the update flow in the PDE Updates tab using an item that requires a reboot, then compare it with the message shown in the Modes tab. Done means a successful update clearly indicates that Processing must be restarted instead of disappearing as if it failed.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.