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.

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

Internal Error Attempting Rlink Forwarding #2076

Open
Skully17 opened this issue May 2, 2023 · 1 comment
Open

Internal Error Attempting Rlink Forwarding #2076

Skully17 opened this issue May 2, 2023 · 1 comment
Labels
bug needs-investigation rlinks Router-to-router links and multi-node operation.

Comments

@Skully17
Copy link
Contributor

Skully17 commented May 2, 2023

Hello,

I have a simple setup of a “local” Crossbar router which connects to a “remote” Crossbar router using Rlink. When calling/publishing from the “remote” router to a URL that was registered/subscribed to, I am getting this error:
RLinkRemoteSession.onUserError(): "RuntimeError: Internal error attempting rlink forwarding"

I can see that this is being raised here and it’s because details does not have a caller, caller_authrole or caller_authid:

raise RuntimeError("Internal error attempting rlink forwarding")

I can’t work out why these values are not being set or even how they are set at all. How are details passed to the on_call method here:

def on_call(*args, **kwargs):

I can see that this method is registered here but details isn't passed there, just reference in RegisterOptions:

reg = yield other.register(on_call,

Does RegisterOptions supply the details?

Just to be clear, the same process works when the “local” router calls/registers to a URI that has been registered/subscribed to on the “remote” router and I can see that the caller variables in details have values.

@Skully17
Copy link
Contributor Author

Skully17 commented May 19, 2023

This comment describes exactly what tripped me up:
#1909 (comment)

Would it be agreeable if the error message "Internal error attempting rlink forwarding" was edited to include a suggestion to change the role's disclosures to "true" if this is not expected behaviour?

@oberstet oberstet added bug needs-investigation rlinks Router-to-router links and multi-node operation. labels May 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug needs-investigation rlinks Router-to-router links and multi-node operation.
Projects
None yet
Development

No branches or pull requests

2 participants