-
Notifications
You must be signed in to change notification settings - Fork 122
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.
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
Allow the same endpoint number to be reused for IN and OUT endpoints separately #1
Conversation
separately, effectively allowing two endpoints with the same number - numbers are no unique, only endpoint addresses are.
I still get this problem: |
@half2me it seems like you didn't pull the right branch - that error message was removed in this pull request, so I wouldn't expect to see ever it if you had the correct branch. |
@zagrodzki
|
@half2me that should definitely have been enough, you can also check that your result of "git branch -v" matches the commit ID from the pull request: same-endpoint-in-out 2b78100 Allow the same endpoint number ... If that's the case, then I think the problem might be with your paths setup, i.e. the package you use when compilng your binary is not from the same directory that you showed above - maybe your compilation runs a "go get" somewhere outside of that dir?. I don't really want to spend time here debugging local client setup, so if you don't come up with anything useful, you can just wait until this pull req is merged into master, and then try again. |
FWIW, that error message is present in interface.go in the master branch, line 120. In the same-endpoint-in-out branch, the string "is not an" does not occur anywhere in the code. |
@zagrodzki Gogland EAP made a new GOPATH and was using that... damn :) |
@stapelberg an alternative approach would be to have two separate InEndpoints/OutEndpoints maps in the interface descriptor, indexed by endpoint number. That would avoid the "EndpointAddress" type and having an "Address" field in the endpoint descriptor. Let me know if you think that would be a cleaner approach. |
@zagrodzki So the endpoint problem is fixed, but now I get this, when setting |
@half2me please file a separate issue for that one, to keep the conversations focused. |
..., effectively allowing two endpoints with the same number - endpoint numbers are not unique, only endpoint addresses are.