Closed
Bug 1275550
Opened 10 years ago
Closed 9 years ago
error while disabling client in client manager
Categories
(Taskcluster :: UI, defect)
Taskcluster
UI
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jhford, Unassigned)
Details
I tried disabling a client id in the client manager. It seemed to work, but the state of the UI didn't update to reflect this being disabled until I did a cache-clearing refresh of the page.
Here's the stack I got:
Warning: setState(...): Can only update a mounted or mounting component. This usually means you called setState() on an unmounted component. This is a no-op. Please check the code for the ConfirmAction component.
common.bundle.js:65017:9
require<[836]</</warning() common.bundle.js:65017
getInternalInstanceReadyForUpdate() common.bundle.js:59497
enqueueSetState() common.bundle.js:59644
require<[711]</</ReactComponent.prototype.setState() common.bundle.js:51181
setLoaded() app.bundle.js:1793
loadState/promises</<() app.bundle.js:1801
tryCallOne() common.bundle.js:29521
handleResolved/<() common.bundle.js:29607
flush()
Sounds like something's trying to set state but is doing it incorrectly, causing the page not to update.
Comment 1•9 years ago
|
||
This should be fixed as part of the June 2017 refactoring.
https://github.com/taskcluster/taskcluster-tools/commit/b8424aebbbf4bafa34241083a4ba881bf17ced6d
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
| Assignee | ||
Updated•7 years ago
|
Component: Tools → UI and Tools
You need to log in
before you can comment on or make changes to this bug.
Description
•