seaside-dev February 2014

seaside-dev@lists.squeakfoundation.org

10 participants
23 discussions

"Bootstrap" project for Seaside with separated Magritte support in a new project "BootstrapMagritte" on STHub
by Torsten Bergmann 16 Jul '18

16 Jul '18

Hi, The bundling with magritte polluted the repo and the Bootstrap project with stuff that was not really needed for "Seaside + Bootstrap" only. Also a "Bootstrap-Demo" package appeared that was more a demo for magritte than for Bootstrap. Since there already was an "Bootstrap-Examples" package this added more confusion (at least on my side). I now took action and cleaned up the Bootstrap project again to remove the magritte stuff. If one wants to to use Bootstrap with Seaside he does not necessarily have to go the Magritte path, so IMHO this was necessary. The magritte stuff for Bootstrap is now hosted as an own separate project on STHub which would also help to see to which part code additions really belong. As a result: ============ 1. The Bootstrap project now again only contains and loads the initial three packages: - Bootstrap-Core - Bootstrap-Tests-Core - Bootstrap-Examples assembled by the known ConfigurationOfBootstrap 2. The Magritte support on top of Bootstrap is now separated in an own project to avoid too much mixin. See "BootstrapMagritte" on SmalltalkHub. The new repo "http://smalltalkhub.com/#!/~TorstenBergmann/BootstrapMagritte" has the same commiters as the old one, so feel free to continue with your work. This project includes two packages: - Bootstrap-Magritte-Core (former Bootstrap-Magritte) - Bootstrap-Magritte-Examples (former Bootstrap-Demo) assembled by a new ConfigurationOfBootstrapMagritte for this particular project 3. The Bootstrap/ConfigurationOfBootstrap is now available as - a release version 0.4.0 for Seaside 3.0.9 - a release version 0.5.0 for Seaside 3.0.10 - a release version 0.6.0 for Seaside 3.1.0 (#stable) - a development version 0.7.0 for Seaside 3.1.0 for new stuff 4. The CI for Bootstrap is green for Pharo 2.0 and now also Pharo 3.0 5. The config browser is updated for Pharo 2.0 and Pharo 3.0 with the "Bootstrap" package So you can now also open a fresh Pharo 3.0 image, open World menu -> Configuration Browser to load "Bootstrap". Then run ZnZincServerAdaptor startOn: 8080 and start coding your web application with the latest Seaside 3.1.0. Next steps: Setting up a CI for the new project "BootstrapMagritte"/ConfigurationOfBootstrapMagritte Have fun! Bye Torsten

3 7

HTTP 302 vs 303
by Philippe Marschall 07 Jun '14

07 Jun '14

Hi I came upon this HN thread [1]. The linked article suggests we should use HTTP 303 instead of 302 (because we want a change from POST to GET). [1] http://insanecoding.blogspot.ch/2014/02/http-308-incompetence-expected.html Cheers Philippe

3 3

WAJsonParser: crossplatform readStream questions
by Diego Lont 28 Feb '14

28 Feb '14

Hi all, Nice to see that more people are working on json at the moment. I currently am working on it to move my data from pharo to gemstone, using magritte json. As Gemstone does not have a String readStream implementation, I decided to take a better look into the parsing done by seaside: and I refactored this a bit, so it only uses the core streaming methods ( peek, next, next: ) and no longer requires the stream to be positionable. I checked the tests: and they are all green, so I committed this change. Note that I assume that "next: anInteger” conforms to the “c” standard. It returns the next … characters, and if not available a shorter string. If this is not the case, it will cause that on invalid json a different error may be thrown than a WAJsonSyntaxError. Is this a problem for other platforms? And if this is a problem, do you have suggestions how to solve this cross-platform? Next step is that I add a readstreamFromString: method to grease, since I have to read my json from a string, and the seaside UI only allows me to read it from a stream. - The pharo implementation will be easy: “^aString readStream” - I guess I will need to add a basic stream to Gemstone that allows me to “stream” a string. If someone knows a better (easier) solution: let me know. Cheers, Diego

3 4

Jenkins build became unstable: Seaside » 20,bleedingEdge,vm #438
by ci-pharo-contribution＠inria.fr 25 Feb '14

25 Feb '14

See <https://ci.inria.fr/pharo-contribution/job/Seaside/PHARO=20,VERSION=bleedin…>

1 1

Jenkins build became unstable: Seaside » 30,bleedingEdge,vm #438
by ci-pharo-contribution＠inria.fr 25 Feb '14

25 Feb '14

See <https://ci.inria.fr/pharo-contribution/job/Seaside/PHARO=30,VERSION=bleedin…>

1 1

Grease repo on github
by Johan Brichau 23 Feb '14

23 Feb '14

Hi all, Over the past few weeks, I have set up a Grease repository in the GLASS Github account [1], with two purposes: - serve as the reference repository for Grease1.1 in Gemstone - run Travis CI for all platforms (currently: Pharo1.4, Pharo2.0, Pharo3.0, Gemstone2.4 and Gemstone3.1) It will mirror the code from the main Grease1.1 repository [2] in addition to serving the Gemstone-specific packages. In addition to the Pharo Contribution CI builds, this expands the automated testing to more platforms. All tests are green (at the moment), so I will start referencing it from the Seaside3.1 repository for Gemstone [3]. cheers, Johan [1] https://github.com/glassdb/Grease [2] http://www.smalltalkhub.com/#!/~Seaside/Grease11 [3] https://github.com/glassdb/Seaside31

1 0

Seaside Security
by Philippe Marschall 19 Feb '14

19 Feb '14

Hi Having had a few too many security reviews and secure coding events in the past we days I started working on a Seaside-Security package. The idea behind the package is that it contains things that you can add it to your application to make it more secure. It doesn't contain things that we can add by default because they have to be configured specifically for your application. Right now the plan is for it to contain two things: * filters that add additional headers (Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Strict-Transport-Security) * key generators for cryptographically secure session ids for Pharo/Squeak The filters would mean that the current WAStrictTransportSecurityFilter is moved from Seaside-Core to Seaside-Security and #iMeanIt is moved from Seaside-InternetExplorer to Seaside-Core. A limitation of the current WAStrictTransportSecurityFilter is that when reverse proxying it's hard to find out whether the original request was made with HTTPS or HTTP. AJP is the only adapter that I know of that finds this out reliably. Swazoo could find it out when not proxying but I don't know whether anybody uses this. CGI could in theory find it you but I don't know whether this is done currently. I don't know what the other platforms do but neither Pharo nor Squeak seem to ship a cryptographically secure PRNG. Therefore it's hard for Seaside to provide cryptographically secure session ids on these platforms so we don't do it (we could implement SHA1PRNG since we have SHA-1 on GRPlatform). We could in theory use OpenSSL RAND_bytes but the SqueakSSL plugin doesn't seem to provide access to it. This leaves us more or less with the Cryptography package [1]. It implements two cryptographically secure PRNGS: SHA1PRNG and Fortuna. I'm not super exited about this package. It's huge, contains failing tests and as far as I can tell you're somehow supposed to come up with a good seed on your own (we can just read from /dev/random on Unix but what do we do on Windows). If anybody knows of any better options please speak up. [1] http://smalltalkhub.com/#!/~Cryptography/Cryptography Cheers Philippe

4 8

Seaside-JSON-Core-DiegoLont.25
by Philippe Marschall 17 Feb '14

17 Feb '14

Hi I think this should render as a string otherwise we get invalid JSON. And tests would be nice, eg testDateAndTime self assert: [ :json | | date | date := DateAndTime year: 2007 month: 11 day: 21 hour: 14 minute: 42 second: 48 offset: (Duration days: 0 hours: 2 minutes: 0 seconds: 0). json array: [ json dateAndTime: date ] ] gives: '["2007-11-21T14:42:48+02:00"]' Cheers Philippe

2 1

GRCountingStream
by Johan Brichau 17 Feb '14

17 Feb '14

Hi, GRCountingStream is referenced by Seaside (in WAComboResponse) but it’s not included in the Grease-Core package (it’s in Grease-Pharo30-Core). I don’t see a reason not to include into Grease-Core. Or am I missing anything? I noticed this now while working on the Gemstone version and I would need to duplicate it otherwise in the Grease-GemStone-Core package. Ok if I move it? Johan

2 7

Build failed in Jenkins: Seaside » 20,stable,vm #432
by ci-pharo-contribution＠inria.fr 17 Feb '14

17 Feb '14

See <https://ci.inria.fr/pharo-contribution/job/Seaside/PHARO=20,VERSION=stable,…> ------------------------------------------ Started by upstream project "Seaside" build number 432 originally caused by: Started by upstream project "Grease" build number 332 originally caused by: [URLTrigger] A change within the response URL invocation (log) Building remotely on pharo-contribution-linux64-3.ci.inria.fr in workspace <https://ci.inria.fr/pharo-contribution/job/Seaside/PHARO=20,VERSION=stable,…> Deleting project workspace... Deleting old artifacts from #430 [vm] $ /bin/sh -xe /tmp/hudson6861678580217387126.sh + dirname Seaside/PHARO=20,VERSION=stable,VM=vm + export JOB_NAME=Seaside + bash + wget --quiet -O - get.pharo.org/20+vm Downloading the latest 20 Image: http://files.pharo.org/image/20/latest.zip Pharo.image Downloading the latest pharoVM: http://files.pharo.org/vm/pharo/linux/stable.zip pharo-vm/pharo Downloading PharoV10.sources: http://files.pharo.org/sources//PharoV10.sources.zip Downloading PharoV20.sources: http://files.pharo.org/sources//PharoV20.sources.zip Creating starter scripts pharo and pharo-ui + ./pharo Pharo.image save Seaside --delete-old + ./pharo Seaside.image --version + REPO=http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main + ./pharo Seaside.image config http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main ConfigurationOfSeaside3 --install=stable --group=CI [31m[33m =============================================================================== Notice: Installing ConfigurationOfSeaside3 stable =============================================================================== [0m[0m[31m==== Startup Error: An attempt to use interactive tools detected, while in non-interactive mode Interactive Request: You are about to load new versions of the following packages that have unsaved changes in the image: Grease-Pharo20-Core If you continue, you will lose these changes: [0mNonInteractiveUIManager>>nonInteractiveWarning: NonInteractiveUIManager>>nonInteractiveRequest:title: NonInteractiveUIManager>>nonInteractiveRequest: NonInteractiveUIManager>>confirm:trueChoice:falseChoice:cancelChoice:default: MCMergeOrLoadWarning>>defaultAction UndefinedObject>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: [0m[31mGot startup errors: [0m[31m An attempt to use interactive tools detected, while in non-interactive mode Interactive Request: You are about to load new versions of the following packages that have unsaved changes in the image: Grease-Pharo20-Core If you continue, you will lose these changes: [0mBuild step 'Execute shell' marked build as failure Archiving artifacts Recording test results

1 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

seaside-dev February 2014