Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem serializing some Kueue types for logging #4137

Open
gabesaba opened this issue Feb 3, 2025 · 0 comments
Open

Problem serializing some Kueue types for logging #4137

gabesaba opened this issue Feb 3, 2025 · 0 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@gabesaba
Copy link
Contributor

gabesaba commented Feb 3, 2025

What happened:
Observing error messages like the following in logs:

"nominatedAssignmentError": "json: unsupported type: resources.FlavorResourceQuantities"
"resourcesError": "json: unsupported type: resources.FlavorResourceQuantities"
"resourcesRequiringPreemptionError": "json: unsupported type: sets.Set[[sigs.k8s.io/kueue/pkg/resources.FlavorResource](http://sigs.k8s.io/kueue/pkg/resources.FlavorResource)]"
"usageError": "json: unsupported type: resources.FlavorResourceQuantities"

here are the lines, corresponding to v0.10.0

cache/snapshot.go:64
cache/snapshot.go:73
preemption/preemption.go:346
scheduler/logging.go:43

What you expected to happen:
These types should be serialized properly

How to reproduce it (as minimally and precisely as possible):
Run integration tests with higher log verbosity, grep for json: unsupported type

Anything else we need to know?:
The scope of this bug includes identifying other types we fail to serialize - the list above is not necessarily exhaustive - and fixing those too

Environment:

  • Kueue version (use git describe --tags --dirty --always): v0.10.0
@gabesaba gabesaba added the kind/bug Categorizes issue or PR as related to a bug. label Feb 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

1 participant