Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Resolve Bridges service communication issues #170

Closed
ostridm opened this issue May 24, 2024 · 0 comments · Fixed by #171
Closed

Resolve Bridges service communication issues #170

ostridm opened this issue May 24, 2024 · 0 comments · Fixed by #171
Assignees
@ostridm
Labels
Type: bug Something isn't working

Comments

@ostridm
Copy link
Contributor

ostridm commented May 24, 2024 •
edited
Loading

This issue is to address some Socket.IO protocol related discrepancies which are preventing sectester-net from successful communication to Bridges service.

The scope:

  1. Bump Socket.IO client to most recent version
  2. Eliminate message pack key naming discrepancy
  3. Perform protocol message reconciliation using message pack formatters
    3.1 to eliminate http headers structure mapping discrepancy
    3.2 to allow HttpMethod enumeration class serialization
    3.3 to satisfy server requirements for string based native enumeration serialization
@ostridm ostridm added the Type: enhancement New feature or request. label May 24, 2024
@ostridm ostridm self-assigned this May 24, 2024
ostridm added a commit that referenced this issue May 24, 2024
@ostridm
feat(repeater): establish bridges integration
472e126 
closes #170
ostridm added a commit that referenced this issue May 24, 2024
@ostridm
feat(repeater): revert accidental modification
373f3d6 
closes #170
@ostridm ostridm mentioned this issue May 24, 2024
Merged
ostridm added a commit that referenced this issue May 24, 2024
@ostridm
feat(repeater): address complexity and duplication issues
3d86749 
closes #170
ostridm added a commit that referenced this issue May 24, 2024
@ostridm
feat(repeater): improve coverage
6838353 
closes #170
ostridm added a commit that referenced this issue May 24, 2024
@ostridm
revert(repeater): revert unwanted changes
5428396 
closes #170
ostridm added a commit that referenced this issue May 24, 2024
@ostridm
feat(repeater): improve coverage
ad15fcb 
closes #170
ostridm added a commit that referenced this issue May 24, 2024
@ostridm
feat(repeater): fix formatting, improve coverage
ea763bd 
closes #170
@ostridm ostridm changed the title Introduce Bridges service integration Resolve Bridges service communication issues May 27, 2024
ostridm added a commit that referenced this issue May 27, 2024
@ostridm
feat(repeater): support stringified enum value serialization
82502d2 
closes #170
@derevnjuk derevnjuk added Type: bug Something isn't working and removed Type: enhancement New feature or request. labels May 31, 2024
ostridm added a commit that referenced this issue May 31, 2024
@ostridm
feat(repeater): address pr comments
57e168a 
closes #170
ostridm added a commit that referenced this issue Jun 1, 2024
@ostridm
feat(repeater): address pr comments
e4a32d0 
closes #170
ostridm added a commit that referenced this issue Jun 1, 2024
@ostridm
feat(repeater): fix formatting get rid unwanted usings
3fe3e1d 
closes #170
ostridm added a commit that referenced this issue Jun 4, 2024
@ostridm
feat(repeater): address pr comments
fb0478d 
closes #170
derevnjuk pushed a commit that referenced this issue Jun 8, 2024
@ostridm
fix(repeater): msgpack protocol mapping (#171)
d7dce84 
closes #170
Co-authored-by: Artem Derevnjuk <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ostridm ostridm

Labels
Type: bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(repeater): resolve bridges service communication NeuraLegion/sectester-net
2 participants
@ostridm @derevnjuk