Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dIxIG-0006oe-11 for pgadmin-hackers@arkaria.postgresql.org; Thu, 08 Jun 2017 13:16:08 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dIxIF-000166-6Y for pgadmin-hackers@arkaria.postgresql.org; Thu, 08 Jun 2017 13:16:07 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dIxI0-0000h8-Ty for pgadmin-hackers@postgresql.org; Thu, 08 Jun 2017 13:15:52 +0000 Received: from mail-it0-x235.google.com ([2607:f8b0:4001:c0b::235]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1dIxHt-0007hL-Ct for pgadmin-hackers@postgresql.org; Thu, 08 Jun 2017 13:15:52 +0000 Received: by mail-it0-x235.google.com with SMTP id m62so124159455itc.0 for ; Thu, 08 Jun 2017 06:15:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgadmin-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=XOfR+iKT4UDqY2nQXeV4m+JggQS/HCPI7bTSfib2sY4=; b=G4mQcfiz4LyD1syudIXhLXAUDCHoYZQ0U2+p48LXPRs14TlbFaIKj3tpBJ1loUxNr2 +wZRO0EP/0nHoOe60ftSxcqMuejJDQaSa+vLyyxIeXH71CYOGAXFOsa9RtsOM4rh5hRR Y5rbI7K2Yohqnt0tM//LCzAKKnZmK5ZwUEvUn+on99IUnb2XqzXTwjLitOXhHP2ekYNM bKi6SiWSKnGzc36f6+eQ7gQBB8BlPXjA2DG7JrXmIEVYARwd/5F12ffHolb96E/JkjF7 Av+h19WjGisgbLTE/DNt2CmNWsFxpq7aZAxc/qz8mDWczXhZbFBWqCrdXCIF+Fz63XQn D28A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=XOfR+iKT4UDqY2nQXeV4m+JggQS/HCPI7bTSfib2sY4=; b=Kczc5u9N9ecW1fe8O8eVG3rORUO115z5/uJOz4kRu1W543fTb8Va4+XthmMAvDMtU/ WoQyBVRBNicZjTP/L5UWZIN1PuBRc7gG2DIXh7BA0bE4J+jJm22nEB3BMeSzU2eg/OgS cT9i6WJ/PlSRdhKGymRBMEuVBJMgBDHhFGDfECiy/gUC2DebCx3FGeuPYBBwYCByqm78 5k3ivDA0SUj1Y7IFJepqq2+xv5FSpCkTLSfI+UD4YjcjlpeNt8kbwNGAv96NUR0i7ZW7 STPQldcDFyMoUyVCtKtlsJsL3c1Tj5+2TQZiYYGv8h80ZTjGnMFy6taTd5Yr4CUa2A8k lVtw== X-Gm-Message-State: AODbwcCplFeS5yyGJUOJ6QwF+QMjsdKm2MGbOXkgaf8qVs+K+Vu69zbz FShdgE42eBqJgEORope8otYL0AlxQDxQRdvoeA== X-Received: by 10.36.147.2 with SMTP id y2mr4962909itd.43.1496927742948; Thu, 08 Jun 2017 06:15:42 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.174.147 with HTTP; Thu, 8 Jun 2017 06:15:41 -0700 (PDT) In-Reply-To: References: From: Dave Page Date: Thu, 8 Jun 2017 14:15:41 +0100 Message-ID: Subject: Re: [pgAdmin4] [PATCH] History Tab rewrite in React To: George Gelashvili Cc: Sarah McAlear , Surinder Kumar , Matthew Kleiman , Joao Pedro De Almeida Pereira , Murtuza Zabuawala , pgadmin-hackers Content-Type: text/plain; charset="UTF-8" X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgadmin-hackers Precedence: bulk Sender: pgadmin-hackers-owner@postgresql.org Hi George On Wed, Jun 7, 2017 at 10:21 PM, George Gelashvili wrote: > Hi Dave, > > I split the linting out into an intermediate commit, and rebased on top of > master. Unfortunately, it still doesn't apply: error: patch failed: web/regression/javascript/test-main.js:1 error: removal patch leaves file contents error: web/regression/javascript/test-main.js: patch does not apply Checking patch web/regression/requirements.txt... Checking patch web/webpack.config.js... Checking patch web/webpack.test.config.js... Checking patch web/yarn.lock... error: web/yarn.lock: already exists in working directory Applied patch .gitignore cleanly. Applied patch Make.bat cleanly. Applied patch README cleanly. Applied patch pkg/mac/build.sh cleanly. Applied patch pkg/pip/build.sh cleanly. Applied patch pkg/src/build.sh cleanly. Applied patch web/.eslintrc.js cleanly. Applied patch web/karma.conf.js cleanly. Applied patch web/package.json cleanly. Applied patch web/pgAdmin4.py cleanly. Applied patch web/pgadmin/static/jsx/components.jsx cleanly. Applied patch web/pgadmin/tools/javascript/__init__.py cleanly. Applied patch web/pgadmin/tools/javascript/javascript_bundler.py cleanly. Applied patch web/pgadmin/tools/javascript/tests/__init__.py cleanly. Applied patch web/pgadmin/tools/javascript/tests/test_javascript_bundler.py cleanly. Applied patch web/regression/README cleanly. Applied patch web/regression/javascript/jasmine_capture_warnings_beforeall.js cleanly. Applied patch web/regression/requirements.txt cleanly. Applied patch web/webpack.config.js cleanly. Applied patch web/webpack.test.config.js cleanly. The second (lint update) patch is even worse, with significant number change that just don't want to apply. Clearly yarn.lock needs to be removed from there repo. Once I can apply a version of this, how should I be running the linter and the unit tests? -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-hackers