Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qZBn5-004YM3-D0 for pgadmin-hackers@arkaria.postgresql.org; Thu, 24 Aug 2023 14:58:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qZBn3-009ePz-D7 for pgadmin-hackers@arkaria.postgresql.org; Thu, 24 Aug 2023 14:58:29 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qZBn3-009ePl-29 for pgadmin-hackers@lists.postgresql.org; Thu, 24 Aug 2023 14:58:28 +0000 Received: from mail-pg1-x532.google.com ([2607:f8b0:4864:20::532]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qZBmu-000nXp-SO for pgadmin-hackers@postgresql.org; Thu, 24 Aug 2023 14:58:28 +0000 Received: by mail-pg1-x532.google.com with SMTP id 41be03b00d2f7-56a3e6bce68so2791083a12.1 for ; Thu, 24 Aug 2023 07:58:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1692889099; x=1693493899; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=qB0AkRozXFc4Y2EBbqW/mJQnjddQylF0DshuD+ezork=; b=VMwnbTJl+0O93Qr23EFDSdyV+CTprenLTHwrM7LegdIdDelHeSKa/ByR/0bebHgpQS 6Kwqe2lw6VmlVg4zuEZpaXOw1sn7YqfY7l7vJ9liFIhf3GgLlohVC5BtzIZG7XEQNXPw 5Cledt2NyJSwTxHIpi6hCu+cl89RfTl9S/xgNPw86n31euzC9PwXcWRqe4Xz5PSm1OAY kAajpyskXtYijmJy41cJv2CzM7V7Qhczl31TNiZnDh5DmEPO0XTEamD7NHGUjvPBfwsg aGVN29cEv6GuyPpxpKcH0F0I9WSKrFhM8rgo1I3D8AJ9TyLBJ7xr76DAUgxWmkOJKoNe laUA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692889099; x=1693493899; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=qB0AkRozXFc4Y2EBbqW/mJQnjddQylF0DshuD+ezork=; b=WgIdESqutOtXVj2Dc+dTq7egoWJeyOnaXC+d3VWNLcyQml6CMOkN1CvlkzI3lPeEja geR3EenCSyjZeImlbCN+qDZ/aJGwewYCD3cGxrHADTDubUzWQSE9dcfqTCQ5yu6e/GlI zpgyNayohrgfV/9Rqc0XgGyWriUfDRjJe3VlD1ex1/t0sNlnN3lt/qa32EjLj6TuDcge cIE4DOExHMBVrvgsQO7pNxDy4I/nlqPRhozdkmVexLQ04GL8H0WWqe8qvNsdSVQd0TbE 5jpIwmP45JMwjAFt0rNW1De/oYqw4dCEMu3nEjnexnbdi16otkCSWRPr2RRwod61ZR0p /jnw== X-Gm-Message-State: AOJu0Yx5FYIju8zb6+2FeBYm1sKw4xmoBYHELWfIw9+bE1e4hW7VBJRG mayKTLP9JnqpdyhgiHLJlBa/z7ONge0DDt/Dw4k= X-Google-Smtp-Source: AGHT+IG+474U95J4S+C8quipODjs5r9WJX5h8tZGr5DdwQ//UQoD3Q71MqAQ0SRiajyFiWyBwjXbC3/LvyfhnUK5FjM= X-Received: by 2002:a17:90b:3884:b0:268:3b8b:140d with SMTP id mu4-20020a17090b388400b002683b8b140dmr11156432pjb.35.1692889098584; Thu, 24 Aug 2023 07:58:18 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Sahil Harpal Date: Thu, 24 Aug 2023 20:27:50 +0530 Message-ID: Subject: Re: Pgadmin4 System Stats Extension Design To: Khushboo Vashi , Aditya Toshniwal Cc: pgadmin-hackers@postgresql.org Content-Type: multipart/alternative; boundary="0000000000005d88240603ac75e5" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000005d88240603ac75e5 Content-Type: text/plain; charset="UTF-8" On Sat, 19 Aug 2023 at 16:20, Sahil Harpal wrote: > On Thu, 17 Aug 2023 at 17:57, Khushboo Vashi < > khushboo.vashi@enterprisedb.com> wrote: > >> >> - Sometimes graphs start from left and then shift to right. This >> issue I have reported in my initial review too. >> >> For StreamingChart should I ignore it for now? > On Mon, 7 Aug 2023 at 17:12, Aditya Toshniwal < > aditya.toshniwal@enterprisedb.com> wrote: > >> OK I thought you wanted the graph to go from left to right. Yeah, I >> have seen that glitch a few times (but rare). I think you can ignore it for >> now, we can look into it once we get time. It is not a priority. >> > > Or try the solution below? > On Sun, 6 Aug 2023 at 13:21, Sahil Harpal > wrote: > >> I've tried one more approach here. If our data array is full, this graph >> shifting won't happen. So, if we initialize our data list with null values, >> there won't be any visible shift. What do you think about this solution? >> > Can you please help me with this? --0000000000005d88240603ac75e5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Sat, 19 Aug 2023 at 16:20, Sahil Harpa= l <sahilharpal1234@gmail.co= m> wrote:
3D""
On Thu, 17 Aug 2023 at 17:57, Khushboo Vashi <khushboo.vas= hi@enterprisedb.com> wrote:
  • Som= etimes graphs start from left and then shift to right. This issue I have re= ported in my initial review too.
For StreamingChart should I ignore i= t for now?=C2=A0
= On Mon, 7 Aug 2023 at 17:12, Aditya Toshniwal <aditya.toshniwal@enterprisedb= .com> wrote:
=
OK I thought you wanted the gr= aph to go from left to right.=C2=A0=C2=A0Yeah, I have seen that glitch a= few times (but rare). I think you can ignore it for now, we can look into = it once we get time. It is not a priority.

Or try the solution below?=C2=A0
On Sun, 6 Aug 2023 at 13:21, Sahil Harpal <sahilharpal1234@gmail.com> wro= te:
I've tried one more approach here. If = our data array is full, this graph shifting won't happen. So, if we ini= tialize our data list with null values, there won't be any visible shif= t. What do you think about this solution?
Can you please help me with this?
--0000000000005d88240603ac75e5--