From: Matthieu Malvache <matthieu@ma2t.com>
To: Matthias Heiserer <m.heiserer@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH container 1/1] vnc: Allow custom timeout value in vncproxy method
Date: Fri, 3 Mar 2023 14:43:12 +0100 [thread overview]
Message-ID: <C6D85841-DFCE-498B-83FE-1E87AC50F824@ma2t.com> (raw)
In-Reply-To: <3e15f154-8e08-e13c-e844-d445eee06940@proxmox.com>
Hi Matthias,
Thank you for your email. I sent the CLA earlier this afternoon.
This is actually the first time I'm contributing to a project like this, so thank you for your guidance
and pointing out the issues with the patch.
Regarding the tab issue, should I submit a fix for this separately, or can I include it in the same patch?
Also, could you please let me know how I can "rename" the subject from [PATCH container] to [PATCH qemu-server]?
Thank you again for your help.
Matthieu Malvache
Ma2t.
matthieu@ma2t.com
> Le 3 mars 2023 à 13:06, Matthias Heiserer <m.heiserer@proxmox.com> a écrit :
>
> Hi,
>
> Did you already submit a CLA? https://pve.proxmox.com/wiki/Developer_Documentation#Software_License_and_Copyright
>
> I noticed two issues:
>
> This patch is not for pve-container, but rather qemu-server, so the subject should include [PATCH qemu-server] rather than [PATCH container]
>
> On 03.03.2023 12:16, Matthieu Malvache wrote:
>> This commit adds support for a custom timeout value in the 'vncproxy'
>> method of the Proxmox PVE REST API. The timeout can be specified using
>> the 'timeout' parameter and defaults to 10 seconds if not set.
>> Signed-off-by: Matthieu Malvache <matthieu@ma2t.com>
>> ---
>> PVE/API2/Qemu.pm | 10 ++++++++--
>> 1 file changed, 8 insertions(+), 2 deletions(-)
>> diff --git a/PVE/API2/Qemu.pm b/PVE/API2/Qemu.pm
>> index 587bb22..4ca5842 100644
>> --- a/PVE/API2/Qemu.pm
>> +++ b/PVE/API2/Qemu.pm
>> @@ -2164,6 +2164,13 @@ __PACKAGE__->register_method({
>> default => 0,
>> description => "Generates a random password to be used as ticket instead of the API ticket.",
>> },
>> + timeout => {
>> + optional => 1,
>> + type => 'integer',
>> + minimum => 5,
>> + default => 10,
>> + description => "Timeout in seconds for the vnc proxy connection.",
>> + },
> The indent here should be (\tab.... is a tab, \w.. are four spaces)
> \tab....\w..timeout
> \tab....\tab....optional => 1
>
> so the difference in indents is always 4 spaces (1 tab = 8 spaces wide)
>> },
>> },
>> returns => {
>> @@ -2192,6 +2199,7 @@ __PACKAGE__->register_method({
>> my $vmid = $param->{vmid};
>> my $node = $param->{node};
>> my $websocket = $param->{websocket};
>> + my $timeout = $param->{timeout};
>> my $conf = PVE::QemuConfig->load_config($vmid, $node); # check if VM exists
>> @@ -2226,8 +2234,6 @@ __PACKAGE__->register_method({
>> my $port = PVE::Tools::next_vnc_port($family);
>> - my $timeout = 10;
>> -
>> my $realcmd = sub {
>> my $upid = shift;
>>
> Other than that, I'd say it looks fine.
>
next prev parent reply other threads:[~2023-03-03 13:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 11:16 [pve-devel] [PATCH container 0/1] Add support for custom timeout " Matthieu Malvache
2023-03-03 11:16 ` [pve-devel] [PATCH container 1/1] vnc: Allow custom timeout value " Matthieu Malvache
2023-03-03 12:06 ` Matthias Heiserer
2023-03-03 13:43 ` Matthieu Malvache [this message]
2023-03-03 15:07 ` Matthias Heiserer
2023-03-03 14:50 ` Dominik Csapak
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=C6D85841-DFCE-498B-83FE-1E87AC50F824@ma2t.com \
--to=matthieu@ma2t.com \
--cc=m.heiserer@proxmox.com \
--cc=pve-devel@lists.proxmox.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 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.