Problems with Postmark in Pharo 2.0 with and without Seaside
Locked
 
|
Hi guys,
I'm going to crosspost to the seaside and pharo lists, so please forgive me First: I'm stuck in installing Postmark, I think is something wrong with seaside, because on a Pharo 2.0 clean image everything is fine So the scenario is: On Pharo 2.0 and clean image, cmd-p on: Gofer new url: 'http://smalltalkhub.com/mc/PharoExtras/Postmark/main' ; package: 'ConfigurationOfPostMark'; load. (Smalltalk at: #ConfigurationOfPostMark) project stableVersion load. returns: a MetacelloFetchingMCSpecLoader(linear load : explicit load : 1.0 [ConfigurationOfPostMark] load : ConfigurationOfGrease-JohanBrichau.236 explicit load : 1.0 [ConfigurationOfPostMark] load : ConfigurationOfJSON-PaulDeBruicker.3 linear load : 1.0 [ConfigurationOfPostMark] linear load : 1.0.8 [ConfigurationOfGrease] load : Grease-Core-pmm.72 load : Grease-Pharo20-Core-pmm.1 linear load : 1.0 [ConfigurationOfJSON] load : JSON-ul.35 load : PostMark-Core-PaulDeBruicker.15) On Pharo 2.0 and clean image, cmd-p on: Gofer new url: 'http://smalltalkhub.com/mc/PharoExtras/Postmark/main' ; package: 'ConfigurationOfPostMark'; load. (Smalltalk at: #ConfigurationOfPostMark) project stableVersion load. gives me: - a DNU GRPackage(Object)>>doesNotUnderstand: #includesSelector:ofClassName: - then an alert: "You are about to load new versions of the following packages that have unsaved changes in the images: Zinc-FileSystem" I press merge - then another alert: "You are about to load new versions of the following packages that have unsaved changes in the images: Zinc-HTTP" I press merge so finally the result of cmd-p is: a MetacelloFetchingMCSpecLoader(linear load : explicit load : 1.0 [ConfigurationOfPostMark] load : ConfigurationOfGrease-JohanBrichau.236 explicit load : 1.0 [ConfigurationOfPostMark] load : ConfigurationOfJSON-PaulDeBruicker.3 explicit load : 1.0 [ConfigurationOfPostMark] load : ConfigurationOfSeaside3-JohanBrichau.71 linear load : 1.0 [ConfigurationOfPostMark] explicit load : 1.0.8 [ConfigurationOfGrease] linear load : 1.0.8 [ConfigurationOfGrease] load : Grease-Core-pmm.72 load : Grease-Pharo20-Core-pmm.1 load : Grease-Tests-Core-DamienCassou.81 explicit load : 3.0.9 [ConfigurationOfSeaside3] explicit load : 3.0.9 [ConfigurationOfSeaside3] explicit load : 3.0.9 [ConfigurationOfSeaside3] load : ConfigurationOfSPort2-JohanBrichau.12 explicit load : 3.0.9 [ConfigurationOfSeaside3] explicit load : 3.0.9 [ConfigurationOfSeaside3] explicit load : 3.0.9 [ConfigurationOfSeaside3] load : ConfigurationOfZincHTTPComponents-SvenVanCaekenberghe.59 linear load : 3.0.9 [ConfigurationOfSeaside3] linear load : 1.0.8 [ConfigurationOfGrease] linear load : 1.0.8 [ConfigurationOfGrease] linear load : 2.4.6 [ConfigurationOfZincHTTPComponents] load : Zinc-Character-Encoding-Core-SvenVanCaekenberghe.28 load : Zinc-Character-Encoding-Tests-SvenVanCaekenberghe.15 load : Zinc-Resource-Meta-Core-SvenVanCaekenberghe.28 load : Zinc-Resource-Meta-Tests-SvenVanCaekenberghe.16 load : Zinc-FileSystem-SvenVanCaekenberghe.10 load : Zinc-HTTP-SvenVanCaekenberghe.383 load : Zinc-Tests-SvenVanCaekenberghe.199 load : Seaside-Core-pmm.771 postload : Seaside-Core >> seaside304DoIts load : Javascript-Core-pmm.94 load : Seaside-Tests-Core-pmm.258 load : Seaside-Tests-Canvas-pmm.59 load : Javascript-Tests-Core-pmm.68 linear load : 2.33 [ConfigurationOfSPort2] load : FileSystem-Legacy-JohanBrichau.2 linear load : 1.0.8 [ConfigurationOfGrease] linear load : 1.0.8 [ConfigurationOfGrease] linear load : 1.0 [ConfigurationOfJSON] load : JSON-ul.35 load : PostMark-Core-PaulDeBruicker.15) Wow, so many more packages than the clean image! Second: That's not the end of the story, both in Pharo 2 clean image then the image with Seaside, if I evaulate: email := PMEmail new from: 'me@me.com'; to: 'you@you.com'; subject: 'whatever'; textBody: 'test'; yourself. interface := PMInterface new. interface apiKey: 'my key'. interface send: email. I discover 1) textBody is no more a valid selector (so PMInterface comment is obsolete), I got rid of it and I tried again, but 2) I get an alert: NameLookupFailure: cannot resolve 'api.postmark.com' Gosh! Hints? TIA Dave |
Re: Problems with Postmark in Pharo 2.0 with and without Seaside
|
Hi Dave,
Looks like I broke somethings. I'll take a look now. The answer to your second question is that the api endpoint url is api.postmarkapp.com not postmark.com. Give that a try and see if you get further along. I'll include that fix when I get the rest of it working here in a bit. Sorry you ran into problems Paul
|
|
|
Hi Paul,
I've just posted on the pharo-users list, but I write that post here: ----------------- Hi, I solved a couple of issues 1) I didn't see PMEmail is a JsonObject. Now I understand why selector textBody: is not known by the system but it's valid. 2) The "NameLookupFailure: cannot resolve 'api.postmark.com'" is because PMInterface class>> defaultApiUrl ^ 'http://api.postmark.com/' instead of: PMInterface class>> defaultApiUrl ^ 'http://api.postmarkapp.com/' ** Can anyone who has access to the project change it? ** With the change it works! ----------------- Paul, what's really weird is the set of packages loaded in the seaside version (merges included) and the DNU GRPackage(Object)>>doesNotUnderstand: #includesSelector:ofClassName: Dave
|
Re: Problems with Postmark in Pharo 2.0 with and without Seaside
|
|
Hi Dave,
I can make the changes to PostMark What Seaside version are you installing prior to installing PostMark? PostMark is updating Zinc to the current #stable. I wonder why the Seaside install dirties Zinc packages. It probably shouldn't. Paul
|
|
|
I'm using Seaside 3.0.x but I don't know which x :-). Do you know how to retrieve it?
The version of ConfigurationOfSeaside3 on my package-cache is this one: Name: ConfigurationOfSeaside3-DiegoLont.15 Author: DiegoLont Time: 2 September 2013 Dave
|
|
|
In reply to this post by Paul DeBruicker
I tried to load the version 0.6 of PostMark on my seaside image:
The cmd-p of (Smalltalk at: #ConfigurationOfPostMark) project load: '0.6' returns: a MetacelloFetchingMCSpecLoader(linear load : explicit load : 0.6 [ConfigurationOfPostMark] load : ConfigurationOfGrease-JohanBrichau.236 linear load : 0.6 [ConfigurationOfPostMark] explicit load : 1.0.8 [ConfigurationOfGrease] linear load : 1.0.8 [ConfigurationOfGrease] load : Grease-Core-pmm.72 load : Grease-Pharo20-Core-pmm.1 load : Grease-Tests-Core-DamienCassou.81 load : JSON-ul.35 load : PostMark-Core-FrancoisStephany.11) So no updates of Zinc nor Seaside, I can send emails via Postmark, but as before, there is the DNU: GRPackage(Object)>>doesNotUnderstand: #includesSelector:ofClassName: here the full stack --- The full stack --- GRPackage(Object)>>doesNotUnderstand: #includesSelector:ofClassName: [:each | (each includesSelector: self selector ofClassName: self origin theNonMetaClass originalName) or: [each includesSelector: self selector ofMetaclassName: self origin theNonMetaClass originalName]] in CompiledMethod>>packageFromOrganizer: [:each | (aBlock value: each) ifTrue: [^ each]. nil] in Array(Collection)>>detect:ifNone: Array(SequenceableCollection)>>do: Array(Collection)>>detect:ifNone: CompiledMethod>>packageFromOrganizer: RPackageOrganizer>>systemMethodModifiedActionFrom: WeakMessageSend>>value: WeakMessageSend>>cull: WeakMessageSend>>cull:cull: [action cull: anAnnouncement cull: announcer] in WeakAnnouncementSubscription>>deliver: BlockClosure>>on:do: [Processor terminateActive] in [:ex | | copy onDoCtx process handler bottom thisCtx | onDoCtx := thisContext. thisCtx := onDoCtx home. [onDoCtx sender == thisCtx] whileFalse: [onDoCtx := onDoCtx sender. onDoCtx ifNil: [^ handlerAction cull: ex]]. bottom := [Processor terminateActive] asContext. onDoCtx privSender: bottom. handler := [handlerAction cull: ex] asContext. handler privSender: thisContext sender. (Process forContext: handler priority: Processor activePriority) resume. thisContext privSender: thisCtx. nil] in BlockClosure>>on:fork: ------------------------------------------------------------------------------- Dave |
Re: Problems with Postmark in Pharo 2.0 with and without Seaside
|
|
Hi Dave,
Try using a clean Pharo 2 image, the latest ConfigurationOfSeaside3 (e.g. from here:http://smalltalkhub.com/#!/~Seaside/MetacelloConfigurations ), and loading the stable version of PostMark. doing that I get no errors. Not sure why its happening in your image. Also I did update the config to include your URL fix. Thanks for spotting it and reporting it Paul
|
|
|
Hi Paul,
To sum up. Loading Postmark: 1) On a clean Pharo 2 image, no problem. 2) On a clean Pharo 2 image + Seaside 3.0.9, no problem. 3) On my image that is a Pharo 2 + Seaside 3.0.8, DNU GRPackage(Object)>>doesNotUnderstand: #includesSelector:ofClassName: I don't understand why, but I also tried to load a previous version of Postmark: (Smalltalk at: #ConfigurationOfPostMark) project version:'0.6' it does not start the load of Seaside 3.0.9 nor Zinc, but at the end of loading all packages it returns the DNU above :-( Now, a couple of notes: 1) I don't need (want) to update Seaside. I made a couple of manual tests with Postmark version 0.6 and it works, so I gonna load that version. Paul, is there any warning on doing that? 2) During several attempts in loading seaside from a clean pharo image I evaluated the code I found on http://www.seaside.st/download/pharo i.e. Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside30'; load. (Smalltalk at: #ConfigurationOfSeaside30) load. That code does not work because it should load version "3.1.0-gemstone [ConfigurationOfSeaside30]" that, if I understand, is not available in ConfigurationOfSeaside30 but in ConfigurationOfSeaside3 !!! Someone should update http://www.seaside.st/download/pharo. Actually, who is the manager of Seaside project? |
|
|
In reply to this post by Dave
I share your pain ... I have basically given up trying to use Pharo or Squeak and Seaside as usually I get an error of some sort when trying to load many packages, usually because of some sort of version dependency issue.
_______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
Yep Recursive,
It's not an easy ride. From time to time I start from a clean image and load all the packages, but you must have a very strong set of tests. Dave
|
Re: Problems with Postmark in Pharo 2.0 with and without Seaside
|
|
Hi guys,
Let us try to help you... For starters, I just updated the download instructions now on seaside.st. The switch from ConfigurationOfSeaside30 to ConfigurationOfSeaside3 and from Squeaksource to Smalltalkhub was necessary but does not make it a smooth ride because other projects should update their references. In addition, there is a VM bug that often pops up when loading packages with metacello in Pharo2.0. And probably there are a number of configuration problems somewhere. Now, does the ConfigurationOfPostMark reference the correct Seaside repository and configuration? As a side note: if you are not able to load your project with all its dependencies in an automated way, you will end up in trouble at some point... so it's worth the time to figure out the issues cheers Johan On 20 Dec 2013, at 08:02, Dave <[hidden email]> wrote: > Yep Recursive, > It's not an easy ride. From time to time I start from a clean image and load > all the packages, but you must have a very strong set of tests. > Dave > > > recursive wrote >> I share your pain ... I have basically given up trying to use Pharo or >> Squeak and Seaside as usually I get an error of some sort when trying to >> load many packages, usually because of some sort of version dependency >> issue. >> >> _______________________________________________ >> seaside mailing list > >> seaside@.squeakfoundation > >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > > > > > -- > View this message in context: http://forum.world.st/Problems-with-Postmark-in-Pharo-2-0-with-and-without-Seaside-tp4730958p4731318.html > Sent from the Seaside General mailing list archive at Nabble.com. > _______________________________________________ > seaside mailing list > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
Thanks Johan Brrr. That's why I keep seaside 3.0.8 as long as possible yes, it's correct. Cheers Dave
|
«
Return to Seaside General
|
1 view|%1 views
| Free forum by Nabble | Edit this page |