Upgrade to 2.0.0 breaks CI/CD with ValueError
See original GitHub issueHi there, love the library!
We recently spotted an error in our CI/CD pipeline which was occurring after this package upgraded to 2.0.0.post0
, the issue occurs when a OneOfSchema
with fields.Nested
is used on the line (in marshmallow/fields.py:451):
ret, errors = schema.dump(nested_obj, many=self.many,
update_fields=not self.__updated_fields)
The function schema.dump
appears to be returning an empty list
object instead of a MarshalResult
object resulting in:
ValueError: not enough values to unpack (expected 2, got 0)
Hotfix:
Downgrade to 1.0.5
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Troubleshooting CI/CD - GitLab Docs
GitLab provides several tools to help make troubleshooting your pipelines easier. This guide also lists common issues and possible solutions.
Read more >Bug listing with status UNCONFIRMED as at 2022/12/24 17 ...
... Bug:444652 - "Upgrade to OpenRC 0.11.5 breaks services: "You are attempting ... Bug:524636 - "sci-mathematics/soplex-2.0.0 - a Linear Programming (LP) ...
Read more >Release notes & updates – Azure CLI - Microsoft Learn
Learn about the latest Azure Command-Line Interface (CLI) release notes and updates for both the current and beta versions of the CLI.
Read more >Rasa Open Source Change Log
#10673: Catch ValueError for any port values that cannot be cast to integer and ... #10150: Training data version upgraded from 2.0 to...
Read more >Changelog - Python client library | Google Cloud
clarify `%%bigquery`` magics and fix broken link (#508) (eedf93b). update python ... Raise ValueError when BQ Storage is required but missing (#7726).
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
True.
@sloria, do you think 2.0.0 releases should be removed and marshmallow-oneofschema be kept in beta until MA3 is out?
Releasing 2.x as a pre-release doesn’t seem quite right. 2.0 is meant to be a stable release even though it targets marshmallow 3.x. The release lines should be relatively independent. Also, we’re already pinning marshmallow-oneofschema to marshmallow>=3.0.0rc6, so you should get incompatible versions.