[Glass] Updating code from seaside gem

[Dale Henrichs via Glass]

On Tue, Oct 21, 2014 at 1:08 PM, Mariano Martinez Peck <
marianopeck at gmail.com> wrote:

> Hi Dale,
>
> I found I could reproduce it even easier... I am trying to built a fresh
> extent...but everything I try fails...
>

Not needed for this, but I am curious what you are trying and what is
failing...


> maybe, if you can easily get a fresh extent + stone, then try:
>

What version of Seaside do you have loaded when you start? Perhaps just
send me the result of:

 Gofer new
  package: 'GsUpgrader-Core';
  url: 'http://ss3.gemtalksystems.com/ss/gsUpgrader';
  load.
(Smalltalk at: #GsUpgrader) metacelloReport.

Than I'll take things for a spin...


> 1)
>
> Gofer new
>   package: 'GsUpgrader-Core';
>   url: 'http://ss3.gemtalksystems.com/ss/gsUpgrader';
>   load.
> (Smalltalk at: #GsUpgrader) upgradeGrease.
>
>
> 2)  File in this class:
>
> BugLoadingCode class >> initialize
> (WAAdmin register: self asApplicationAt: 'bug')
>
> BugLoadingCode class >> canBeRoot
> ^ true
>
> BugLoadingCode class >> blockToLoad
> ^ [:iam |
>  Metacello new
>     baseline: 'Seaside3';
>     repository: 'github://GsDevKit/Seaside31:v3.1.3-gs/repository';
>     onLock: [:ex | ex honor];
>     load: #('Development' 'Examples' 'Zinc').
>  ]
>
> BugLoadingCode class >> renderContentOn: html
> html anchor
> callback: [ self blockToLoad value: nil ];
> with: 'Load'.
>
> 3) Evaluate "BugLoadingCode initialize" and fire a seaside adaptor
> 4) Go to /bug and click "load" link.
>
> I can reproduce it even in 3.1.0.4 and 3.1.0.6. In Unix and in OSX. With
> and without native code enabled.
>
> Let me know if you can reproduce it. Otherwise, I keep trying to get a
> working/fresh extent...
>
> Thanks!
>
>
>
>
>
>
> On Tue, Oct 21, 2014 at 4:00 PM, Dale Henrichs <
> dale.henrichs at gemtalksystems.com> wrote:
>
>>
>>
>> On Tue, Oct 21, 2014 at 11:51 AM, Mariano Martinez Peck <
>> marianopeck at gmail.com> wrote:
>>
>>>
>>> extent that exhibits the problem.
>>>
>>> Hi Dale,
>>>
>>> Stupid question...if I send the simple extent, are you able to run it
>>> just like that? No problem which OS user I was using, which gemtone
>>> username/pass I was using, etc?
>>>
>>
>> I probably would need some sort of credentials to allow me to log and run
>> the seaside gems edit code, etc. but I probably wouldn't need SystemUser
>> credentials ... I would need a way to reproduce the load issue without
>> having to have copies of your code repos ... from the look of things it
>> should break just trying to load a project with a block so Seaside31 with a
>> Grease lock might do the trick ... perhaps you could verify that the bug
>> reproduces before sending us the extent ...
>>
>>   I guess you can also use a swazoo adaptor to avoid nginx..
>>> would you need anything else besides the extent file and maybe tranlogs?
>>>
>>
>> The extent file should be all that we need ...
>>
>> Dale
>>
>
>
>
> --
> Mariano
> http://marianopeck.wordpress.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20141021/9cf2937a/attachment-0001.html>