config values that are octal strings get interpreted parsed as ints

[vmarunov]

Summary

Unexpected type conversion in presets when using Dagit.

Reproduction

Test solid and pipeline:

from dagster import pipeline, solid, PresetDefinition


@solid(config_schema={'data': [str]})
def test_solid(context):
    ...
    return 0


@pipeline(
    name="test_pipeline",
    preset_defs=[
        PresetDefinition(
            name='dev',
            run_config={
                'solids': {
                    'test_solid': {
                        'config': {
                            'data': ['1234', '0148', '1418', '0183', '4567']}
                    }
                }
            },
            solid_selection=None,
            mode='default',
            tags={}
        )
    ]
)
def test_pipeline():
    test_solid()

This behavior reproduce for values, that starts with 0 and contains 8.
This behavior is only in Dagit. Without dagit, the config is read without errors.

Dagit UI/UX Issue Screenshots

dagit version == 0.12.9

[alangenfeld]

This issue has to do with how the yaml 1.1 spec interprets octal values. They addressed this in the 1.2 version of the spec.
We currently use PyYAML which abides by the 1.1 spec causing these issues.

context: yaml/pyyaml#98

[yuhan]

Closing it as it's less related to Dagster but more related to the third party libs we depend on. Reopen if there's anything we can do.