[sakai-core-team] The weird behavior of Trunk (from last Sakai Core Team Call) - NOW SOLVED

[José Mariano Luján]

Mmmmm, interesting. Thanks for the investigation. Samigo was doing really weird things, i remember also some error in the UI (might be relates to your description) and then the navigation problems... So, both fixes were neded! 

Thanks Matt,
Cheers,
Mariano

Enviado desde mi iPhone

> El 04/03/2015, a las 15:38, Matthew Jones <matthew at longsight.com> escribió:
> 
> Ah great to hear,
> 
> I didn't know the problem was specific to Samigo but I spent some time this week investigating a stack trace on the nighly servers. It ended up coming back to
> https://jira.sakaiproject.org/browse/SAM-2111
> 
> Where this property"samigo.answerUploadRepositoryPath" was defined and set to a location that the server didn't have access to write to. I just commented out that property so it uses the default and it probably works better. What that does is set the temporary directory for the the internal UploadFilter for samigo, and every POST request (even saving a form) was going through there).
> 
> -Matthew
> 
> 
>> On Wed, Mar 4, 2015 at 9:19 AM, JOSE MARIANO LUJáN GONZáLEZ <jmariano at um.es> wrote:
>> Hi everyone!
>> 
>> Since I won't be able to attend tomorrow's meeting, I wanted to let you know that now things work well with Samigo in Trunk. Last week, I mentioned that during Testing, we were seeing some weird behavior in Samigo (when navigating through the tool). We now believe that it was probably related to SAM-2466 which was merged to trunk last night.
>> 
>> Today trunk is behaving as expected :) and we were able to verify some jiras.
>> 
>> -----
>> 
>> Here is what might have happened:
>> 
>> We were trying to verify some issues in the nightly severs (PRs already merged). Since Samigo was behaving weird (in nightly), we     went back to our S2U qa server and saw that Samigo was working fine in that one. Our S2U qa server was the same built as nightly but including some patches that were already issued for PR but not merged yet (one of them was SAM-2466).
>> 
>>     - https://sakai-trunk.atica.um.es (included SAM-2466 for testing and it was working as expected)
>>     - https://trunk-mysql.nightly.sakaiproject.org/portal/ (did not include SAM-2466 yet)
>> 
>> So, after SAM-2466 has been merged to master, Samigo is behaving well in both servers!
>> 
>> Thanks for you input in the call (Matt and Earl),
>> best regards,
>> Mariano
>>  -- 
>> ******************************************
>> José Mariano Luján González - Aula Virtual
>> Area de Tecnologías de la Información
>> y las Comunicaciones Aplicadas (ATICA)
>> UNIVERSIDAD DE MURCIA - http://www.um.es
>> 
>> _______________________________________________
>> sakai-core-team mailing list
>> sakai-core-team at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-core-team
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-core-team/attachments/20150304/4492092f/attachment.html