TypeError: e.getCondition is not a function

[bingwork]

I could only get these on windows when jump to a job that created by volcano.

Component stack:

at l (https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:1402964)
at I (https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:1396458)
at b (https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:9663813)
at l (https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:1402964)
at I (https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:1396458)
at l (https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:1402964)
at re (https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:2:855769)
at https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:12355780
at div
at https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:10459272
at t (https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:5455435)
at https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:12355780
at https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:9903851
at l (https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:1402964)

Error stack:

TypeError: e.getCondition is not a function
at https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:10083578
at https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:10082508
at ct (https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:1450747)
at t.computeValue_ (https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:1448204)
at t.trackAndCompute (https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:1448049)
at t.get (https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:1447295)
at https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:10319892
at Array.filter ()
at https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:10319871
at ct (https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:1450747)

[Tixon123]

Hello bingwork,

Thank you for reaching out to Lens GitHub!

I'll let our Dev team about this issue.

Thank you for the reporting.

Best Regards,
Tikhon Kudinov
Lens Support Engineer
Mirantis, Inc

[dechegaray]

May we know in which version of Lens are you currently on? @bingwork

[bingwork]

May we know in which version of Lens are you currently on? @bingwork

hi, @dechegaray , the information is below:

Lens: 2024.10.171859-latest
Electron: 31.6.0
Chrome: 126.0.6478.234
Node: 20.17.0
© 2024 Mirantis, lnc.

[dechegaray]

May we know in which version of Lens are you currently on? @bingwork

hi, @dechegaray , the information is below:

Lens: 2024.10.171859-latest Electron: 31.6.0 Chrome: 126.0.6478.234 Node: 20.17.0 © 2024 Mirantis, lnc.

Would you mind giving a try to our latest version 2024.11.131815-latest? Currently only available through direct download from our Website.

If the problem persist, could you please provide a dummy job for us to replicate the issue? is it something like https://volcano.sh/en/docs/vcjob ?

And, does this happen when:

• opening the list of jobs
• opening the details panel of the aforementioned job
• opening the details panel of the pod created by the job?

Just trying to narrow down how to best reproduce the issue, so we can quickly fix it on engineering as there are a couple of places where the getCondition could be triggering this...

[panuhorsmalahti]

Can you paste the kubectl describe of this job?

[bingwork]

May we know in which version of Lens are you currently on? @bingwork

hi, @dechegaray , the information is below:
Lens: 2024.10.171859-latest Electron: 31.6.0 Chrome: 126.0.6478.234 Node: 20.17.0 © 2024 Mirantis, lnc.

Would you mind giving a try to our latest version 2024.11.131815-latest? Currently only available through direct download from our Website.

If the problem persist, could you please provide a dummy job for us to replicate the issue? is it something like https://volcano.sh/en/docs/vcjob ?

And, does this happen when:

• opening the list of jobs
• opening the details panel of the aforementioned job
• opening the details panel of the pod created by the job?

Just trying to narrow down how to best reproduce the issue, so we can quickly fix it on engineering as there are a couple of places where the getCondition could be triggering this...

@dechegaray Thank you for your reply, and sorry, I can't reproduce this issue at the moment because we are using vcluster, and Volcano has been uninstalled. It might have been due to our previous vcluster not supporting CRD.

[dechegaray]

May we know in which version of Lens are you currently on? @bingwork

hi, @dechegaray , the information is below:
Lens: 2024.10.171859-latest Electron: 31.6.0 Chrome: 126.0.6478.234 Node: 20.17.0 © 2024 Mirantis, lnc.

Would you mind giving a try to our latest version 2024.11.131815-latest? Currently only available through direct download from our Website.
If the problem persist, could you please provide a dummy job for us to replicate the issue? is it something like https://volcano.sh/en/docs/vcjob ?
And, does this happen when:

• opening the list of jobs
• opening the details panel of the aforementioned job
• opening the details panel of the pod created by the job?

Just trying to narrow down how to best reproduce the issue, so we can quickly fix it on engineering as there are a couple of places where the getCondition could be triggering this...

@dechegaray Thank you for your reply, and sorry, I can't reproduce this issue at the moment because we are using vcluster, and Volcano has been uninstalled. It might have been due to our previous vcluster not supporting CRD.

Sounds good. Let us know if you ever face this again. Anyways we created an item in our backlog to verify unhandled functions when pulling the job condition