Heath C

@aurelien-brevet I switched around the JSON Schema a little bit in this [playground](https://rjsf-team.github.io/react-jsonschema-form/#eyJmb3JtRGF0YSI6eyJwb3NzaWJsZVZhbHVlcyI6W119LCJzY2hlbWEiOnsidHlwZSI6Im9iamVjdCIsInByb3BlcnRpZXMiOnsicG9zc2libGVWYWx1ZXMiOnsidHlwZSI6ImFycmF5IiwiaXRlbXMiOnsib25lT2YiOlt7InRpdGxlIjoiTnVtYmVyIiwidHlwZSI6Im51bWJlciJ9LHsidGl0bGUiOiJTdHJpbmciLCJ0eXBlIjoic3RyaW5nIn1dfX19fSwidWlTY2hlbWEiOnt9LCJ0aGVtZSI6ImRlZmF1bHQiLCJsaXZlU2V0dGluZ3MiOnsic2hvd0Vycm9yTGlzdCI6InRvcCIsInZhbGlkYXRlIjpmYWxzZSwiZGlzYWJsZWQiOmZhbHNlLCJub0h0bWw1VmFsaWRhdGUiOmZhbHNlLCJyZWFkb25seSI6ZmFsc2UsIm9taXRFeHRyYURhdGEiOmZhbHNlLCJsaXZlT21pdCI6ZmFsc2UsImV4cGVyaW1lbnRhbF9kZWZhdWx0Rm9ybVN0YXRlQmVoYXZpb3IiOnsiYXJyYXlNaW5JdGVtcyI6InBvcHVsYXRlIiwiZW1wdHlPYmplY3RGaWVsZHMiOiJwb3B1bGF0ZUFsbERlZmF1bHRzIn19fQ==) and am wondering if this works for you? Note that `oneOf`s are turned into dropdowns by default...

@aurelien-brevet Good point. I believe that this [playground](https://rjsf-team.github.io/react-jsonschema-form/#eyJmb3JtRGF0YSI6e30sInNjaGVtYSI6eyJ0eXBlIjoib2JqZWN0Iiwib25lT2YiOlt7InRpdGxlIjoiTnVtYmVycyIsInByb3BlcnRpZXMiOnsicG9zc2libGVWYWx1ZXMiOnsidHlwZSI6ImFycmF5IiwiaXRlbXMiOnsidHlwZSI6Im51bWJlciJ9fX19LHsidGl0bGUiOiJTdHJpbmdzIiwicHJvcGVydGllcyI6eyJwb3NzaWJsZVZhbHVlcyI6eyJ0eXBlIjoiYXJyYXkiLCJpdGVtcyI6eyJ0eXBlIjoic3RyaW5nIn19fX1dfSwidWlTY2hlbWEiOnt9LCJ0aGVtZSI6ImRlZmF1bHQiLCJsaXZlU2V0dGluZ3MiOnsic2hvd0Vycm9yTGlzdCI6InRvcCIsInZhbGlkYXRlIjpmYWxzZSwiZGlzYWJsZWQiOmZhbHNlLCJub0h0bWw1VmFsaWRhdGUiOmZhbHNlLCJyZWFkb25seSI6ZmFsc2UsIm9taXRFeHRyYURhdGEiOmZhbHNlLCJsaXZlT21pdCI6ZmFsc2UsImV4cGVyaW1lbnRhbF9kZWZhdWx0Rm9ybVN0YXRlQmVoYXZpb3IiOnsiYXJyYXlNaW5JdGVtcyI6InBvcHVsYXRlIiwiZW1wdHlPYmplY3RGaWVsZHMiOiJwb3B1bGF0ZUFsbERlZmF1bHRzIn19fQ==) example does what you want

You could also use the `uiOptions` to pass disabled to the `SubmitButton`: ``` uiSchema = { submitButtonOptions: { disabled: true, }, }; ```

@Nezteb So if I select `Rejected` the second time it works. I know that is a crappy work-around, but it might give you a clue on how to fix it?

@tyrdavis Is this something you feel comfortable fixing for us?

@elbywan I noticed that this [PR](https://github.com/elbywan/wretch/pull/204) related to the babel traverse upgrade failed one of your build pipelines... Did that somehow indicate this issue?

I can confirm that upgrading to `terser-webpack-plugin@4` worked for me too

@urugator I'm still waiting for this. Can you rebase and merge?

We were seeing the same issue on our `gitlab` runners and we were forced to pinned node to `18.18.x` to avoid it. This seems to be an issue with node...

I'm still seeing issue with this on my gitlab pipelines as well, inside of Dockerfiles within the CI/CD pipelines. I am using `10.5.0`: ``` #15 470.1 npm ERR! code ETIMEDOUT...