Skip to content

[BUG] Logger is not very usefull when receiving corrupted data. #370

Description

@Hadatko

Describe the bug

When corrupted data are received (crc check fail) logger action is skipped. We now that fail occured but we cannot figure out why as we don't see message.

To Reproduce

Send message with wrong crc to server.

Expected behavior

I think we can refactor code a bit to developer decide if he want log all messages or only good messages and moved code to better place than client/server initialization as it is really tight to transport.

Screenshots

image

Desktop (please complete the following information):

  • OS:
  • eRPC Version:

Steps you didn't forgot to do

  • I checked if there is no related issue opened/closed.
  • I checked that there doesn't exist opened PR which is solving this issue.

Additional context

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions