Munish Chouhan

> It would be better to solve this using Surreal SQL statement, instead of truncating the Conda env. ok sure, i will work on it

Tried different ways to add it using SQL, the issue is paring of containerfile ``` { "code": 400, "details": "Request problems detected", "description": "There is a problem with your request....

Tested in locally, getting this error: ``` java.lang.NoSuchMethodError: 'void io.kubernetes.client.openapi.models.V1Pod.validateJsonObject(com.google.gson.JsonObject)' at io.kubernetes.client.openapi.models.V1Pod$CustomTypeAdapterFactory$1.read(V1Pod.java:309) at io.kubernetes.client.openapi.models.V1Pod$CustomTypeAdapterFactory$1.read(V1Pod.java:299) at com.google.gson.TypeAdapter$1.read(TypeAdapter.java:308) at com.google.gson.Gson.fromJson(Gson.java:1361) at com.google.gson.Gson.fromJson(Gson.java:1262) at com.google.gson.Gson.fromJson(Gson.java:1171) at com.google.gson.Gson.fromJson(Gson.java:1137) at io.kubernetes.client.openapi.JSON.deserialize(JSON.java:778) at io.kubernetes.client.openapi.ApiClient.deserialize(ApiClient.java:895) at io.kubernetes.client.openapi.ApiClient.handleResponse(ApiClient.java:1105)...

issue created https://github.com/kubernetes-client/java/issues/3539

Still not working error: ``` io.seqera.wave.exception.BadRequestException: Unexpected build failure - {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods \"build-090844c190db1409-1\" is forbidden: pod rejected: Pod Overhead set without corresponding RuntimeClass defined Overhead","reason":"Forbidden","details":{"name":"build-090844c190db1409-1","kind":"pods"},"code":403} at io.seqera.wave.service.builder.KubeBuildStrategy.build(KubeBuildStrategy.groovy:114) at io.seqera.wave.service.builder.ContainerBuildServiceImpl.launch(ContainerBuildServiceImpl.groovy:203) at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)...

found the solution here https://github.com/quarkusio/quarkus/issues/39934#issuecomment-2099132431

A new issue emerges with this upgrade is how to find pods associated with jobs, because new functions doesnot have filed to mentioned the jobname when fetching pods

> @munishchouhan Maybe it's time to move forward this sure I will start working on it

Tested locally: 1. Build and scan: ``` (base) munish.chouhan@Munishs-MacBook-Pro ~ % kubectl get jobs -n wave-local NAME STATUS COMPLETIONS DURATION AGE bd-322727e313d784e8-1 Running 0/1 41s 41s (base) munish.chouhan@Munishs-MacBook-Pro ~ %...

Tested successfully yin dev: ``` (base) munish.chouhan@Munishs-MacBook-Pro ~ % kubectl get pods -n wave-build NAME READY STATUS RESTARTS AGE bd-17b61f06aa206422-1-5x796 0/1 Completed 0 3h53m bd-455c62e9081e85ab-2-dprkj 0/1 Completed 0 4m58s bd-d61125149884e89d-1-7s5zn...