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

Bug into REAR provider which limits the availability of peering candidates in the REAR consumer #38

Open
fracappa opened this issue Apr 17, 2024 · 0 comments
Open

Bug into REAR provider which limits the availability of peering candidates in the REAR consumer #38

fracappa opened this issue Apr 17, 2024 · 0 comments
Assignees
@fracappa @LorenzoMoro @andreacv98
Labels
bug Something isn't working low priority Low priority issue question Further information is requested

Comments

@fracappa
Copy link
Contributor

Hi everyone.

The aims of this issue is to report a bug present inside the provider implementation of the REAR protocol.

More specifically, if a provider receives a request that matches several available flavors, it only returns one out of many.

This behavior should be fixed as it limits the availability of peering candidates list on the consumer side.

Regards,
Francesco
@fracappa fracappa added the bug Something isn't working label Apr 17, 2024
@fracappa fracappa closed this as completed May 9, 2024
@fracappa fracappa reopened this May 9, 2024
@fracappa fracappa added low priority Low priority issue question Further information is requested labels May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@fracappa fracappa

@LorenzoMoro LorenzoMoro

@andreacv98 andreacv98

Labels
bug Something isn't working low priority Low priority issue question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@fracappa @LorenzoMoro @andreacv98