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 1r2syv-001Et5-J7 for pgsql-www@arkaria.postgresql.org; Tue, 14 Nov 2023 12:57:29 +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 1r2syu-007Qqy-7Z for pgsql-www@arkaria.postgresql.org; Tue, 14 Nov 2023 12:57:28 +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 1r2syu-007Qqn-0q for pgsql-www@lists.postgresql.org; Tue, 14 Nov 2023 12:57:28 +0000 Received: from mail-lf1-x142.google.com ([2a00:1450:4864:20::142]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1r2syr-006ODe-Ue for pgsql-www@lists.postgresql.org; Tue, 14 Nov 2023 12:57:27 +0000 Received: by mail-lf1-x142.google.com with SMTP id 2adb3069b0e04-507b9408c61so7641944e87.0 for ; Tue, 14 Nov 2023 04:57:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1699966645; x=1700571445; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=z3Zg9g27/GyhStDfH2nE0dKGg2xfKsvSw+dbfBGueOQ=; b=GOm+b+VtuKLzA0TCcwmbGODrdWgw6rwW1osNaEeEewEJ69b/66qjQq0llSGz0gF04Q 984ppRiOySQ99N1ydgoGfRwawdgh6NvTX4VXRRf8Ud0bvD53DWjsWUDqk9l0NCyT1ujN EbP1w8+Kiv12RjI78MRxzoLTFhgg+0j1XhwfmoQ8KXElzl7/lbFCiS3JgNrYqOwQ1nSF l9Fjm0fYZAPawRW4chXKWXvxAebZqT2cYARADG7a74HRhglr6pNlXNFMScXN7o9kITnG mT10gk1u89sXdIH5nrfkyPmamURdNNlarHJonxyg4TFf9jEGVBmPltPHSBTnvqxQoM/2 0bpA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699966645; x=1700571445; 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=z3Zg9g27/GyhStDfH2nE0dKGg2xfKsvSw+dbfBGueOQ=; b=BxPg6P0r7cg16cxm90PiTX2jlb9c5FelxB1BkN7tEgYZWK4IvVkSCK45Qo4LL7/SUz /ME3aSTKk4AWoBic7LIUmZoDUTDSS940wKlTLSoomkcP1iWysYAKPcTaJ5Cg/qC9scVk ytVX7zeYqAZ6LC6Ymk9mTg3VVnH8Z5WR1veiIv48hv5ZkdgfG9dvXbv7c9E7i9M6lJG4 UbjMrIB5GrdTuvg5um3W+KyJju2SxILmhjzQl77S6Mbm+UQ9k/sNz5u8lVLzO57Cc5Wr r8Rg8fRCYMAp8x1sDVc4nmTGht2a1JvIl0kuIGZPvyVsUVu1PzX4Ps+nAbSV7pCJfSN9 z+0w== X-Gm-Message-State: AOJu0YxYzUzGDEfEw0dCO11bbztp1kfA+9Hm6Ns8wry7Dw89sHxfLtn9 DuQbw6UURNktNlALqmNG46xnjbjqk03WocvNl49qAjnpOYJsGw== X-Google-Smtp-Source: AGHT+IEofM37BDAYXpYwCyZPCGuTFKO2MO5ojpNo3JYK0acMtn9mQh6aAdflVcxT5zgqKuhNOhoFckWhKclRegbJQoo= X-Received: by 2002:a19:3809:0:b0:50a:6375:d5f1 with SMTP id f9-20020a193809000000b0050a6375d5f1mr5888352lfa.60.1699966644440; Tue, 14 Nov 2023 04:57:24 -0800 (PST) MIME-Version: 1.0 References: <7F99AF5A-8D5D-47A3-B238-4E34004C3DFE@yesql.se> <433F3C16-B91E-45D1-8C5A-E1AAEAA2541C@yesql.se> In-Reply-To: From: Akshat Jaimini Date: Tue, 14 Nov 2023 18:27:12 +0530 Message-ID: Subject: Re: Permission to allow testing harness to send error reports for pgweb directly to mailing list. To: Daniel Gustafsson Cc: pgsql-www@lists.postgresql.org, Magnus Hagander Content-Type: multipart/alternative; boundary="000000000000f8d2f9060a1c53ef" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000f8d2f9060a1c53ef Content-Type: text/plain; charset="UTF-8" Hey everyone, Sorry for the delay(got stuck in some uni stuff). I am working on this right now, so currently I am planning to use Supabase to store the failure report content instead of storing entire files. This will also give us a way to prevent the harness from reporting any repeating errors in subsequent builds and make it easier to display the data on the website for the harness(which can then be hosted easily on Cloudflare pages or whatever is preferred by the community). Does this seem to be in the right direction or should we opt for some other solution? Regards, Akshat Jaimini --000000000000f8d2f9060a1c53ef Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hey everyone,
Sorry for the delay(got stuck= in some uni stuff). I am working on this right now, so currently I am plan= ning to use Supabase to store the failure report content instead of storing= entire files. This will also give us a way to prevent the harness from rep= orting any repeating errors in subsequent builds and make it easier to disp= lay the data on the website for the harness(which can then be hosted easily= on Cloudflare pages or whatever is preferred by the community). Does this = seem to be in the right direction or should we opt for some other solution?=

Regards,
Akshat Jaimini
--000000000000f8d2f9060a1c53ef--