WAGemStoneRunSeasideGems class>>#executeGemCommand: path may need edited

[pdebruic]

Hi Dale,

I get an error when running

tode> seaside/seasideWebServer --start

---start Seaside gems (03/29/2016 21:53:46)
/private/var/tmp/tmp.0Tz2pU: line 1: /opt/git/GsDevKit_home/server/stones/3213b/productseaside/bin/runSeasideGems30: No such file or directory

editing the line that sets the commandLine temp var in the method mentioned in the subject to

  commandLine := (GsFile _expandEnvVariable: 'GEMSTONE' isClient: false)
    , '/seaside/bin/runSeasideGems30 ' , command , ' ' , self default name , ' '
    , self defaultPortString.

fixes it.

[dalehenrich]

I think this method has been a thorn in my side for a long time and I
could swear that I've fixed it at various times in the past, but ???

Anyway, if you have a pull request with the fix, I can integrate it ...

On 03/29/2016 02:58 PM, Paul DeBruicker wrote:

Hi Dale,

I get an error when running

|tode> seaside/seasideWebServer --start|

|---start Seaside gems (03/29/2016 21:53:46)
/private/var/tmp/tmp.0Tz2pU: line 1:
/opt/git/GsDevKit_home/server/stones/3213b/productseaside/bin/runSeasideGems30:
No such file or directory |

editing the line that sets the commandLine temp var in the method
mentioned in the subject to

|commandLine := (GsFile _expandEnvVariable: 'GEMSTONE' isClient: false)
, '/seaside/bin/runSeasideGems30 ' , command , ' ' , self default name
, ' ' , self defaultPortString. |

fixes it.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#5

[dalehenrich]

@pdebruic - It looks to me that that edit is already present on the gs_master branch: GsDevKit/Seaside31@6a614c5; and that commit is present in 3.1.4.2 ... so perhaps you are using a slightly older version of Seaside31? ... What SHA are you on?

[pdebruic]

Hi Dale,

When I do 'project list' I get an UndefinedObject dnu '#projectPath:' So I don't know how to learn the SHA. IT should be #stable. So whatever SHA that is.

Paul

On Mar 30, 2016, at 8:12 PM, Dale Henrichs [email protected] wrote:

@pdebruic - It looks to me that that edit is already present on the gs_master branch: GsDevKit/Seaside31@6a614c5; and that commit is present in 3.1.4.2 ... so perhaps you are using a slightly older version of Seaside31? ... What SHA are you on?

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

[dalehenrich]

If you are using #stable, then it depends upon a) when you loaded the
project and b) how #stable is defined in the configuration and by
extension c) which version of the configuration you have loaded ... At
one point in time the seaside configuration was changed to load from
Github, in which case you would have a SHA in the project list ...

So you are using an older version of Seaside and the issue has been
recently patched and you've patched the problem in your system ...

All we need to do now is get your project list fixed... if you give me
a stack and/or put the stack into an issue report I can help fix the DNU
...

Dale

On 03/31/2016 11:10 AM, Paul DeBruicker wrote:

Hi Dale,

When I do 'project list' I get an UndefinedObject dnu '#projectPath:'
So I don't know how to learn the SHA. IT should be #stable. So
whatever SHA that is.

Paul

On Mar 30, 2016, at 8:12 PM, Dale Henrichs
[email protected] wrote:

@pdebruic - It looks to me that that edit is already present on the
gs_master branch: GsDevKit/Seaside31@6a614c5; and that commit is
present in 3.1.4.2 ... so perhaps you are using a slightly older
version of Seaside31? ... What SHA are you on?

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#5 (comment)