[cle-release-team] [samigo-team] 500 Error blocker for 2.9?

[Andrea Schmidt]

Hi Karen,

I would be happy to verify the fix in 2.9 after it is merged.

Andrea

On Tue, Oct 16, 2012 at 1:57 PM, Karen Tsao <ktsao at stanford.edu> wrote:

> Hi Andrea,
>
> The 500 error is not related to SAM-1591. It is caused by SAM-1368<https://jira.sakaiproject.org/browse/SAM-1368>which is a 2.10 new feature and only
> happens in trunk. If all tests are fine other then the 500 error, I will go
> ahead merge the fix to 2.9 and maybe you can verify in 2.9 where is no 500
> error.
>
> Thanks,
> Karen
>
>
> On Tue, Oct 16, 2012 at 10:24 AM, Andrea Schmidt <agschmid at umail.iu.edu>wrote:
>
>> Hi Karen,
>>
>> Yes, it is the 500 error if using the URL and the assessment allows late
>> submissions, whether timed or untimed, so I cannot verify how late
>> submissions would work under those circumstances. These assessments were
>> not released to anonymous users.
>>
>> Assessments with due dates and late not allowed, when using a URL worked
>> as they should, not allowing the student to even begin the assessment if
>> the due date had passed.
>>
>> Andrea
>>
>> I updated https://jira.sakaiproject.org/browse/SAM-1829 to include this
>> information.
>>
>>
>> On Tue, Oct 16, 2012 at 1:17 PM, Karen Tsao <ktsao at stanford.edu> wrote:
>>
>>> Hi Andrea,
>>>
>>> Thanks for verifying SAM-1835 and SAM-1591. But you said "SAM-1591 is
>>> still failing under certain conditions", do you mean the 500 error? If not,
>>> please let me know what goes wrong so I can take a look.
>>>
>>> Karen
>>>
>>>
>>> On Tue, Oct 16, 2012 at 9:27 AM, Andrea Schmidt <agschmid at umail.iu.edu>wrote:
>>>
>>>> Karen stated in https://jira.sakaiproject.org/browse/SAM-1835 that she
>>>> applied a fix and wanted me to test this one and
>>>> https://jira.sakaiproject.org/browse/SAM-1591. I assume the fixes were
>>>> to be tested on trunk, where SAM-1591 is still failing under certain
>>>> conditions.
>>>>
>>> 500 error if using the URL and the assessment allows late submissions,
>>>> whether timed or untimed. I tested several scenarios this morning:
>>>>
>>>> SAM-1591A - timed, late not allowed
>>>>
>>>> http://nightly2.sakaiproject.org:8082/samigo-app/servlet/Login?id=ad0f919a-08db-482f-9b37-4c2fefd293421350397744915
>>>> Late Submission not allowed message
>>>>
>>>> SAM-1591B - untimed, late not allowed
>>>>
>>>> http://nightly2.sakaiproject.org:8082/samigo-app/servlet/Login?id=ad0f919a-08db-482f-9b37-4c2fefd293421350397797805
>>>> Late Submission not allowed message
>>>>
>>>> SAM-1591C - untimed, late allowed
>>>>
>>>> http://nightly2.sakaiproject.org:8082/samigo-app/servlet/Login?id=ad0f919a-08db-482f-9b37-4c2fefd293421350397843366
>>>> Clicked Begin button - 500 error
>>>>
>>>> http://nightly2.sakaiproject.org:8082/portal
>>>> 114381 (Kernel 1.4.0-SNAPSHOT)- Server sakai-nightly.uits.iupui.edu
>>>>
>>>> Andrea Schmidt
>>>>
>>>>
>>>> On Tue, Oct 16, 2012 at 11:57 AM, Matthew Jones <matthew at longsight.com>wrote:
>>>>
>>>>> Actually that probably wouldn't work, we'd have to have all of the 2.9
>>>>> versions rather than just excluding the 2.10 right? :( Too bad they don't
>>>>> support version ranges yet.
>>>>>
>>>>>
>>>>> On Tue, Oct 16, 2012 at 11:56 AM, Matthew Jones <matthew at longsight.com
>>>>> > wrote:
>>>>>
>>>>>> Comments still indicate it was a regression from
>>>>>>
>>>>>> https://jira.sakaiproject.org/browse/SAM-1368
>>>>>>
>>>>>> Which isn't merged into 2.9, so nothing to worry about! We could
>>>>>> possibly improve the filter to have it say like "and Affects version !=
>>>>>> 2.10" to make something like a 2.9 unresolved issues filter.
>>>>>>
>>>>>>
>>>>>> On Tue, Oct 16, 2012 at 11:54 AM, Neal Caidin <
>>>>>> nealcaidin at sakaifoundation.org> wrote:
>>>>>>
>>>>>>> Sorry, I realize that I asked about this one before. But I think at
>>>>>>> the time it seemed like a 2.10 issue, but now may be a 2.9.0 issue?
>>>>>>>
>>>>>>> Confused. :-p
>>>>>>>
>>>>>>> -- Neal
>>>>>>>
>>>>>>>
>>>>>>> On Oct 16, 2012, at 11:52 AM, Neal Caidin <
>>>>>>> nealcaidin at sakaifoundation.org> wrote:
>>>>>>>
>>>>>>> > Hi ,
>>>>>>> >
>>>>>>> > It looks like there is a blocker for 2.9.0 -
>>>>>>> >
>>>>>>> > https://jira.sakaiproject.org/browse/SAM-1829
>>>>>>> >
>>>>>>> > but that a patch may be available for it already?
>>>>>>> >
>>>>>>> > Not sure if there is still time to get this fixed for RC 02 ?
>>>>>>> >
>>>>>>> > Thanks,
>>>>>>> > Neal
>>>>>>> >
>>>>>>> > ---------------------
>>>>>>> >
>>>>>>> > Neal Caidin
>>>>>>> >
>>>>>>> > Sakai CLE Community Coordinator
>>>>>>> > nealcaidin at sakaifoundation.org
>>>>>>> > Skype: nealkdin
>>>>>>> > AIM: ncaidin at aol.com
>>>>>>> >
>>>>>>> >
>>>>>>> >
>>>>>>> >
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> cle-release-team mailing list
>>>>>>> cle-release-team at collab.sakaiproject.org
>>>>>>> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> samigo-team mailing list
>>>>> samigo-team at collab.sakaiproject.org
>>>>> http://collab.sakaiproject.org/mailman/listinfo/samigo-team
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> samigo-team mailing list
>>>> samigo-team at collab.sakaiproject.org
>>>> http://collab.sakaiproject.org/mailman/listinfo/samigo-team
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20121016/c45d27c0/attachment-0006.html