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 1qXJXA-005xTh-2G for pgadmin-hackers@arkaria.postgresql.org; Sat, 19 Aug 2023 10:50:20 +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 1qXJX7-00GfiY-Bj for pgadmin-hackers@arkaria.postgresql.org; Sat, 19 Aug 2023 10:50:17 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qXJX7-00GfiP-1U for pgadmin-hackers@lists.postgresql.org; Sat, 19 Aug 2023 10:50:17 +0000 Received: from mail-oi1-x22b.google.com ([2607:f8b0:4864:20::22b]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qXJX2-000y0x-ND for pgadmin-hackers@postgresql.org; Sat, 19 Aug 2023 10:50:15 +0000 Received: by mail-oi1-x22b.google.com with SMTP id 5614622812f47-3a82db15081so1121907b6e.0 for ; Sat, 19 Aug 2023 03:50:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1692442212; x=1693047012; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=4gFMAUkun3Ix+vM75ht3V10woiAHPbkb/GKExJZN2RI=; b=FB+oLfy56GGvFqbFbvwJDe4zhRaqQRQoseu4/HYCx0ax20ts0RG3uEMRISyohBF/vf tPwg8r6vwR1yx1GiO0/YPlB6x6kCcJ7R4QNVOwarLMdVXlRGPuduPI9ME72FeiIpYZqc u43f/iCACVo8jEM4px80WQdGzP/LkpM53OaT1ckUnAXuvYHlKiaTYadmt3bGy8QaWVYt 3lrmSULhziKPe9PDh6c8AbSmtweoFww1JEr95CYrhRi/TCRq6QkQdhhebIVwEcbJD5RG ooAI1fYg8xbu78DnPROC3zQT1dwLwBUQHC5Xwtoif8cwahlk8O5aauKBRqi9lJ+1iofj Adag== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692442212; x=1693047012; 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=4gFMAUkun3Ix+vM75ht3V10woiAHPbkb/GKExJZN2RI=; b=fIfiQVOwATLpb61NpsbegHUAAnQb/zFGXNqqgb2qi5rgpeYOGxouyu3tCdzHTFbg2g GGaFFWi+cbuEGrt0oQSRJLI+VitudqQQFWTJZiDcawLpYLJfGoLYogfIL1vbI4mWaaDp ZpQ2fwJtP/8p9up19hBurkF1Ai4iosa1Hgl9P+SEk3/kLEpsIQHHIlWlvC1jhOvmH9lD /eAvYdM23h4wIOdI4AWqq5nMKQCepk0xExicQj9TvnrB47a1+mKjHWHMksqHSGafzc38 EHXBYf5YLX2Uj6Dmw0UAZONhKMx4CQPzzObvATMUQiscGqsVWEHppUStWNLcCyKYFmIi Zq0g== X-Gm-Message-State: AOJu0YxSanU3FymlPWbt/OJ83Hhpb/R2ScjzvuPtpmVp4XuFLu2r2o/N FkrUt4OYlX4lQywnxQ89tMt6xSzAP6ibb3dQnok= X-Google-Smtp-Source: AGHT+IEXrY398cQDSnY8IA4RxxnleGRkBCbr1BC1+h7vNSMU3eR+OD98yt+1cIXR52q1lTlH+ONalIqgW3KQLhrJ4Us= X-Received: by 2002:a05:6808:1904:b0:3a7:6385:28ac with SMTP id bf4-20020a056808190400b003a7638528acmr2418007oib.4.1692442211763; Sat, 19 Aug 2023 03:50:11 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Sahil Harpal Date: Sat, 19 Aug 2023 16:20:01 +0530 Message-ID: Subject: Re: Pgadmin4 System Stats Extension Design To: Khushboo Vashi Cc: pgadmin-hackers@postgresql.org, Aditya Toshniwal Content-Type: multipart/alternative; boundary="000000000000d5cb780603446820" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000d5cb780603446820 Content-Type: text/plain; charset="UTF-8" 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? > Thank you, Sahil --000000000000d5cb780603446820 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, 17 Aug 2023 at 17:57, Khushboo Va= shi <khushboo.vashi@e= nterprisedb.com> wrote:
3D""
=
  • Sometimes graphs start from left and then shi= ft to right. This issue I have reported in my initial review too.
    • <= /ul>
For= StreamingChart should I ignore it for now?=C2=A0
On Mon, 7 Aug 2023 at 17:12, Aditya Toshni= wal <aditya.toshniw= al@enterprisedb.com> wrote:
OK I thought yo= u wanted the graph to go from left to right.=C2=A0=C2=A0Yeah, I have se= en that glitch a few times (but rare). I think you can ignore it for now, w= e 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?

Thank you,
Sahil=C2=A0
--000000000000d5cb780603446820--