Skip to content
This repository has been archived by the owner on Mar 27, 2024. It is now read-only.

refactor: Add handling inbound problem report messages inside legacy-connection protocol #3369

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Abdulbois
Copy link
Contributor

Title:
Problem report inside legacy connection

Summary:

  • Add handling problem report messages inside protocol
  • Cover with unit tests

@Abdulbois Abdulbois changed the title feat: Add handling inbound problem report messages. Add unit tests feat: Add handling inbound problem report messages inside legacy-connection protocl Sep 12, 2022
@Abdulbois Abdulbois changed the title feat: Add handling inbound problem report messages inside legacy-connection protocl feat: Add handling inbound problem report messages inside legacy-connection protocol Sep 12, 2022
@Abdulbois Abdulbois force-pushed the problem-report-inside-legacy-connection branch from cf99045 to 9bda127 Compare September 12, 2022 07:05
@Abdulbois Abdulbois closed this Sep 12, 2022
@Abdulbois Abdulbois reopened this Sep 12, 2022
@Abdulbois Abdulbois force-pushed the problem-report-inside-legacy-connection branch from 9bda127 to 5f500ec Compare September 12, 2022 07:30
…ection protocol. Add unit tests

Signed-off-by: Abdulbois <abdulbois.tursunov@avast.com>
@Abdulbois Abdulbois force-pushed the problem-report-inside-legacy-connection branch from 5f500ec to ad977a6 Compare September 12, 2022 07:38
@Abdulbois Abdulbois changed the title feat: Add handling inbound problem report messages inside legacy-connection protocol refactor: Add handling inbound problem report messages inside legacy-connection protocol Sep 12, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant