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
Support functionalities to add user-provided, original labels. (#446)
* WIP: implement GCSObjectMetadataClient class to attach custom-metadata to gcs-object.
* WIP: change dump method interface.
* WIP: add user_provided_gcs_labels parameter to TaskOnKart.
* Test: add test of GCSObjectMetadataClient.
* feat: dealed with nits PR comments.
* feat: Remove user_provided_labels feature. This feature will be supported another PR.
* for-PR: apply almost all comments.
* fix: change Dict to dict.
* feat: add gokart specific parameter serialize test.
* fix: fix testcases with literals and more meaningful assertion.
* feat: add mock testcase.
* fix: fix CI errors.
* feat: deal with pr comments, and modify testcases.
* feat: deal with kitagry comments.
* feat: Supportfunctionalities to add user specific original labels and namespace support feature and test it.
* feat: remove namespace feature.
* feat: Deal with kitagry PR comments. Added type annotations.
* CI: apply ruff
* feat: rename user_provided labels to custom_labels.
* CI: apply ruff
* feat: Deal with PR comments. Change _normalize_labels signature and apply changes to test.
* feat: deal with PR comments.
* feat: deal with PR comments.
* CI: fix tests
* feat: deal with PR comments.
* CI: apply ruff
* feat: deal with kitagry PR comments, responsibility separation.
* feat: deal with yokomotod PR comments, use hoge | None expression instead of Optional.
---------
Co-authored-by: 荒木 太一 <taichi.araki@m3-2024mac75.local>
# There is a possibility that the keys of user-provided labels(custom_labels) may conflict with those generated from task parameters (task_params_labels).
101
+
# However, users who utilize custom_labels are no longer expected to search using the labels generated from task parameters.
102
+
# Instead, users are expected to search using the labels they provided.
103
+
# Therefore, in the event of a key conflict, the value registered by the user-provided labels will take precedence.
0 commit comments