Re: Concerning that big, big bug

  (Dhyani) wrote:

> Jagrata wrote:
> 
> 
> 
>>Priyadarshan wrote:
>>
>>>Hi Jagrata,
>>>
>>>this bug brings up a situation which was not foreseen: some developers
>>>are unable to develop with all the feature of zope, due to platform
>>>limitations.
>>>
>>>I still am very hesitant to use zopestage without a proper testing
>>>procedure, which is expensive.
>>
>>I have kicked the staging zope on vasudev.
>>It is running now with version 56 of the repo
>>and a refreshed races filestorage.
>>
> 
> 
> All right, error still there.
Is there a traceback? I presume the error is that
no mail is sent when registering--Issue 01.
Is that right?
(need gforge...)

>>>What would you like us to do:
>>>1) use zopestage also for developers' own testing (vs only for testers,
>>>with proper testing cycle)
>>
>>Dhyani, does using the stage on vasudev help to address the issue?
> 
> 
> The problem is that the error is raised by methods on the filesystem. Do I
> have access to the filesystem on stage?

No you don't. If you need it in order to address the problem,
then we have to give it to you and teach you how to work in
the bash shell on Linux/FreeBSD. That is overhead I want to
avoid. If it can't be avoided, then we stop, learn bash, and
mark off dev areas on new staging server. Priydarshan would
need to make this call.

What methods on the filesystem raise errors?
Can you supply a traceback?

>>I have also opened the stage on supreme at
>>http://supreme.vasudevaserver.net:7072/
>>Since we are going to freeBSD, we will want to make
>>sure the issue occurs there. Dhyani, please check, thanks.
> 
> 
> Is this a different Zope installation? All files different? Or just some
> mount thing? - The error occurs there, too.

It is a different zope installation, on a new machine called
supreme. That machine runs on the FreeBSD operating system.
Not all files are different; it is looking at the same Data.fs,
which is on the production machine, vasudev.

...
>>>3) try to see if there is any way to solve this problem on windows.
>>>What about any future problems?
>>
>>If we plan to support windows, we should test all features on windows.
>>That is a separate thread, I suppose.
> 
> 
> I do not understand this problem as operating system related. Maybe I just
> don't understand what you guys are talking about, but my feeling is
> definitely not that things go well on Windows and crash on Linux, if that is
> what you mean.
You might be right. However, the eol problem we had recently
was os related. The traceback showing "\r\n" in the python
script revealed that.

> 
> Dhyani


--------------------------------------------------------------------------
This message is sent to you because you are subscribed to the mailing list <VasudevaService-K9y3B4ipJAZZAIG4hdpdiNBPR1lH4CV8@public.gmane.org>.