You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "James Hartig (Jira)" <ji...@apache.org> on 2025/07/03 13:35:00 UTC

[jira] [Updated] (CASSGO-84) Prevent panic when setting different types

     [ https://issues.apache.org/jira/browse/CASSGO-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Hartig updated CASSGO-84:
-------------------------------
    Fix Version/s: 2.x

> Prevent panic when setting different types
> ------------------------------------------
>
>                 Key: CASSGO-84
>                 URL: https://issues.apache.org/jira/browse/CASSGO-84
>             Project: Apache Cassandra Go driver
>          Issue Type: Bug
>          Components: Core
>            Reporter: James Hartig
>            Assignee: James Hartig
>            Priority: Normal
>             Fix For: 2.x
>
>
> This is not a regression as it was an issue in 1.x. If you send the wrong value into Unmarshal in certain cases we will panic instead of return an error. This is because we're not directly checking the types when using reflection before calling Set on a Value. We should be more conservative and assert the types before blindly calling Set.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org