You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Sankeerthan Kasilingam (Jira)" <ji...@apache.org> on 2022/01/16 09:06:00 UTC

[jira] [Commented] (YUNIKORN-51) cast failures are not handled correctly

    [ https://issues.apache.org/jira/browse/YUNIKORN-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17476756#comment-17476756 ] 

Sankeerthan Kasilingam commented on YUNIKORN-51:
------------------------------------------------

Hi [~wilfreds] /[~wilfreds],

I'm new to YUNIKORN. Can i giveĀ  try this issue? I'll inform if i couldn't do it.

Thanks,

Sankeerthan

> cast failures are not handled correctly
> ---------------------------------------
>
>                 Key: YUNIKORN-51
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-51
>             Project: Apache YuniKorn
>          Issue Type: Bug
>          Components: core - scheduler
>            Reporter: Wilfred Spiegelenburg
>            Priority: Critical
>              Labels: newbie
>         Attachments: cast_panic.go
>
>
> While reviewing the code for YUNIKORN-47 I noticed that we are not correctly handling cast errors which could cause panics.
>  In all cases we use the proper cast like this:
> {code:java}
> obj, ok := i.(*T)
> {code}
> We check the value of ok but do not handle the fact correctly that we can get a nil back which could cause a panic later when we us it.
> examples: {{scheduler.processNodeEvent()}}
> test code attached to show the issue.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org