kernels-data: allow unknown fields in Metadata (#481)

* kernels-data: allow unknown fields in `Metadata`

Now that we will use `kernels-data` inside `kernels`, we have to allow
unknown fields in metadata. Otherwise the following scenario will break:

1. We publish kernels 0.14.
2. We add a field `foo` to the metadata in kernel-builder 0.15.
3. `kernels` 0.14 will not load metadata from kernel-builder 0.15,
   since it contains an unknown (for 0.14) field `foo`.

* Flip around test: unknown metadata fields must be accepted

* Fix style of kernels-data Python files

Author: danieldk

Makefile

@@ -1,7 +1,7 @@
 .PHONY: style kernel-builder-cli-docs quality
 
 
-export check_dirs := kernels/src kernels/tests
+export check_dirs := kernels/src kernels/tests kernels-data/bindings/python
 
 all: src/kernels/python_depends.json
 

kernels-data/bindings/python/tests/test_kernels_data.py

@@ -124,7 +124,7 @@ def test_metadata_load_cann(tmp_path):
     assert Metadata.load(path).backend.backend_type == Backend.CANN
 
 
-def test_metadata_load_unknown_field_rejected(tmp_path):
+def test_metadata_load_unknown_field_accepted(tmp_path):
     path = tmp_path / "metadata.json"
     path.write_text(
         json.dumps(
@@ -135,8 +135,7 @@ def test_metadata_load_unknown_field_rejected(tmp_path):
             }
         )
     )
-    with pytest.raises(ValueError):
-        Metadata.load(path)
+    Metadata.load(path)
 
 
 def test_metadata_load_malformed(tmp_path):

kernels-data/src/metadata.rs

@@ -14,7 +14,7 @@ pub struct BackendInfo {
 }
 
 #[derive(Debug, Deserialize, Serialize)]
-#[serde(deny_unknown_fields, rename_all = "kebab-case")]
+#[serde(rename_all = "kebab-case")]
 pub struct Metadata {
     #[serde(skip_serializing_if = "Option::is_none")]
     pub version: Option<usize>,