yes, this is a known bug.
we will fix this problem soon (is already fixed, just needs to be properly
integrated).
Esteban
> On 22 Sep 2016, at 01:28, JupiterJones wrote:
>
> Starting from the cmdline I get the following output - which I guess is
> correct since none of the listed PlugIns are
> > Hello, two questions about Seaside sessions:
> >
> > 1) URL sharing between different users - what if "boss" shares URL from
> > his browser and send it to another regular user - of course, easy way,
> > whole URL with session (_s=) - when another/regular user opens that
> > link -> whole "
> Mariano,
>
> this would be a perfect article for your blog (hint, hint) and I'd be
> one of the first and excited readers. I must admit I sometimes am
> frightened by all the filters and whatnot that I could be using for
> certain tasks. I always feel like I miss half of what the power of
>
> > > Hello, two questions about Seaside sessions:
> > >
> > > 1) URL sharing between different users - what if "boss" shares URL from
> > his browser and send it to another regular user - of course, easy way,
> > whole URL with session (_s=) - when another/regular user opens that
> > link -> w
> > Hello, two questions about Seaside sessions:
> >
> > 1) URL sharing between different users - what if "boss" shares URL from his
> > browser and send it to another regular user - of course, easy way, whole
> > URL with session (_s=) - when another/regular user opens that link ->
> > who
Starting from the cmdline I get the following output - which I guess is
correct since none of the listed PlugIns are in that path :) But they
weren't in the path before the update either.
I had no lock with the linked VM either - same result as you.
./pharo-ui Pharo.image
2016-09-22 09:22:05.231
sorry, no, i can't reproduce it.
thanks
On Wed, Sep 21, 2016 at 4:22 PM, Tudor Girba wrote:
> Hi,
>
> No, this was not at all a stupid question. It might be that we have a
> memory leak.
>
> Could you reproduce the problem?
>
> Cheers,
> Doru
>
> > On Sep 21, 2016, at 4:34 PM, Bernardo Ezequiel
Hi,
No, this was not at all a stupid question. It might be that we have a memory
leak.
Could you reproduce the problem?
Cheers,
Doru
> On Sep 21, 2016, at 4:34 PM, Bernardo Ezequiel Contreras
> wrote:
>
> everything was closed, i was using the simple workspace. but anyways there
> were ref
Martin,
which image were you using? The "unofficial" VM from the link presents a
dialog to open a file and once I select an image, it just disappears and
nothing happens after that.
--
View this message in context:
http://forum.world.st/Pharo-not-running-with-macOS-Sierra-tp4916468p4916529.ht
Hi Guille,
I was wondering if I could have kill manually this process, but the
process browser does not let you do that mistake.
Thanks for the tip.
Hilaire
Le 21/09/2016 à 12:11, Guille Polito a écrit :
> Hi Hilaire, all,
>
> I started digging this morning on this issue, and I see why we can
Mariano,
this would be a perfect article for your blog (hint, hint) and I'd be
one of the first and excited readers. I must admit I sometimes am
frightened by all the filters and whatnot that I could be using for
certain tasks. I always feel like I miss half of what the power of
Seaside is be
On Wed, Sep 21, 2016 at 11:50 AM, Johan Brichau wrote:
>
> > On 21 Sep 2016, at 12:31, Petr Fischer wrote:
> >
> > Hello, two questions about Seaside sessions:
> >
> > 1) URL sharing between different users - what if "boss" shares URL from
> his browser and send it to another regular user - of c
> On 21 Sep 2016, at 12:31, Petr Fischer wrote:
>
> Hello, two questions about Seaside sessions:
>
> 1) URL sharing between different users - what if "boss" shares URL from his
> browser and send it to another regular user - of course, easy way, whole URL
> with session (_s=) - when anoth
everything was closed, i was using the simple workspace. but anyways there
were references.
it was a stupid question, i solved it starting from a fresh image.
thanks
On Wed, Sep 21, 2016 at 1:16 AM, Tudor Girba wrote:
> Hi,
>
> You should close the respective Glamour browser. Could it be that
> On Sep 21, 2016, at 01:14, Tudor Girba wrote:
>
>> Speaking for myself, I honestly would not think about clicking on the ? icon
>> to expect these kinds of instructions. I cannot say exactly why, I only have
>> a feeling that the ? does not transmit to me that there are ‘power user’
>> tips
On Wed, Sep 21, 2016 at 3:55 AM, Holger Freyther wrote:
>
> > On 20 Sep 2016, at 20:38, Mariano Martinez Peck
> wrote:
> >
> > Hi Holger,
>
>
> Good Morning,
>
> thank you for your reply.
>
>
Good morning.
> > | reader |
> > reader := OSSAttachableFileStream name:'myStream' attachTo: aFileID
>
Thank you, Henrik.
This VM first shows a black window too, but it comes alive, once you click
one time into the window.
Best regards,
Martin.
Henrik Sperre Johansen wrote
>> i just updated to macOS Sierra, and Pharo now starts with an empty black
>> window and 100% CPU load and stays like this
On Wed, Sep 21, 2016 at 7:31 AM, Petr Fischer wrote:
> Hello, two questions about Seaside sessions:
>
> 1) URL sharing between different users - what if "boss" shares URL from
> his browser and send it to another regular user - of course, easy way,
> whole URL with session (_s=) - when anothe
> On 21 Sep 2016, at 2:07 , MartinW wrote:
>
> Hello,
>
> i just updated to macOS Sierra, and Pharo now starts with an empty black
> window and 100% CPU load and stays like this forever.
> Any ideas?
>
> Best regards,
> Martin.
It's not an "official" official release, but the following link t
Hello,
i just updated to macOS Sierra, and Pharo now starts with an empty black
window and 100% CPU load and stays like this forever.
Any ideas?
Best regards,
Martin.
--
View this message in context:
http://forum.world.st/Pharo-not-running-with-macOS-Sierra-tp4916468.html
Sent from the Pharo
2016-09-21 12:11 GMT+02:00 Guille Polito :
>
> I'm still taking a look at what would cause this. And I also think we
> still have this bug in pharo 6 (and thus pharo 5) because I found it lately
> very often.
>
> In the meantime, if you find that your image is causing you these
> problems, you can
1) If you share the url with the _s parameter, then you can continue
that session in other browser/machine.
This is so because by the default the application uses
WAQueryFieldHandlerTrackingStrategy as the #trackingStrategy config.
But you can override it and use any of the WAHandlerTrackingStrate
Hello, two questions about Seaside sessions:
1) URL sharing between different users - what if "boss" shares URL from his
browser and send it to another regular user - of course, easy way, whole URL
with session (_s=) - when another/regular user opens that link -> whole
"boss" session opens
Hi Hilaire, all,
I started digging this morning on this issue, and I see why we can have
such problems.
Apparently, there is some strange case that produces a bug in UIManager.
To explain it with code, the UIManager should satisfy allways the
following invariant.
"If executed from a worksp
24 matches
Mail list logo
