public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Mira Limbeck <m.limbeck@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
	Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [PATCH v2 storage 12/15] iscsi: add support for non-persistent discovery
Date: Tue, 26 May 2026 10:36:30 +0200	[thread overview]
Message-ID: <855f8336-66ff-4bd9-823f-3f3572c6dd96@proxmox.com> (raw)
In-Reply-To: <20260523212856.2822353-9-t.lamprecht@proxmox.com>

On 5/23/26 11:28 PM, Thomas Lamprecht wrote:
> On Thu, 30 Apr 2026 19:27:10 +0200, Mira Limbeck wrote:
>> diff --git a/src/PVE/Storage/ISCSIPlugin.pm b/src/PVE/Storage/ISCSIPlugin.pm
>> @@ -226,7 +227,7 @@ sub iscsi_discovery {
>>          # In case of multipath we can stop after receiving targets from any available portal
>> -        last if scalar(keys %$res) > 0;
>> +        last if defined($target) && scalar(keys %$res) > 0;
> 
> $target is declared with `my` inside the outfunc closure a few lines up, so
> it is out of scope here - this doesn't compile under `use strict` ("Global
> symbol $target requires explicit package name"). 13/15 rewrites the line to
> use $target_found, so the final status is again fine, but this commit on its
> own breaks the build. Worth folding that fix into this commit for
> bisectability.
> 
> btw. I like using rebase + exec for ensuring that every commit is clean
> from code format and testing/build POV. It's slightly nicer in rust projects
> where just cargo fmt / check / test calls can be used in a generic fashion
> independent of the specific repo layout, but most of our perl repos are
> rather uniform in its basic targets nowadays, so something like:
> 
>  git rebase --update-refs -x 'printf "\n-------\n"' \
>    -x 'git show --no-patch --oneline --no-decorate HEAD' \
>    -x 'make tidy' \
>    -x 'make -C src test' \
>    origin/master
> 
> should do the trick (btw. --update-refs is normally not required, but
> essential for stacked branches for (sub) series, and it normally doesn't
> hurt to pass).
> We might want to add something like that to the developer wiki, or maybe
> even add a proper (e.g.) "dev-test" make target that combines the four -x
> steps (for me my shell history got me covered ^^).

Thank you for the tip!

I've rebased it so many times, but didn't think of doing an exec and
building every commit on its own.




  reply	other threads:[~2026-05-26  8:36 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-30 17:26 [PATCH v2 cluster/storage/manager 00/15] storage mapping Mira Limbeck
2026-04-30 17:26 ` [PATCH v2 cluster 01/15] mapping: add storage.cfg Mira Limbeck
2026-04-30 17:27 ` [PATCH v2 storage 02/15] mapping: add base plugin Mira Limbeck
2026-04-30 17:35   ` Mira Limbeck
2026-05-23 21:26   ` Thomas Lamprecht
2026-04-30 17:27 ` [PATCH v2 storage 03/15] mapping: add iSCSI plugin Mira Limbeck
2026-04-30 17:27 ` [PATCH v2 storage 04/15] iscsi: introduce mapping support Mira Limbeck
2026-04-30 17:27 ` [PATCH v2 storage 05/15] iscsi: add helper to get local config Mira Limbeck
2026-05-23 21:26   ` Thomas Lamprecht
2026-04-30 17:27 ` [PATCH v2 storage 06/15] iscsi: change functions to handle mappings Mira Limbeck
2026-05-23 21:26   ` Thomas Lamprecht
2026-04-30 17:27 ` [PATCH v2 storage 07/15] iscsi: introduce helper to update discovery db Mira Limbeck
2026-05-11 16:46   ` Samuel Rufinatscha
2026-05-23 21:26   ` Thomas Lamprecht
2026-04-30 17:27 ` [PATCH v2 storage 08/15] iscsi: rework to update discovery db and simplify login Mira Limbeck
2026-05-23 21:26   ` Thomas Lamprecht
2026-05-26  8:42     ` Mira Limbeck
2026-04-30 17:27 ` [PATCH v2 storage 09/15] iscsi: remove stale sessions in non-mapping case Mira Limbeck
2026-05-23 21:26   ` Thomas Lamprecht
2026-05-26  8:48     ` Mira Limbeck
2026-04-30 17:27 ` [PATCH v2 storage 10/15] api: add mapping support Mira Limbeck
2026-05-23 21:26   ` Thomas Lamprecht
2026-04-30 17:27 ` [PATCH v2 storage 11/15] mapping: iscsi: add discovery-portal config option Mira Limbeck
2026-04-30 17:27 ` [PATCH v2 storage 12/15] iscsi: add support for non-persistent discovery Mira Limbeck
2026-04-30 17:38   ` Mira Limbeck
2026-05-23 21:26   ` Thomas Lamprecht
2026-05-26  8:36     ` Mira Limbeck [this message]
2026-04-30 17:27 ` [PATCH v2 storage 13/15] api: add non-persistent iscsi discovery option Mira Limbeck
2026-05-23 21:26   ` Thomas Lamprecht
2026-04-30 17:27 ` [POC v2 storage 14/15] mapping: add zfspool plugin Mira Limbeck
2026-05-23 21:26   ` Thomas Lamprecht
2026-04-30 17:27 ` [PATCH v2 manager 15/15] api: mapping: add storage mapping path Mira Limbeck
2026-05-11 17:05 ` [PATCH v2 cluster/storage/manager 00/15] storage mapping Samuel Rufinatscha
2026-05-23 21:26 ` Thomas Lamprecht

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=855f8336-66ff-4bd9-823f-3f3572c6dd96@proxmox.com \
    --to=m.limbeck@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=t.lamprecht@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal