On June 14, 2022 3:43 pm, Daniel Tschlatscher wrote:
>
>
> On 6/14/22 14:51, Fabian Grünbichler wrote:
>> On June 14, 2022 2:22 pm, Daniel Tschlatscher wrote:
>>> When an attempt was made to clone a locked container the API would
>>> correctly present the error 'CT is locked (disk)' but create th
applied, thanks
On Wed, Jun 08, 2022 at 07:09:59AM +, Hannes Laimer wrote:
> ... and remove '(mounted)' from usage string
>
> Signed-off-by: Hannes Laimer
> ---
> PVE/API2/Disks.pm | 1 +
> PVE/Diskmanage.pm | 7 +++
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/P
applied series and removed the empty lines between the S-o-b and R-b
lines.
On Tue, Jun 14, 2022 at 11:00:10AM +0200, Daniel Tschlatscher wrote:
> When a VM or Container backup was deleted, the .notes file was not
> removed, therefore, over time the dump folder would get polluted with
> notes for
applied, thanks
On Wed, Jun 08, 2022 at 07:10:00AM +, Hannes Laimer wrote:
> Signed-off-by: Hannes Laimer
> ---
> src/panel/DiskList.js | 9 -
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/src/panel/DiskList.js b/src/panel/DiskList.js
> index eb8b1a8..76d92cd 100
--- Begin Message ---
Unfortunately, the docs are still referring to Corosync V2.x.
(https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_ports_used_by_proxmox_ve)
I sent a PR a few weeks ago, but it wasn't applied yet. Was is just
overseen or was there any reason?
Best regards,
Marco
On
Azure AD seems to have a variable authorization code size, depending on
the browser state according to one report in bug #4074 [0].
Sometimes the size is greater than our current limit of 1024, so
increase it to 2048.
The RFC [1] mentions that there is no limit to the code size, but based on
curr
