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 deployed Nebari on commit 2f85ece2b00686de99d94695b55e1c7bb9dde642 (latest commit at time of writing on develop branch, shorly after 2024.3.3 release)
GCPNodeGroupInputVars(
File "/home/balast/miniconda3/envs/possee-neb/lib/python3.11/site-packages/pydantic/main.py", line 164, in __init__
__pydantic_self__.__pydantic_validator__.validate_python(data, self_instance=__pydantic_self__)
pydantic_core._pydantic_core.ValidationError: 1 validation error for GCPNodeGroupInputVars
guest_accelerators.0
Input should be a valid dictionary or instance of GCPGuestAccelerators [type=model_type, input_value=GCPGuestAccelerator(name=...idia-tesla-t4', count=1), input_type=GCPGuestAccelerator]
For further information visit https://errors.pydantic.dev/2.4/v/model_type
I noticed src/_nebari/stages/infrastructure/__init__.py has both a GCPGuestAccelerator class and a GCPGuestAccelerators (plural) class that are nearly identical, and we were passing the wrong one in the code above. It seems this wasn't a problem in pydantic version 1, but it is a problem in pydantic version 2.
To verify this is a quirk of pydantic v1 vs v2 behavior I ran the following code with both pydantic 1.10.12 and 2.4.2. It runs without complain with v1 and throws the error above with v2.
Describe the bug
I deployed Nebari on commit
2f85ece2b00686de99d94695b55e1c7bb9dde642
(latest commit at time of writing on develop branch, shorly after 2024.3.3 release)I got an error similar to this being thrown on
error is something like
I noticed
src/_nebari/stages/infrastructure/__init__.py
has both a GCPGuestAccelerator class and a GCPGuestAccelerators (plural) class that are nearly identical, and we were passing the wrong one in the code above. It seems this wasn't a problem in pydantic version 1, but it is a problem in pydantic version 2.To verify this is a quirk of pydantic v1 vs v2 behavior I ran the following code with both pydantic 1.10.12 and 2.4.2. It runs without complain with v1 and throws the error above with v2.
Expected behavior
No error
OS and architecture in which you are running Nebari
Linux x86-64
How to Reproduce the problem?
See above
Command output
No response
Versions and dependencies used.
No response
Compute environment
None
Integrations
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: