DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jeremy Spewock <jspewock@iol.unh.edu>
To: Nicholas Pratte <npratte@iol.unh.edu>
Cc: paul.szczepanek@arm.com, wathsala.vithanage@arm.com,
	probb@iol.unh.edu,  Luca.Vizzarro@arm.com, thomas@monjalon.net,
	juraj.linkes@pantheon.tech,  Honnappa.Nagarahalli@arm.com,
	yoan.picchi@foss.arm.com, dev@dpdk.org
Subject: Re: [PATCH v3 2/3] dts: Add missing docstring from XML-RPC server
Date: Mon, 17 Jun 2024 11:06:51 -0400	[thread overview]
Message-ID: <CAAA20UStBeb+aKgMGBHFEiP8ZH6qXsGCG1bQsEJUQXA+TBC99A@mail.gmail.com> (raw)
In-Reply-To: <CAKXZ7eibX0ettdPZc2e4J8pNy5-FcamTPtCONgZVJi7pzWqDDQ@mail.gmail.com>

On Fri, Jun 14, 2024 at 4:48 PM Nicholas Pratte <npratte@iol.unh.edu> wrote:
>
> Just a small nitpick. Otherwise:
>
> Reviewed-by: Nicholas Pratte <npratte@iol.unh.edu>
>
> <snip>
> >  class QuittableXMLRPCServer(SimpleXMLRPCServer):
> > -    """Basic XML-RPC server.
> > +    r"""Basic XML-RPC server.
> >
> >      The server may be augmented by functions serializable by the :mod:`marshal` module.
> > +
> > +    Example:
> > +        ::
> > +
> > +            def hello_world():
> > +                # to be sent to the XML-RPC server
> > +                print("Hello World!")
> > +
> > +            # start the XML-RPC server on the remote node
> > +            # the example assumes you're already connect to a tg_node
>
> This just a very small nitpick, but you wrote 'connect' when it should
> be 'connected.'

Good catch, I'll fix this.

>
> > +            # this is done by starting a Python shell on the remote node
> > +            from framework.remote_session import PythonShell
>
> This comment is related to the one I made above, but maybe you could
> move the above comment 'assumes you're already connected to a tg_node'
> on this line instead of where it is right now. I had to rescan this a
> couple times when reading. Again, this is just an extremely minuscule
> nitpick, but I figured I'd bring it up, in any case.

I agree when looking at this more in-depth that the order should be
swapped, this comment looks like a continuation of the first line, but
then there is another just kind of thrown in-between. good catch.

