Not a Whimsy bug.
The workbench get the list of potential members from the
memapp-received.txt file in the meetings directory.
Not sure who or what is suppose to pre-populate that, but at present
it is an empty template.
Sebb
On Fri, 10 Mar 2023 at 01:04, sebb wrote:
>
> Just noticed that as we
Just noticed that as well. Will try to look into it tomorrow if no-one
else gets there first
On Fri, 10 Mar 2023 at 00:52, Craig Russell wrote:
>
> Membership application form is unusable. The field for Public Name cannot be
> filled and the form cannot be filed.
>
> Craig L Russell
> c...@apach
Hi Sebb,
Yes, it seems to work now.
Thanks,
Craig
> On Jan 17, 2023, at 16:33, sebb wrote:
>
> Hopefully now fixed.
>
> On Tue, 17 Jan 2023 at 22:27, Craig Russell wrote:
>>
>> Seems to be related to sending email to submitter, although it is hard to
>> tell what failed. The icla was appar
Hopefully now fixed.
On Tue, 17 Jan 2023 at 22:27, Craig Russell wrote:
>
> Seems to be related to sending email to submitter, although it is hard to
> tell what failed. The icla was apparently correctly filed but no email was
> sent.
>
> > On Jan 17, 2023, at 14:24, Craig Russell wrote:
> >
>
Seems to be related to sending email to submitter, although it is hard to tell
what failed. The icla was apparently correctly filed but no email was sent.
> On Jan 17, 2023, at 14:24, Craig Russell wrote:
>
> Happens every time after successful filing of an ICLA...
>
> #
> /var/lib/gems/2.7.0
On 6 November 2017 at 19:29, Sam Ruby wrote:
> On Mon, Nov 6, 2017 at 12:49 PM, sebb wrote:
>> On 4 November 2017 at 12:42, Sam Ruby wrote:
>>> On Sat, Nov 4, 2017 at 6:54 AM, sebb wrote:
On 3 November 2017 at 15:47, Sam Ruby wrote:
> On Fri, Nov 3, 2017 at 11:37 AM, Craig Russell
>
On Mon, Nov 6, 2017 at 12:49 PM, sebb wrote:
> On 4 November 2017 at 12:42, Sam Ruby wrote:
>> On Sat, Nov 4, 2017 at 6:54 AM, sebb wrote:
>>> On 3 November 2017 at 15:47, Sam Ruby wrote:
On Fri, Nov 3, 2017 at 11:37 AM, Craig Russell
wrote:
> I cannot reproduce this error on my
On 4 November 2017 at 12:42, Sam Ruby wrote:
> On Sat, Nov 4, 2017 at 6:54 AM, sebb wrote:
>> On 3 November 2017 at 15:47, Sam Ruby wrote:
>>> On Fri, Nov 3, 2017 at 11:37 AM, Craig Russell wrote:
I cannot reproduce this error on my local machine running Chrome or Safari.
With th
On Sun, Nov 5, 2017 at 1:11 PM, Craig Russell wrote:
>
>> On Nov 4, 2017, at 5:42 AM, Sam Ruby wrote:
>>
>> On Sat, Nov 4, 2017 at 6:54 AM, sebb wrote:
>>> On 3 November 2017 at 15:47, Sam Ruby wrote:
On Fri, Nov 3, 2017 at 11:37 AM, Craig Russell
wrote:
> I cannot reproduce thi
> On Nov 4, 2017, at 5:42 AM, Sam Ruby wrote:
>
> On Sat, Nov 4, 2017 at 6:54 AM, sebb wrote:
>> On 3 November 2017 at 15:47, Sam Ruby wrote:
>>> On Fri, Nov 3, 2017 at 11:37 AM, Craig Russell wrote:
I cannot reproduce this error on my local machine running Chrome or Safari.
W
On Sat, Nov 4, 2017 at 6:54 AM, sebb wrote:
> On 3 November 2017 at 15:47, Sam Ruby wrote:
>> On Fri, Nov 3, 2017 at 11:37 AM, Craig Russell wrote:
>>> I cannot reproduce this error on my local machine running Chrome or Safari.
>>>
>>> With the production code, the problem shows up if the Full n
On 3 November 2017 at 15:47, Sam Ruby wrote:
> On Fri, Nov 3, 2017 at 11:37 AM, Craig Russell wrote:
>> I cannot reproduce this error on my local machine running Chrome or Safari.
>>
>> With the production code, the problem shows up if the Full name has the
>> non-ascii character.
>>
>> So I can
On Fri, Nov 3, 2017 at 11:37 AM, Craig Russell wrote:
> I cannot reproduce this error on my local machine running Chrome or Safari.
>
> With the production code, the problem shows up if the Full name has the
> non-ascii character.
>
> So I can't test to see if substituting \r\n for \n helps. :(
I cannot reproduce this error on my local machine running Chrome or Safari.
With the production code, the problem shows up if the Full name has the
non-ascii character.
So I can't test to see if substituting \r\n for \n helps. :(
Craig
> On Nov 3, 2017, at 7:50 AM, Craig Russell wrote:
>
>>
> On Nov 2, 2017, at 10:35 PM, Sam Ruby wrote:
>
> On Thu, Nov 2, 2017 at 11:34 PM, Craig Russell wrote:
>>
>>> On Nov 2, 2017, at 4:24 PM, Sam Ruby wrote:
>>>
>>> On Thu, Nov 2, 2017 at 6:58 PM, Craig Russell wrote:
The error appears to be here:
# untaint to email address
On Thu, Nov 2, 2017 at 11:34 PM, Craig Russell wrote:
>
>> On Nov 2, 2017, at 4:24 PM, Sam Ruby wrote:
>>
>> On Thu, Nov 2, 2017 at 6:58 PM, Craig Russell wrote:
>>> The error appears to be here:
>>>
>>># untaint to email addresses
>>>mail.to = mail.to.map {|email| email.dup.untaint} <==
> On Nov 2, 2017, at 4:24 PM, Sam Ruby wrote:
>
> On Thu, Nov 2, 2017 at 6:58 PM, Craig Russell wrote:
>> The error appears to be here:
>>
>># untaint to email addresses
>>mail.to = mail.to.map {|email| email.dup.untaint} <== here
>>
>> But the mail.to should be r...@apache.org
>
> m
On Thu, Nov 2, 2017 at 6:58 PM, Craig Russell wrote:
> The error appears to be here:
>
> # untaint to email addresses
> mail.to = mail.to.map {|email| email.dup.untaint} <== here
>
> But the mail.to should be r...@apache.org
mail.to is normally an array of values. In this case, it is a s
The error appears to be here:
# untaint to email addresses
mail.to = mail.to.map {|email| email.dup.untaint} <== here
But the mail.to should be r...@apache.org
Why does this need to be untainted? Why does it fail just on this email? The
only thing different about this email is the non-a
Hi Sam,
> On Nov 2, 2017, at 12:08 PM, Sam Ruby wrote:
>
> Reproduction instructions?
Try to file the icla from Nandor Kollar.
Thanks!
Craig
>
> - Sam Ruby
>
> On Thu, Nov 2, 2017 at 11:27 AM, Craig Russell wrote:
>> # Did
>> you mean? tap>
>> /x1/srv/whimsy/www/secretary/workbench/views/
Reproduction instructions?
- Sam Ruby
On Thu, Nov 2, 2017 at 11:27 AM, Craig Russell wrote:
> # Did
> you mean? tap>
> /x1/srv/whimsy/www/secretary/workbench/views/actions/icla.json.rb:232:in
> `block in _evaluate'
> /x1/srv/whimsy/www/secretary/workbench/tasks.rb:9:in `task'
> /x1/srv/whimsy/
21 matches
Mail list logo
