You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've encountered a bug in Nango where the UI becomes dysfunctional when the CI environment variable is set to false. This issue arises when using Flightcontrol for deployments as it automatically sets this variable to false.
I've identified 3 instances of the CI environment variable within Nango's codebase. However, none of these instances involve a direct comparison of the variable's value. Instead, they merely check for its existence. This approach seems suboptimal, as it could lead to unintended consequences in certain scenarios (like a broken UI).
Steps to Reproduce:
Create a Docker Compose file (see below) that sets the CI environment variable to false for the Nango container.
Start the Nango container using the Docker Compose file (docker-compose up).
I've encountered a bug in Nango where the UI becomes dysfunctional when the
CI
environment variable is set tofalse
. This issue arises when using Flightcontrol for deployments as it automatically sets this variable tofalse
.I've identified 3 instances of the
CI
environment variable within Nango's codebase. However, none of these instances involve a direct comparison of the variable's value. Instead, they merely check for its existence. This approach seems suboptimal, as it could lead to unintended consequences in certain scenarios (like a broken UI).Steps to Reproduce:
CI
environment variable tofalse
for the Nango container.docker-compose up
).Expected Behavior:
The Nango UI should function normally regardless of the CI environment variable's value (or at least when it's set to anything but
true
).Actual Behavior:
The Nango UI displays errors and becomes unresponsive when
CI
is set tofalse
.Proposed Solution:
Implement a more robust check for the
CI
environment variable, comparing its value to ensure correct behavior.The text was updated successfully, but these errors were encountered: