Config variables not working properlly #2613
Labels
area: orchestrator QoL
need: investigation
need to investigate what is happening before proceeding
type: bug
Something isn't working
Config parameters often break, where even though they are defined in the launch script they do not get parsed correctly and use their default value instead. Changing the order of the parameters or using a
often fixes the issue, which causes confusion for new O's coming in:
=
instead of amonitor
flag in order to get it to work-autoAdjustPrice=false
and-pricePerUnit=1199
but didn't receive any work since it was adjusting above 1200 (pricePerUnit is now set to 1099 and he is receiving work again)There have been plenty of other instances where over the past few months, maybe we can add some more verbosity over what config variables it has read or what values it is using?
The text was updated successfully, but these errors were encountered: