Re: Incorrect email address in the auth.py module

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: PostgreSQL WWW <pgsql-www(at)lists(dot)postgresql(dot)org>
Subject: Re: Incorrect email address in the auth.py module
Date: 2019-03-27 15:50:05
Message-ID: zZs-Ir-mezjBf_tvR4hOaHXDvpOlWa652ocaIKmY9E2E5t06xAZ0_iNgW_qFQe-XHHnY4bF2X4T3deFJmZCm1QJ7_VXA3gAhsfgQEsH0-zI=@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

On Wednesday, March 27, 2019 3:51 PM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:

> On Wed, Mar 27, 2019 at 2:12 PM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
>
>> Poking around in the CF app I noticed that the auth.py module for integrating with
>> the community authentication was out of sync with the copy in the main pgweb repo.
>> Turns out the copy in the CF app is the most up to date as it has fixed the email
>> address in the account merging support email template. The attached patch merges
>> the changes from the CF app copy into the one in the pgweb repo. Unless there are
>> objections I plan to apply this soon.
>>
>> This also fixes an adjacent typo spotted in the process.
>
> That update breaks the commit hook. Have you perhaps forgotten to instlall it? :)

Aha, nice catch. This repo does indeed not run any commit hooks, will fix.

> Please make sure that a "pep8" run (with version 2.2.0 or compatible, as that's what's used on the prod servers) passes on the code before pushing! Easiest way is to make sure that the tools/githook/pre-commit is linked into your git hooks directory.

Gotcha, thanks. Any objections to the patch when the above mentioned breakage is resolved?

cheers ./daniel

In response to

Responses

Browse pgsql-www by date

  From Date Subject
Next Message Magnus Hagander 2019-03-28 10:27:06 Re: Incorrect email address in the auth.py module
Previous Message Magnus Hagander 2019-03-27 14:57:50 Re: Redundant role attribute on the CF app