17 Replies
seems to be related to "allowedCudaVersions" changing in some way
I think its better to remove allowedCudaVersions from your payload than to leave it empty
Can’t control that because it is how the UI is built
oh damn, yeah sorry oversight from my part, I think @nerdylive or @justin [Not Staff] can help by pinging the UI dev(s).
@zkreutzjanz @flash-singh Bug? I think if you want to provide more info @zkreutzjanz can maybe put under #🧐|feedback as a [Bug]
@zkreutzjanz can you share endpoint id? we can try to replicate using that
6fiz1j5a45xg0u
Looks like only reason why is because it now adds
which is invalid graphql maybe?
oh empty one is not allowed, @Zeke
But also fails when you add fyi
see:
"allowedCudaVersions":"12.1,12.2"
hm, I can't seem to replicate this on my own, can you detail what steps in the UI you take to reproduce this issue?
empty string works just fine for me
doesn't seem to be allowedCudaVersions causing the issue
might be that the GPU IDs you're sending aren't quite right?
is it possible you reached max workers?
You never really know what the actual problem is with GraphQL, it never gives a useful error. It is a nightmare trying to debug GraphQL payloads.
No, have plenty of workers left
Just hit three dots, clone, deploy
And here is the exact request:
and response
same response here so not a gpu is issue:
@kaj did we get to the bottom of this?
not yet, looking into a possible solution