>
> > +            session = tg_node.create_interactive_shell(PythonShell, timeout=5, privileged=True)
> > +
> > +            # then importing the modules needed to run the server
> > +            # and the modules for any functions later added to the server
> > +            session.send_command("import xmlrpc")
> > +            session.send_command("from xmlrpc.server import SimpleXMLRPCServer")
> > +
> > +            # sending the source code of this class to the Python shell
> > +            from xmlrpc.server import SimpleXMLRPCServer
> > +            src = inspect.getsource(QuittableXMLRPCServer)
> > +            src = "\n".join([l for l in src.splitlines() if not l.isspace() and l != ""])
> > +            spacing = "\n" * 4
> > +            session.send_command(spacing + src + spacing)
> > +
> > +            # then starting the server with:
> > +            command = "s = QuittableXMLRPCServer(('0.0.0.0', {listen_port}));s.serve_forever()"
> > +            session.send_command(command, "XMLRPC OK")
> > +
> > +            # now the server is running on the remote node and we can add functions to it
> > +            # first connect to the server from the execution node
> > +            import xmlrpc.client
> > +            server_url = f"http://{tg_node.config.hostname}:8000"
> > +            rpc_server_proxy = xmlrpc.client.ServerProxy(server_url)
> > +
> > +            # get the function bytes to send
> > +            import marshal
> > +            function_bytes = marshal.dumps(hello_world.__code__)
> > +            rpc_server_proxy.add_rpc_function(hello_world.__name__, function_bytes)
> > +
> > +            # now we can execute the function on the server
> > +            xmlrpc_binary_recv: xmlrpc.client.Binary = rpc_server_proxy.hello_world()
> > +            print(str(xmlrpc_binary_recv))
> >      """
> >
> >      def __init__(self, *args, **kwargs):
> > --
> > 2.45.1
> >

  reply	other threads:[~2024-06-17 15:07 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-12 17:25 [PATCH v1 0/2] Improve interactive shell output gathering jspewock
2024-03-12 17:25 ` [PATCH v1 1/2] dts: Improve output gathering in interactive shells jspewock
2024-04-03  9:00   ` Juraj Linkeš
2024-04-08 16:20     ` Jeremy Spewock
2024-04-10 10:20       ` Juraj Linkeš
2024-03-12 17:25 ` [PATCH v1 2/2] dts: Add missing docstring from XML-RPC server jspewock
2024-04-24 13:42   ` Patrick Robb
2024-05-01 16:16 ` [PATCH v2 0/3] Improve interactive shell output gathering and logging jspewock
2024-05-01 16:16   ` [PATCH v2 1/3] dts: Improve output gathering in interactive shells jspewock
2024-05-09  9:57     ` Luca Vizzarro
2024-05-13 14:58     ` Juraj Linkeš
2024-05-15 19:13       ` Jeremy Spewock
2024-05-01 16:16   ` [PATCH v2 2/3] dts: Add missing docstring from XML-RPC server jspewock
2024-05-09  9:57     ` Luca Vizzarro
2024-05-13 14:58     ` Juraj Linkeš
2024-05-01 16:16   ` [PATCH v2 3/3] dts: Improve logging for interactive shells jspewock
2024-05-09  9:57     ` Luca Vizzarro
2024-05-13 15:02     ` Juraj Linkeš
2024-05-15 19:23       ` Jeremy Spewock
2024-05-09  9:59   ` [PATCH v2 0/3] Improve interactive shell output gathering and logging Luca Vizzarro
2024-05-20 15:08     ` Nicholas Pratte
2024-05-29 19:49   ` [PATCH v3 " jspewock
2024-05-29 19:49     ` [PATCH v3 1/3] dts: Improve output gathering in interactive shells jspewock
2024-05-31 16:49       ` Luca Vizzarro
2024-06-07 13:37       ` Juraj Linkeš
2024-06-14 20:58       ` Nicholas Pratte
2024-06-17 15:00       ` Luca Vizzarro
2024-05-29 19:49     ` [PATCH v3 2/3] dts: Add missing docstring from XML-RPC server jspewock
2024-05-31 16:50       ` Luca Vizzarro
2024-06-07 13:37       ` Juraj Linkeš
2024-06-14 20:48       ` Nicholas Pratte
2024-06-17 15:06         ` Jeremy Spewock [this message]
2024-06-17 15:00       ` Luca Vizzarro
2024-05-29 19:49     ` [PATCH v3 3/3] dts: Improve logging for interactive shells jspewock
2024-05-31 16:50       ` Luca Vizzarro
2024-06-07 13:38       ` Juraj Linkeš
2024-06-14 20:26       ` Nicholas Pratte
2024-06-17 15:01       ` Luca Vizzarro
2024-06-20 17:36   ` [PATCH v4 0/3] Improve interactive shell output gathering and logging jspewock
2024-06-20 17:36     ` [PATCH v4 1/3] dts: Improve output gathering in interactive shells jspewock
2024-06-21  9:10       ` Juraj Linkeš
2024-06-20 17:36     ` [PATCH v4 2/3] dts: Add missing docstring from XML-RPC server jspewock
2024-06-21  9:12       ` Juraj Linkeš
2024-06-20 17:36     ` [PATCH v4 3/3] dts: Improve logging for interactive shells jspewock
2024-06-21  9:23       ` Juraj Linkeš
2024-06-21 15:31       ` Patrick Robb

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAAA20UStBeb+aKgMGBHFEiP8ZH6qXsGCG1bQsEJUQXA+TBC99A@mail.gmail.com \
    --to=jspewock@iol.unh.edu \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=Luca.Vizzarro@arm.com \
    --cc=dev@dpdk.org \
    --cc=juraj.linkes@pantheon.tech \
    --cc=npratte@iol.unh.edu \
    --cc=paul.szczepanek@arm.com \
    --cc=probb@iol.unh.edu \
    --cc=thomas@monjalon.net \
    --cc=wathsala.vithanage@arm.com \
    --cc=yoan.picchi@foss.arm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).