Updates tab blank after failed contribution manager install #4704

Closed
jeremydouglass opened this Issue Oct 16, 2016 · 3 comments

Comments

Projects
None yet
2 participants
@jeremydouglass
Contributor

jeremydouglass commented Oct 16, 2016

In Processing 3.2.1 on MacOS 10.10.5:

When the Contribution Manager fails on individual install, all updates disappear from the Contribution manager Updates tab. They have not been updated -- they are just no longer listed. Closing and then restarting Processing correctly repopulates the Updates tab.

I am testing with the failing p5.js update reported in p5js issue 11.


Before a failed update:

contribution manager -- updates tab

After:

contributions manager -- updates tab empty

On closing and restarting, Updates tab listings are restored (until next failed update).


I wasn't sure if this should be reported here or to processing-docs

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Oct 18, 2016

Member

This is the correct place, thanks.

Do you get any red error messages in the console?

Member

benfry commented Oct 18, 2016

This is the correct place, thanks.

Do you get any red error messages in the console?

@jeremydouglass

This comment has been minimized.

Show comment
Hide comment
@jeremydouglass

jeremydouglass Oct 19, 2016

Contributor
  • No error messages in an open Processing sketch console while replicating the error.
  • No error messages in the system Console while replicating the error.

The only recent error I see with Processing in the system Console logs is "excessive wakeups" -- possibly when I work the computer or launched processing just before running the first test, rather than during the test itself.

10/19/16 09:33:42.000 kernel[0]: process Processing[88834] caught causing excessive wakeups. Observed wakeups rate (per sec): 167; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 95421
10/19/16 09:33:54.634 spindump[87535]: Saved wakeups_resource.diag report for Processing version 3.2.1 (0253) to /Library/Logs/DiagnosticReports/Processing_2016-10-19-093354_Bundtcake.wakeups_resource.diag

However it seems probable that this is unrelated to the Updates tab. I then closed and restarted Processing 3.2.1 and walked through replicating the error two more times, and the error occured without triggering another system Console error either time.

Contributor

jeremydouglass commented Oct 19, 2016

  • No error messages in an open Processing sketch console while replicating the error.
  • No error messages in the system Console while replicating the error.

The only recent error I see with Processing in the system Console logs is "excessive wakeups" -- possibly when I work the computer or launched processing just before running the first test, rather than during the test itself.

10/19/16 09:33:42.000 kernel[0]: process Processing[88834] caught causing excessive wakeups. Observed wakeups rate (per sec): 167; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 95421
10/19/16 09:33:54.634 spindump[87535]: Saved wakeups_resource.diag report for Processing version 3.2.1 (0253) to /Library/Logs/DiagnosticReports/Processing_2016-10-19-093354_Bundtcake.wakeups_resource.diag

However it seems probable that this is unrelated to the Updates tab. I then closed and restarted Processing 3.2.1 and walked through replicating the error two more times, and the error occured without triggering another system Console error either time.

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Nov 3, 2016

Member

Now fixed for the release after 3.2.2: #4082

Member

benfry commented Nov 3, 2016

Now fixed for the release after 3.2.2: #4082

@benfry benfry closed this Nov 3, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment