Re: [Pharo-users] MongoCursor>>execute raising 'Unexpected responseTo in response'
> On 17. Dec 2018, at 01:04, Sebastian Sastre > wrote: > > Hi All, Holger... The Mongo protocol allows multiple requests to be in transient and is using a client assigned id to indicate which request was responded to. MongoTalk is only fit to send/handle one request at a time per socket. Without more context it is difficult to say which failure mode you have but I can see these possible ones: 1.) Due to concurrency you are using the same connection but make more than one request. 2.) Our request id goes wrong (not sure how would this happen) 3.) Mongod sent a unsolicited response 4.) Many other things I can't think of right now. Is 1st) possible in your code? Do you have a packet trace to see which _responds_ you received and which request was answered? holger > I’ve seen this today: > http://forum.world.st/MongoCursor-gt-gt-execute-and-MongoTalk-changes-td4889293.html > > > After talking with some people in the Pharo chat group at Discord about this > erratic error I’m having with MongoTalk’s MongoCursor . > > > > Once it happens, the stream stays open and Mongo says isValid true but no > other operations can be executed. > > I’ve loaded MongoTalk with: > > Metacello new > githubUser: 'pharo-nosql' project: 'voyage' commitish:'1.?' path: 'mc'; > baseline: 'Voyage'; > load: 'mongo’. > > in a Pharo 6.1 image. > > Did this Unexpected responseTo happened again to you? > > nextRequestID has the code you mention in the issue: > > nextRequestID > ^requestID := requestID + 1 bitAnd: 16r3FFF > > Do you have any further hint on why the issue? Thanks! > > > Sebastian
[Pharo-users] Teapot and SSL
I had this working some many months ago, but now I can't get it to work.
Really annoying. The entire process is so arcane...
My HTTP server starts like this:
Teapot stopAll.
Teapot on
Get: blah blah blah
Then I visit http://localhost:1701/.
I created a self-signed cert called newcert.pem. My HTTPS server starts like
this:
Teapot stopAll.
secureServer := (ZnSecureServer on: 1443)
certificate: '/home/richard/newcert.pem';
logToTranscript;
start;
yourself.
teapot := Teapot configure: { #znServer -> secureServer }.
teapot
Get: blah blah blah
When I visit https://localhost/, I get "Unable to connect". I tried
localhost:1701, localhost:1443, just about every damn port number I can
think of. No joy.
So what the devil am I doing wrong???
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
Re: [Pharo-users] How to log Teapot activity
Ask a Teapot's server (which will be a Zinc HTTP Components server) to log. Teapot on server logLevel: 1; logToTranscript. Or even better, inspect the log objects emitted by Zinc HTTP Components. ZnLogEvent announcer inspect. And select the Announcements tab. > On 20 Dec 2018, at 17:02, horrido wrote: > > Is there a way to log server activity (to Transcript?) with Teapot? Without > ZnSecureServer. > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >
[Pharo-users] How to log Teapot activity
Is there a way to log server activity (to Transcript?) with Teapot? Without ZnSecureServer. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
Re: [Pharo-users] [Moose-dev] Re: glamorous toolkit: v0.4.0
Hi Luke, I am happy this looks exciting :). About the confusion part: The Glamorous Toolkit we are working on right now is a complete new world built on a complete new graphical stack that does is not based on the existing stack that ships with Pharo. It is not an evolution. It is a leap. The goal of the new GT is to propose a completely reshaped programming experience that enables moldable development. You will find the concepts from the old GT in the new world as well. For example, the Inspector is extensible in similar ways and the API is similar as well. But, in the new world, we are bringing the concept much further. For example, Documenter provides a whole new kind of a tool that can mold to unify multiple workflows (like data notebooks, code documentation, or tutorials) right in the IDE. Coder provides the infrastructure for manipulating code that can mold its shape as you type. Transcript allows you to embed various widgets to transform the otherwise dull experience of a console into a live one. Behind the scenes GT comes with several engines. The Examples engine enables example-driven development which also bridges the gap between testing and documentation effort, especially when combined with Documenter. Releaser is able to release deeply nested projects. Phlow offers an engine that shares similarities with Glamour. Completer provides moldable completion. Visualizer offers a couple of visualization engines such as Mondrian. All of these are possible because of the underlying graphical stack made of Sparta/Bloc/Brick. All in all, we believe that the new GT enables a new way of programming. Individual features can be attractive, but our goal is to reshape the development experience. Does this address the concern? Cheers, Doru > On Dec 19, 2018, at 2:09 PM, Luke Gorrie wrote: > > On Fri, 14 Dec 2018 at 05:13, Tudor Girba wrote: > Please do let us know what you think .. and, of course, what you feel. > > I'm feeling excited and confused :). > > Excited because I love seeing all these new demos streaming out and I'm > itching to put new capabilities to work. > > Confused about the roadmap. How does this "new" Glamorous Toolkit relate to > the "old" one that I learned about last year from the Moldable Tools thesis? > Is this a new version or a complete rewrite? Is it backwards compatible or > completely reimagined? Is adopting the new version a seamless process or is > porting required? Are frameworks like Glamour still there behind the scenes > or were they replaced? etc. > > > ___ > Moose-dev mailing list > moose-...@list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.feenk.com "Things happen when they happen, not when you talk about them happening."
