SafelyPerformBlockRequiringAbort error when running Seaside

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

SafelyPerformBlockRequiringAbort error when running Seaside

GLASS mailing list
Hi,

A fresh GS 3.5.1 installation and installing Seaside with:
Gofer new
  package: 'GsUpgrader-Core';
  url: 'http://ss3.gemtalksystems.com/ss/gsUpgrader';
  load.
(Smalltalk at: #GsUpgrader) upgradeGrease.
GsDeployer deploy: [
  Metacello new
    baseline: 'Seaside3';
    repository: 'github://GsDevKit/Seaside31:gs_master/repository';
    onLock: [:ex | ex honor];
    load: 'CI' ].

When running Seaside with:
 | handler commitThreshold |
   commitThreshold := 65.
   handler := AlmostOutOfMemory addDefaultHandler: [ :ex | self halt ].
   SessionTemps current at: #'AlmostOutOfMemoryStaticException' put:
handler.
   System signalAlmostOutOfMemoryThreshold: commitThreshold.
[WAGsZincAdaptor startOn: 8787]
  on: AlmostOutOfMemory enable
  do: [:ex | ex error: ex description].

The Seaside server at http://192.168.178.130:8787/ answer the following
exception:
Internal server malfunction
a MessageNotUnderstood occurred (error 2010), a
SafelyPerformBlockRequiringAbort class does not understand #'do:'
You should contact the system administrator

Still researching on this error. Any comment is welcome ...

regards,
bruno



--
Sent from: http://forum.world.st/GLASS-f1460844.html
_______________________________________________
Glass mailing list
[hidden email]
https://lists.gemtalksystems.com/mailman/listinfo/glass
Reply | Threaded
Open this post in threaded view
|

Re: SafelyPerformBlockRequiringAbort error when running Seaside

GLASS mailing list
A stack would be useful if you need help.

Dale

On 2/19/20 1:20 PM, BrunoBB via Glass wrote:

> Hi,
>
> A fresh GS 3.5.1 installation and installing Seaside with:
> Gofer new
>    package: 'GsUpgrader-Core';
>    url: 'http://ss3.gemtalksystems.com/ss/gsUpgrader';
>    load.
> (Smalltalk at: #GsUpgrader) upgradeGrease.
> GsDeployer deploy: [
>    Metacello new
>      baseline: 'Seaside3';
>      repository: 'github://GsDevKit/Seaside31:gs_master/repository';
>      onLock: [:ex | ex honor];
>      load: 'CI' ].
>
> When running Seaside with:
>   | handler commitThreshold |
>     commitThreshold := 65.
>     handler := AlmostOutOfMemory addDefaultHandler: [ :ex | self halt ].
>     SessionTemps current at: #'AlmostOutOfMemoryStaticException' put:
> handler.
>     System signalAlmostOutOfMemoryThreshold: commitThreshold.
> [WAGsZincAdaptor startOn: 8787]
>    on: AlmostOutOfMemory enable
>    do: [:ex | ex error: ex description].
>
> The Seaside server at http://192.168.178.130:8787/ answer the following
> exception:
> Internal server malfunction
> a MessageNotUnderstood occurred (error 2010), a
> SafelyPerformBlockRequiringAbort class does not understand #'do:'
> You should contact the system administrator
>
> Still researching on this error. Any comment is welcome ...
>
> regards,
> bruno
>
>
>
> --
> Sent from: http://forum.world.st/GLASS-f1460844.html
> _______________________________________________
> Glass mailing list
> [hidden email]
> https://lists.gemtalksystems.com/mailman/listinfo/glass
_______________________________________________
Glass mailing list
[hidden email]
https://lists.gemtalksystems.com/mailman/listinfo/glass
Reply | Threaded
Open this post in threaded view
|

Re: SafelyPerformBlockRequiringAbort error when running Seaside

GLASS mailing list
Dale,

Sorry about that here is the stack:
----------- Internal Zinc ERROR Encountered:
2020-02-19T13:30:22.46508693695068-08:00
a MessageNotUnderstood occurred (error 2010), a
SafelyPerformBlockRequiringAbort class does not understand  #'do:'
1 GRGemStonePlatform >> logError:title:shouldCommit: @2 line 4  [GsNMethod
148908289]
2 GRGemStonePlatform >> logError:title: @2 line 3  [GsNMethod 148908033]
3 WAGsZincAdaptor >> internalServerErrorMessage: @16 line 14  [GsNMethod
277678593]
4 [] in GRGemStonePlatform >> seasideProcessRequest:adaptor:resultBlock: @31
line 15  [GsNMethod 225123329]
5 MessageNotUnderstood (AbstractException) >> _executeHandler: @7 line 11
[GsNMethod 6147073]
6 MessageNotUnderstood (AbstractException) >> _signalWith: @1 line 2
[GsNMethod 6154241]
7 MessageNotUnderstood (AbstractException) >> signal @2 line 47  [GsNMethod
6154753]
8 SafelyPerformBlockRequiringAbort class (Object) >> doesNotUnderstand: @9
line 10  [GsNMethod 5646849]
9 SafelyPerformBlockRequiringAbort class (Object) >>
_doesNotUnderstand:args:envId:reason: @8 line 14  [GsNMethod 5656321]
10 SafelyPerformBlockRequiringAbort class (Object) >> accompaniedBy:do: @2
line 6  [GsNMethod 5569025]
11 Set (Collection) >> addAll: @7 line 7  [GsNMethod 2940417]
12 Set (UnorderedCollection) >> , @4 line 5  [GsNMethod 53810177]
13 [] in GRGemStonePlatform >> seasideProcessRequestWithRetry:resultBlock:
@15 line 13  [GsNMethod 225124865]
14 ExecBlock0 (ExecBlock) >> ensure: @2 line 12  [GsNMethod 5890817]
15 TransientRecursionLock >> critical: @11 line 12  [GsNMethod 13794305]
16 GRGemStonePlatform >> seasideProcessRequestWithRetry:resultBlock: @3 line
6  [GsNMethod 221593089]
17 [] in GRGemStonePlatform >> seasideProcessRequest:adaptor:resultBlock:
@17 line 6  [GsNMethod 236484353]
18 Array (Collection) >> do: @5 line 10  [GsNMethod 2944257]
19 [] in GRGemStonePlatform >> seasideProcessRequest:adaptor:resultBlock: @7
line 5  [GsNMethod 225123585]
20 ExecBlock0 (ExecBlock) >> on:do: @3 line 44  [GsNMethod 5883905]
21 GRGemStonePlatform >> seasideProcessRequest:adaptor:resultBlock: @2 line
12  [GsNMethod 221591041]
22 WAGsZincAdaptor >> process: @3 line 4  [GsNMethod 277678849]
23 ZnSeasideServerAdaptorDelegate >> handleRequest: @3 line 4  [GsNMethod
277697281]
24 [] in ZnSingleThreadedServer >> authenticateAndDelegateRequest: @11 line
12  [GsNMethod 190152449]
25 ZnManagingMultiThreadedServer (ZnSingleThreadedServer) >>
authenticateRequest:do: @4 line 6  [GsNMethod 176040961]
26 ZnManagingMultiThreadedServer (ZnSingleThreadedServer) >>
authenticateAndDelegateRequest: @2 line 8  [GsNMethod 176047105]
27 [] in ZnSingleThreadedServer >> handleRequestProtected: @6 line 5
[GsNMethod 190153217]
28 ExecBlock0 (ExecBlock) >> on:do: @3 line 44  [GsNMethod 5883905]
29 ZnManagingMultiThreadedServer (ZnSingleThreadedServer) >>
handleRequestProtected: @2 line 6  [GsNMethod 176047361]
30 ZnManagingMultiThreadedServer (ZnSingleThreadedServer) >> handleRequest:
@5 line 9  [GsNMethod 176046081]
31 [] in ZnMultiThreadedServer >> executeOneRequestResponseOn: @13 line 11
[GsNMethod 190445569]
32 ExecBlock0 (ExecBlock) >> on:do: @3 line 44  [GsNMethod 5883905]
33 ZnManagingMultiThreadedServer (ZnMultiThreadedServer) >>
executeOneRequestResponseOn: @6 line 15  [GsNMethod 176476673]
34 [] in ZnMultiThreadedServer >> executeRequestResponseLoopOn: @14 line 10
[GsNMethod 197617921]
35 [] in DynamicVariable class >> value:during: @15 line 9  [GsNMethod
91607297]
36 ExecBlock0 (ExecBlock) >> ensure: @2 line 12  [GsNMethod 5890817]
37 ZnCurrentServer class (DynamicVariable class) >> value:during: @6 line 10
[GsNMethod 75520257]
38 [] in ZnMultiThreadedServer >> executeRequestResponseLoopOn: @10 line 9
[GsNMethod 190446337]
39 ExecBlock0 (ExecBlock) >> on:do: @3 line 44  [GsNMethod 5883905]
40 ZnManagingMultiThreadedServer (ZnMultiThreadedServer) >>
executeRequestResponseLoopOn: @4 line 11  [GsNMethod 176476929]
41 [] in ZnMultiThreadedServer >> serveConnectionsOn: @36 line 17
[GsNMethod 199124993]
42 ExecBlock0 (ExecBlock) >> on:do: @3 line 44  [GsNMethod 5883905]
43 [] in ZnMultiThreadedServer >> serveConnectionsOn: @32 line 18
[GsNMethod 198483457]
44 ExecBlock0 (ExecBlock) >> ensure: @2 line 12  [GsNMethod 5890817]
45 [] in ZnMultiThreadedServer >> serveConnectionsOn: @28 line 20
[GsNMethod 197619201]
46 [] in ExecBlock >> ifCurtailed: @7 line 6  [GsNMethod 149952513]
47 ExecBlock0 (ExecBlock) >> ensure: @2 line 12  [GsNMethod 5890817]
48 ExecBlock0 (ExecBlock) >> ifCurtailed: @3 line 8  [GsNMethod 149680897]
49 [] in ZnMultiThreadedServer >> serveConnectionsOn: @24 line 23
[GsNMethod 190449153]
50 ExecBlock >> valueWithArguments: @1 line 7  [GsNMethod 5892097]
51 GsProcess >> _start @7 line 16  [GsNMethod 6186753]
52 <Reenter marker>



--
Sent from: http://forum.world.st/GLASS-f1460844.html
_______________________________________________
Glass mailing list
[hidden email]
https://lists.gemtalksystems.com/mailman/listinfo/glass
Reply | Threaded
Open this post in threaded view
|

Re: SafelyPerformBlockRequiringAbort error when running Seaside

GLASS mailing list

Okay, it looks like the class WARetryHttpRequest is not present in your image (the fact that you've got a Set there instead of the class WARetryHttpRequest is the clue).

The class WARetryHttpRequest is in the package Seaside-GemStone320-Core and from BaselineOfSeaside3:

  spec
    for: #(#'gs3.2.x' #'gs3.3.x' #'gs3.4.x' #'gs3.5.x' #'gs3.6.x')
    do: [ 
      spec
        package: 'Seaside-Core'
          with: [ spec includes: #('Seaside-GemStone320-Core') ];
        package: 'Seaside-GemStone320-Core'
          with: [ 
              spec
                requires: #('Seaside-Core');
                includes: #('Seaside-GemStone-Core') ];

It's not clear how you could have loaded Seaside without installing that package... I'm looking at a Seaside install based upon [hidden email]:

rogue:Seaside>git log
commit 52c653b70649bdb2fda1e873528bfb1323455a35 (HEAD -> master, origin/master, origin/HEAD)Merge: a9b91bbc c5bf3d71
Author: Dale Henrichs [hidden email]
Date:   Mon Jun 17 10:41:41 2019 -0700

    Merge pull request #1132 from SeasideSt/issue_1131
    
    add GemStone3.5.0 to the travis lineup

At this point getting some more information about what expression you used to load Seaside and which Seaside repository you are loading from would probably help us get to the bottom of the problem ...

Dale

On 2/19/20 1:32 PM, BrunoBB via Glass wrote:
Dale,

Sorry about that here is the stack:
----------- Internal Zinc ERROR Encountered:
2020-02-19T13:30:22.46508693695068-08:00
a MessageNotUnderstood occurred (error 2010), a
SafelyPerformBlockRequiringAbort class does not understand  #'do:'
1 GRGemStonePlatform >> logError:title:shouldCommit: @2 line 4  [GsNMethod
148908289]
2 GRGemStonePlatform >> logError:title: @2 line 3  [GsNMethod 148908033]
3 WAGsZincAdaptor >> internalServerErrorMessage: @16 line 14  [GsNMethod
277678593]
4 [] in GRGemStonePlatform >> seasideProcessRequest:adaptor:resultBlock: @31
line 15  [GsNMethod 225123329]
5 MessageNotUnderstood (AbstractException) >> _executeHandler: @7 line 11 
[GsNMethod 6147073]
6 MessageNotUnderstood (AbstractException) >> _signalWith: @1 line 2 
[GsNMethod 6154241]
7 MessageNotUnderstood (AbstractException) >> signal @2 line 47  [GsNMethod
6154753]
8 SafelyPerformBlockRequiringAbort class (Object) >> doesNotUnderstand: @9
line 10  [GsNMethod 5646849]
9 SafelyPerformBlockRequiringAbort class (Object) >>
_doesNotUnderstand:args:envId:reason: @8 line 14  [GsNMethod 5656321]
10 SafelyPerformBlockRequiringAbort class (Object) >> accompaniedBy:do: @2
line 6  [GsNMethod 5569025]
11 Set (Collection) >> addAll: @7 line 7  [GsNMethod 2940417]
12 Set (UnorderedCollection) >> , @4 line 5  [GsNMethod 53810177]
13 [] in GRGemStonePlatform >> seasideProcessRequestWithRetry:resultBlock:
@15 line 13  [GsNMethod 225124865]
14 ExecBlock0 (ExecBlock) >> ensure: @2 line 12  [GsNMethod 5890817]
15 TransientRecursionLock >> critical: @11 line 12  [GsNMethod 13794305]
16 GRGemStonePlatform >> seasideProcessRequestWithRetry:resultBlock: @3 line
6  [GsNMethod 221593089]
17 [] in GRGemStonePlatform >> seasideProcessRequest:adaptor:resultBlock:
@17 line 6  [GsNMethod 236484353]
18 Array (Collection) >> do: @5 line 10  [GsNMethod 2944257]
19 [] in GRGemStonePlatform >> seasideProcessRequest:adaptor:resultBlock: @7
line 5  [GsNMethod 225123585]
20 ExecBlock0 (ExecBlock) >> on:do: @3 line 44  [GsNMethod 5883905]
21 GRGemStonePlatform >> seasideProcessRequest:adaptor:resultBlock: @2 line
12  [GsNMethod 221591041]
22 WAGsZincAdaptor >> process: @3 line 4  [GsNMethod 277678849]
23 ZnSeasideServerAdaptorDelegate >> handleRequest: @3 line 4  [GsNMethod
277697281]
24 [] in ZnSingleThreadedServer >> authenticateAndDelegateRequest: @11 line
12  [GsNMethod 190152449]
25 ZnManagingMultiThreadedServer (ZnSingleThreadedServer) >>
authenticateRequest:do: @4 line 6  [GsNMethod 176040961]
26 ZnManagingMultiThreadedServer (ZnSingleThreadedServer) >>
authenticateAndDelegateRequest: @2 line 8  [GsNMethod 176047105]
27 [] in ZnSingleThreadedServer >> handleRequestProtected: @6 line 5 
[GsNMethod 190153217]
28 ExecBlock0 (ExecBlock) >> on:do: @3 line 44  [GsNMethod 5883905]
29 ZnManagingMultiThreadedServer (ZnSingleThreadedServer) >>
handleRequestProtected: @2 line 6  [GsNMethod 176047361]
30 ZnManagingMultiThreadedServer (ZnSingleThreadedServer) >> handleRequest:
@5 line 9  [GsNMethod 176046081]
31 [] in ZnMultiThreadedServer >> executeOneRequestResponseOn: @13 line 11 
[GsNMethod 190445569]
32 ExecBlock0 (ExecBlock) >> on:do: @3 line 44  [GsNMethod 5883905]
33 ZnManagingMultiThreadedServer (ZnMultiThreadedServer) >>
executeOneRequestResponseOn: @6 line 15  [GsNMethod 176476673]
34 [] in ZnMultiThreadedServer >> executeRequestResponseLoopOn: @14 line 10 
[GsNMethod 197617921]
35 [] in DynamicVariable class >> value:during: @15 line 9  [GsNMethod
91607297]
36 ExecBlock0 (ExecBlock) >> ensure: @2 line 12  [GsNMethod 5890817]
37 ZnCurrentServer class (DynamicVariable class) >> value:during: @6 line 10 
[GsNMethod 75520257]
38 [] in ZnMultiThreadedServer >> executeRequestResponseLoopOn: @10 line 9 
[GsNMethod 190446337]
39 ExecBlock0 (ExecBlock) >> on:do: @3 line 44  [GsNMethod 5883905]
40 ZnManagingMultiThreadedServer (ZnMultiThreadedServer) >>
executeRequestResponseLoopOn: @4 line 11  [GsNMethod 176476929]
41 [] in ZnMultiThreadedServer >> serveConnectionsOn: @36 line 17 
[GsNMethod 199124993]
42 ExecBlock0 (ExecBlock) >> on:do: @3 line 44  [GsNMethod 5883905]
43 [] in ZnMultiThreadedServer >> serveConnectionsOn: @32 line 18 
[GsNMethod 198483457]
44 ExecBlock0 (ExecBlock) >> ensure: @2 line 12  [GsNMethod 5890817]
45 [] in ZnMultiThreadedServer >> serveConnectionsOn: @28 line 20 
[GsNMethod 197619201]
46 [] in ExecBlock >> ifCurtailed: @7 line 6  [GsNMethod 149952513]
47 ExecBlock0 (ExecBlock) >> ensure: @2 line 12  [GsNMethod 5890817]
48 ExecBlock0 (ExecBlock) >> ifCurtailed: @3 line 8  [GsNMethod 149680897]
49 [] in ZnMultiThreadedServer >> serveConnectionsOn: @24 line 23 
[GsNMethod 190449153]
50 ExecBlock >> valueWithArguments: @1 line 7  [GsNMethod 5892097]
51 GsProcess >> _start @7 line 16  [GsNMethod 6186753]
52 <Reenter marker>



--
Sent from: http://forum.world.st/GLASS-f1460844.html
_______________________________________________
Glass mailing list
[hidden email]
https://lists.gemtalksystems.com/mailman/listinfo/glass

_______________________________________________
Glass mailing list
[hidden email]
https://lists.gemtalksystems.com/mailman/listinfo/glass
Reply | Threaded
Open this post in threaded view
|

Re: SafelyPerformBlockRequiringAbort error when running Seaside

GLASS mailing list
Dale,

I tryed again in a fresh installation (without my packages only Seaside) and
the same error.
To install Seaside:
Gofer new
  package: 'GsUpgrader-Core';
  url: 'http://ss3.gemtalksystems.com/ss/gsUpgrader';
  load.
(Smalltalk at: #GsUpgrader) upgradeGrease.
GsDeployer deploy: [
  Metacello new
    baseline: 'Seaside3';
    repository: 'github://GsDevKit/Seaside31:gs_master/repository';
    onLock: [:ex | ex honor];
    load: 'CI' ].

You are right the class WARetryHttpRequest is not present neither
Seaside-GemStone320-Core package.

The package is present locally at:
/home/gemstone/GsDevKit_home/server/stones/devKit_351s/logs/github-cache/GsDevKit/Seaside31/gs_master/GsDevKit-Seaside31-b166df7/repository/Seaside-GemStone320-Core.package/

Not sure what other information you will need...
Tomorrow morning i will try everything from the scratch again (going home
now :)



--
Sent from: http://forum.world.st/GLASS-f1460844.html
_______________________________________________
Glass mailing list
[hidden email]
https://lists.gemtalksystems.com/mailman/listinfo/glass
Reply | Threaded
Open this post in threaded view
|

Re: SafelyPerformBlockRequiringAbort error when running Seaside

GLASS mailing list
Dale,

Check:
https://github.com/GsDevKit/Seaside31/blob/gs_master/repository/BaselineOfSeaside3.package/BaselineOfSeaside3.class/instance/baselinegemstone..st#L123

spec
    for: #(#'gs3.2.x' #'gs3.3.x' #'gs3.4.x')

But gs3.5.x is missing ...

regards,
bruno



--
Sent from: http://forum.world.st/GLASS-f1460844.html
_______________________________________________
Glass mailing list
[hidden email]
https://lists.gemtalksystems.com/mailman/listinfo/glass
Reply | Threaded
Open this post in threaded view
|

Re: SafelyPerformBlockRequiringAbort error when running Seaside

GLASS mailing list
Hi Bruno,

I can’t be sure, but I believe the GsDevKit/Seaside31 branch is becoming obsolete.

I had a successful 3.2 install in 3.5.1 following the instructions here:

https://github.com/GsDevKit/GsDevKit_home/blob/master/docs/gettingStartedWithSeaside.md

It uses the main Seaside repo at: GitHub.com/SeasideSt/Seaside

Cheers,


J

> On 20 Feb 2020, at 9:27 am, BrunoBB via Glass <[hidden email]> wrote:
>
> Dale,
>
> Check:
> https://github.com/GsDevKit/Seaside31/blob/gs_master/repository/BaselineOfSeaside3.package/BaselineOfSeaside3.class/instance/baselinegemstone..st#L123
>
> spec
>    for: #(#'gs3.2.x' #'gs3.3.x' #'gs3.4.x')
>
> But gs3.5.x is missing ...
>
> regards,
> bruno
>
>
>
> --
> Sent from: http://forum.world.st/GLASS-f1460844.html
> _______________________________________________
> Glass mailing list
> [hidden email]
> https://lists.gemtalksystems.com/mailman/listinfo/glass

_______________________________________________
Glass mailing list
[hidden email]
https://lists.gemtalksystems.com/mailman/listinfo/glass
Reply | Threaded
Open this post in threaded view
|

Re: SafelyPerformBlockRequiringAbort error when running Seaside

GLASS mailing list
Dale/Jupiter,

It seems that GsDevKit/Seaside31 that i was using is obsolete (it should be
marked as that).

Using current Seaside master from SeasideSt i got everything working:

GsDeployer deploy: [
  Metacello new
    baseline: 'Seaside3';
    repository: 'github://SeasideSt/Seaside:master/repository';
    onLock: [:ex | ex honor];
    load: 'CI' ].

Thanks to both :)

Regards,
Bruno



--
Sent from: http://forum.world.st/GLASS-f1460844.html
_______________________________________________
Glass mailing list
[hidden email]
https://lists.gemtalksystems.com/mailman/listinfo/glass
Reply | Threaded
Open this post in threaded view
|

Re: SafelyPerformBlockRequiringAbort error when running Seaside

GLASS mailing list
In reply to this post by GLASS mailing list
The GsDevKit/Seaside31 repository was originally created (in 2013)
because Seaside development was not available on Github (until 2015). A
little over a year ago[1], I decided to start recommending that the
official SeasidSt github repository[2] be used instead of
GsDevKit/Seaside31 and in concert with that I stopped updating the
baseline for GsDevKit/Seaside31. My last update was last April[3]. If
you look at the travis build history[4], you'll see that the last time a
travis build ran green was 3 years ago[5]. Up until last April, the
GsDevKit/Seaside31 builds were tested by internal builds on a regular
basis...

Sooo, I would recommend that you switch to using SeasidSt/Seaside, but
if that is too big of a job to take on - the current version of
SeasidSt/Seaside is 3.4.0[6] and GsDevKit/Seaside31 is still at 3.1, so
it wouldn't necessarily be an easy migration, you could update the
baseline, using this commit as reference[7], since that's when I added
3.4 to the lineup and it is very likely that that is all that is needed
... I'm reluctant to update the GsDevKit/Seaside31repository, since it
doesn't use SmalltalkCI and SeasidSt/Seaside is the Seaside repository
of record ...

I see that SeasidSt/Seaside has a tag for 3.1.3[8], but that version
also would need to have it's baseline updated and it seems that
Travis-CI support was added after the 3.1.3 release ....

In the short term it looks like your best bet would be to add 3.5.x to
the GsDevKit/Seaside31 baseline and then run the tests ... when I added
3.4 to the baseline it looks like it wasn't necessary to update the
Seaside code base (most of the gemstone version specific changes get
made in GLASS1 and that is consistently maintained), so that will likely
be all that is necessary for you to move forward....

In the longer term, if you (and others?) expect to continue using
Seaside 3.1 for the foreseeable future, it would be worth adding
travis-ci support to 3.1.3 on SeasideSt/Seaside ... and it would be
useful to get Johan and Philippe involved in a discussion on how that
would be done ...  a 3.1.3 branch could be created where the travis
support could be added and the baseline changes for later versions of
GemStone  could b managed.

I don't have a lot of free time right now, but I could help folks work
through any kinks in the process that might run into ...

Dale

[1]
https://github.com/GsDevKit/GsDevKit_home/commit/902fdcad12c63a08595486ffa9bb9cb962048bf8#diff-04c6e90faac2675aa89e2176d2eec7d8
[2] https://github.com/SeasideSt/Seaside
[3]
https://github.com/GsDevKit/Seaside31/commit/b166df7c2e5e373ccd46db322e55282924b27856
[4] https://travis-ci.org/GsDevKit/Seaside31/builds
[5] https://travis-ci.org/GsDevKit/Seaside31/builds/257455740
[6] https://github.com/SeasideSt/Seaside/releases
[7]
https://github.com/GsDevKit/Seaside31/commit/5900bc1925d0ff001e5264f45daec3c7a895147c
[8] https://github.com/SeasideSt/Seaside/releases/tag/v3.1.3
On 2/19/20 2:22 PM, BrunoBB via Glass wrote:

> Dale,
>
> I tryed again in a fresh installation (without my packages only Seaside) and
> the same error.
> To install Seaside:
> Gofer new
>    package: 'GsUpgrader-Core';
>    url: 'http://ss3.gemtalksystems.com/ss/gsUpgrader';
>    load.
> (Smalltalk at: #GsUpgrader) upgradeGrease.
> GsDeployer deploy: [
>    Metacello new
>      baseline: 'Seaside3';
>      repository: 'github://GsDevKit/Seaside31:gs_master/repository';
>      onLock: [:ex | ex honor];
>      load: 'CI' ].
>
> You are right the class WARetryHttpRequest is not present neither
> Seaside-GemStone320-Core package.
>
> The package is present locally at:
> /home/gemstone/GsDevKit_home/server/stones/devKit_351s/logs/github-cache/GsDevKit/Seaside31/gs_master/GsDevKit-Seaside31-b166df7/repository/Seaside-GemStone320-Core.package/
>
> Not sure what other information you will need...
> Tomorrow morning i will try everything from the scratch again (going home
> now :)
>
>
>
> --
> Sent from: http://forum.world.st/GLASS-f1460844.html
> _______________________________________________
> Glass mailing list
> [hidden email]
> https://lists.gemtalksystems.com/mailman/listinfo/glass
_______________________________________________
Glass mailing list
[hidden email]
https://lists.gemtalksystems.com/mailman/listinfo/glass
Reply | Threaded
Open this post in threaded view
|

Re: SafelyPerformBlockRequiringAbort error when running Seaside

GLASS mailing list
Dale,

Thanks for the explanation.

I already installed my application using "SeasideSt/Seaside:master" and now
i'm testing it.

For now my approach will be a migration to latest Seaside.

If i find any hard problem i will follow your instructions but for now
everything looks ok.

regards,
bruno



--
Sent from: http://forum.world.st/GLASS-f1460844.html
_______________________________________________
Glass mailing list
[hidden email]
https://lists.gemtalksystems.com/mailman/listinfo/glass