-
Notifications
You must be signed in to change notification settings - Fork 246
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
using rpyc over rpyc throws an exception #346
Labels
Done
The issue discussion is exhausted and is closed w/ comment
Comments
comrumino
added
To Start
Description reviewed and a maintainer needs "to start" triage
Done
The issue discussion is exhausted and is closed w/ comment
and removed
To Start
Description reviewed and a maintainer needs "to start" triage
labels
Aug 22, 2019
Thanks for reporting the issue! |
Thank you for the quick reply! It did solve the issue, but unfortunately now doing the same as above throws another exception:
|
knowikow
added a commit
to knowikow/rpyc
that referenced
this issue
Sep 13, 2019
comrumino
added a commit
that referenced
this issue
Sep 14, 2019
Added a test for RPyC over RPyC (Tests #346)
Must've missed your comment post "fix", I'll take a look at this issue again soon |
comrumino
added
Triage
Investigation by a maintainer has started
and removed
Done
The issue discussion is exhausted and is closed w/ comment
labels
Sep 14, 2019
comrumino
added
Done
The issue discussion is exhausted and is closed w/ comment
and removed
Triage
Investigation by a maintainer has started
labels
Oct 2, 2019
YuvalEvron
pushed a commit
to weka/rpyc
that referenced
this issue
Oct 27, 2019
* Added warning to _remote_tb when the major version of local and remote mismatch (tomerfiliba-org#332) * Added `include_local_version` to DEFAULT_CONFIG to allow for configurable security controls (e.g. `include_local_traceback`) * Update readme.txt * Added break to client process loop when everything is dead * Increased chunk size to improve multi-client response time and throughput of large data tomerfiliba-org#329 * Improved test for response of client 1 while transferring a large amount of data to client 2 * Cleaned up coding style of test_service_pickle.py * Updated issue template * added vs code testing cfgs; updated gitignore venv * Changed settings.json to use env USERNAME * Name pack casted in _unbox to fix IronPython bug. Fixed tomerfiliba-org#337 * Fixed netref.class_factory id_pack usage per tomerfiliba-org#339 and added test cases * Added .readthedocs.yml and requirements to build * Make OneShotServer terminates after client connection ends * Added unit test for OneShotServer. Fixed tomerfiliba-org#343 * Fixed 2.6 backwards incompatibility for format syntax * Updated change log and bumped version --- 4.1.1 * Added support for chained connections which result in netref being passed to get_id_pack. Fixed tomerfiliba-org#346 * Added tests for get_id_pack * Added a test for issue tomerfiliba-org#346 * Corrected the connection used to inspect a netref * Refactored __cmp__ getattr * Extended rpyc over rpyc unit testing and removed port parameter from TestRestricted * Added comment explaining the inspect for intermediate proxy. Fixed tomerfiliba-org#346 * Improved docstring for serve_threaded to address when and when not to use the method. Done tomerfiliba-org#345 * Release 4.1.2 * Fixed versions referred to in security.rst * link docs instead of mitre * set up logging with a better formatter * fix bug when proxy context-manager is being exited with an exception (#1) * logging: add a rotating file log handler * fix bug when proxy context-manager is being exited with an exception (#1) * logging: add a rotating file log handler
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have a use case where I have a frontend server in a public-facing network and a bunch
of backend servers in an isolated network that's accessible from the frontend server.
I considered using rpyc to handle this case. In order to simulate this I started two classic services on localhost:
And attempted to use rpyc over rpyc:
I should note that connecting directly to the backend works as expected, but it doesn't solve this specific use case.
I'm new to rpyc, so I'm not sure if it's even supposed to work this way.
This is the log from the frontend server:
And this is the log from the backend server:
The text was updated successfully, but these errors were encountered: