All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Niteesh G. S." <niteesh.gs@gmail.com>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: John Snow <jsnow@redhat.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	Cleber Rosa <crosa@redhat.com>
Subject: Re: [PATCH v2 0/6] python: AQMP-TUI Prototype
Date: Thu, 15 Jul 2021 00:36:59 +0530	[thread overview]
Message-ID: <CAN6ztm97cJrVZ3=XPr9R8WoepOw81XAGXUO3fHB5nt7L9fWS4w@mail.gmail.com> (raw)
In-Reply-To: <20210713220734.26302-1-niteesh.gs@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2176 bytes --]

Hello all,

UPDATE:  The pipelines have run and all tests passed #336491916
Usually, the pipelines start running as soon as I push my code. But this
time they took longer to start and there was no sign of starting. This is my
first experience with pipelines so I assumed I messed up something from
my side.

Thanks,
Niteesh.

On Wed, Jul 14, 2021 at 3:37 AM G S Niteesh Babu <niteesh.gs@gmail.com>
wrote:

> GitLab:
> https://gitlab.com/niteesh.gs/qemu/-/commits/aqmp-tui-prototype-v1/
> Based-on
> <https://gitlab.com/niteesh.gs/qemu/-/commits/aqmp-tui-prototype-v1/Based-on>:
> <20210701041313.1696009-1-jsnow@redhat.com>
>      [PATCH 00/20] python: introduce Asynchronous QMP package
>
> Updates in V2:
> 1) Moved loop related initialization to 'run' function in 'App' class
> 2) Added a module logger with support in TUI log messages.
> 3) Corrected usage of logging.info and logging.debug
> 4) Added an option in setup.cfg to silent pylint regarding duplicate-code
> 4) Modified the arguments list to the TUI
>
> NOTE: I am not able to get the pipelines running after the v2 changes.
> I was only able to test the changes locally using *make check*.
>
> This patch series introduces AQMP-TUI prototype. This prototype has been
> helpfull in letting us try out different ideas and giving some insights
> into things that we had to take care of in the upcoming TUI. It was also
> helpfull in finding out bugs in the AQMP library.
>
> The intent for this patch series is to get comments on the architectural
> design of the prototype. These comments will lay down the foundation for
> the upcoming TUI.
>
> G S Niteesh Babu (6):
>   python: disable pylint errors for aqmp-tui
>   python: Add dependencies for AQMP TUI
>   python/aqmp-tui: Add AQMP TUI draft
>   python: add optional pygments dependency
>   python/aqmp-tui: add syntax highlighting
>   python: add entry point for aqmp-tui
>
>  python/Pipfile.lock          |  20 ++
>  python/qemu/aqmp/aqmp_tui.py | 342 +++++++++++++++++++++++++++++++++++
>  python/setup.cfg             |  36 +++-
>  3 files changed, 397 insertions(+), 1 deletion(-)
>  create mode 100644 python/qemu/aqmp/aqmp_tui.py
>
> --
> 2.17.1
>
>

[-- Attachment #2: Type: text/html, Size: 3426 bytes --]

  parent reply	other threads:[~2021-07-14 19:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-13 22:07 [PATCH v2 0/6] python: AQMP-TUI Prototype G S Niteesh Babu
2021-07-13 22:07 ` [PATCH v2 1/6] python: disable pylint errors for aqmp-tui G S Niteesh Babu
2021-07-13 22:07 ` [PATCH v2 2/6] python: Add dependencies for AQMP TUI G S Niteesh Babu
2021-07-13 22:07 ` [PATCH v2 3/6] python/aqmp-tui: Add AQMP TUI draft G S Niteesh Babu
2021-07-20 17:57   ` John Snow
2021-07-20 18:01     ` Niteesh G. S.
2021-07-20 19:04   ` John Snow
2021-07-21 20:22     ` Niteesh G. S.
2021-07-13 22:07 ` [PATCH v2 4/6] python: add optional pygments dependency G S Niteesh Babu
2021-07-13 22:07 ` [PATCH v2 5/6] python/aqmp-tui: add syntax highlighting G S Niteesh Babu
2021-07-13 22:07 ` [PATCH v2 6/6] python: add entry point for aqmp-tui G S Niteesh Babu
2021-07-14 19:06 ` Niteesh G. S. [this message]
2021-07-20 19:08   ` [PATCH v2 0/6] python: AQMP-TUI Prototype John Snow
2021-07-21 18:08     ` Niteesh G. S.
2021-07-21 20:03       ` John Snow

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='CAN6ztm97cJrVZ3=XPr9R8WoepOw81XAGXUO3fHB5nt7L9fWS4w@mail.gmail.com' \
    --to=niteesh.gs@gmail.com \
    --cc=crosa@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.