Skip to content

Conversation

@yegor256
Copy link
Member

fixes #115

@yegor256
Copy link
Member Author

@volodya-lombrozo please, check

Copy link
Collaborator

@volodya-lombrozo volodya-lombrozo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@yegor256 Great thanks for the contribution! Just a single suggestion.

}

func (a *Artifacts) Marshal() *protocol.MessageSendParams {
if a == nil {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@yegor256 I don't think we need to allow a nil receiver here. By doing this, we’re just hiding the original problem: 'Why do we have a nil here at all?'

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@volodya-lombrozo I have no idea, to be honest...

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@yegor256 can we just remove it then?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@volodya-lombrozo I can try, but the bug may not be fixed in this case

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@yegor256 Maybe you can try it locally?

go install

refrax ...

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@volodya-lombrozo tests fail if I remove this check for nil. I can simply drop this PR, but I don't know how to fix the bug otherwise (since this PR is made by Claude Code, not me)

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@yegor256 I suggest closing it. I've successfully reproduced the issue. Thus, I can fix the bug properly

@yegor256 yegor256 closed this Sep 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

invalid memory address or nil pointer dereference

2 participants