Unable to edit variables after 2021.3 Build 8275 upgrade: "Invariant failed"

seanl · 16 December 2021 23:53

Upgraded to 2021.3 Build 8275, and now I can’t edit variables.
Click on Variables in the project menu has no effect, and dev tools console catches multiple “Invariant failed” errors.

I’ve sent an email to support, has anyone else seen this?

paraic.oceallaigh · 17 December 2021 00:07

Hi Sean,
Thanks for reaching out.
We will process your ticket on the Support queue and close this one off.

Kind Regards,
Paraic

seanl · 23 December 2021 00:16

Here’s the bug if anyone else runs into this issue:

github.com/OctopusDeploy/Issues

Options under More dropdown don't work on smaller screens

opened 06:11AM - 17 Dec 21 UTC

KennethBates

kind/bug area/core state/triage

### Team - [X] I've assigned a team label to this issue ### Severity One repo…rt with a workaround ### Version 2021.3.8275 ### Latest Version _No response_ ### What happened? When the size of the web portal is small enough, the menus in a project has some navigation options that don't work. ### Reproduction 1. Reduce the screen size small enough while in a project to collapse the navigation options 2. Click on `More` 3. Click on `Variables` or `Settings` (any option that themselves have sub-menus won't work) ![image](https://user-images.githubusercontent.com/20388190/146497626-fcf72ea2-eea0-4f51-9380-be41f6564353.png) ### Error and Stacktrace ```shell Browser console log: Error: Invariant failed at r (tiny-invariant.esm.js:8) at react-router.js:695 at wl (react-dom.production.min.js:268) at fs (react-dom.production.min.js:246) at ds (react-dom.production.min.js:246) at rs (react-dom.production.min.js:239) at react-dom.production.min.js:123 at t.unstable_runWithPriority (scheduler.production.min.js:19) at Vo (react-dom.production.min.js:122) at $o (react-dom.production.min.js:123) nl @ react-dom.production.min.js:209 n.callback @ react-dom.production.min.js:226 hi @ react-dom.production.min.js:131 ll @ react-dom.production.min.js:212 gs @ react-dom.production.min.js:255 t.unstable_runWithPriority @ scheduler.production.min.js:19 Vo @ react-dom.production.min.js:122 vs @ react-dom.production.min.js:248 rs @ react-dom.production.min.js:239 (anonymous) @ react-dom.production.min.js:123 t.unstable_runWithPriority @ scheduler.production.min.js:19 Vo @ react-dom.production.min.js:122 $o @ react-dom.production.min.js:123 Xo @ react-dom.production.min.js:122 ne @ react-dom.production.min.js:287 Xt @ react-dom.production.min.js:68 react-dom.production.min.js:123 Uncaught Error: Invariant failed at r (tiny-invariant.esm.js:8) at react-router.js:695 at wl (react-dom.production.min.js:268) at fs (react-dom.production.min.js:246) at ds (react-dom.production.min.js:246) at rs (react-dom.production.min.js:239) at react-dom.production.min.js:123 at t.unstable_runWithPriority (scheduler.production.min.js:19) at Vo (react-dom.production.min.js:122) at $o (react-dom.production.min.js:123) ``` ``` ### More Information Report: https://octopus.zendesk.com/agent/tickets/81022 (private) ### Workaround Expand the screen to get the full-screen navigation back on the left-hand side of the screen

Kenneth_Bates · 23 December 2021 00:24

Hi Sean,

Thanks for updating this public thread with the bug report - great idea! Don’t hesitate to reach out with any questions or concerns in the future.

Best regards,

Kenny

system · 23 January 2022 00:25

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.