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
When using the UI, if you go to Run -> Advanced Configuration -> ECSRun -> Environment Variables, and you set a numeric string, it gets coerced to an integer. This is a problem because ECS itself does not take integers as environment variables and only takes strings. Thus, the Flow will error out and not even run.
There is something weird though because the coercion only happens when using the JSON editor. If you fill in the blanks, it seems to respect the data type.
Steps To Reproduce
Register any flow that uses ECSRun. Just make sure it works, it can be anything.
Go to Run for the Flow, and put an env variable "test" with the value "100".
Click run and this will error out saying that 100 is not an acceptable env variable for ECS.
Browsers Tested:
Chrome
Notes
Images attached as guidance of the error, and the JSON editor.
Image 1 - section of the UI where Run is hit
Image 2- JSON editor and value
Image 3 - Error seen
The text was updated successfully, but these errors were encountered:
Bug Description
When using the UI, if you go to
Run
->Advanced Configuration
->ECSRun
->Environment Variables
, and you set a numeric string, it gets coerced to an integer. This is a problem because ECS itself does not take integers as environment variables and only takes strings. Thus, the Flow will error out and not even run.There is something weird though because the coercion only happens when using the JSON editor. If you fill in the blanks, it seems to respect the data type.
Steps To Reproduce
ECSRun
. Just make sure it works, it can be anything.Run
for the Flow, and put an env variable "test" with the value "100".Browsers Tested:
Notes
Images attached as guidance of the error, and the JSON editor.
Image 1 - section of the UI where Run is hit
Image 2- JSON editor and value
Image 3 - Error seen
The text was updated successfully, but these errors were encountered: