Reporting Issues
View active issues, report bugs and contribute feature requests through our issues tracking system. Alternatively we also accept bug reports or feature requests through the mailing-list.
Recent Updates
- Update 4 to issue 754 ("#asJson produces strings with non-valid escape sequences "\0", "\a" and "\x.."") 2013-05-05T12:11:34+00:00Name: Javascript-Core-pmm.94 Author: pmm Time: 5 May 2013, 2:10:23 pm UUID: ff734fea-ca0d-468c-86c4-dbb39484e092 Ancestors: Javascript-Core-pmm.93 - Issue 754: #asJson produces strings with non-valid escape sequences "\0", "\a" and "\x.." - http://code.google.com/p/seaside/issues/detail?id=754 Name: Javascript-Tests-Core-pmm.68 Author: pmm Time: 5 May 2013, 2:11:16 pm UUID: 7d3c76d4-f8be-4474-972d-162c0b68b0c6 Ancestors: Javascript-Tests-Core-pmm.67 - Issue 754: #asJson produces strings with non-valid escape sequences "\0", "\a" and "\x.." - http://code.google.com/p/seaside/issues/detail?id=754 Status: Fixed
- Update 2 to issue 751 ("WAAccept>>fromString: assumes the only parameter to a media-range is 'q'") 2013-05-03T08:37:00+00:00Ok, level used to be a strange feature of the HTML mime type. http://www.ietf.org/rfc/rfc2854.txt Status: FixedLabels: Version-Seaside3.1
- Update 3 to issue 754 ("#asJson produces strings with non-valid escape sequences "\0", "\a" and "\x.."") 2013-05-02T07:41:10+00:00Kris (who reported this issue) made a change in our code base that should fix it. I attach his changes.
- Update 1 to issue 751 ("WAAccept>>fromString: assumes the only parameter to a media-range is 'q'") 2013-05-01T19:08:07+00:00So I fixed the parser. I'm not entirely sure whether I should take the level into account for sorting in WAQualifiedValue #<= and WASortedAccepts. The RFC doesn't seem very clear on this or maybe I just don't see it. Name: Seaside-Core-pmm.787 Author: pmm Time: 1 May 2013, 9:03:31 pm UUID: ee5988b7-9bbe-4f17-a400-43be93656009 Ancestors: Seaside-Core-pmm.786 - Issue 751: WAAccept>>fromString: assumes the only parameter to a media-range is 'q' - http://code.google.com/p/seaside/issues/detail?id=751 Name: Seaside-Tests-Core-pmm.264 Author: pmm Time: 1 May 2013, 9:04:01 pm UUID: b467320e-bd56-43f3-9023-dda2e640c6c9 Ancestors: Seaside-Tests-Core-pmm.263 - Issue 751: WAAccept>>fromString: assumes the only parameter to a media-range is 'q' - http://code.google.com/p/seaside/issues/detail?id=751 Status: StartedOwner: philippe...@gmail.com
- Update 2 to issue 755 ("JSJsonParser removes whitespace at the start of string literals") 2013-05-01T13:54:15+00:00Status: Fixed
- Update 1 to issue 755 ("JSJsonParser removes whitespace at the start of string literals") 2013-05-01T13:54:05+00:00Name: Javascript-Core-pmm.93 Author: pmm Time: 1 May 2013, 3:51:21 pm UUID: 06c73902-c962-40c6-ac7a-bc9f578ac968 Ancestors: Javascript-Core-pmm.92 - Issue 755: JSJsonParser removes whitespace at the start of string literals - http://code.google.com/p/seaside/issues/detail?id=755 Name: Javascript-Tests-Core-pmm.67 Author: pmm Time: 1 May 2013, 3:51:53 pm UUID: 723cca46-c12c-4d51-8f0c-d8ab46b5b8e9 Ancestors: Javascript-Tests-Core-pmm.66 - Issue 755: JSJsonParser removes whitespace at the start of string literals - http://code.google.com/p/seaside/issues/detail?id=755 Name: Seaside-JSON-Core-pmm.20 Author: pmm Time: 1 May 2013, 3:53:03 pm UUID: f43110b1-b9b8-4054-a10f-d8389899e18c Ancestors: Seaside-JSON-Core-pmm.19 - Issue 755: JSJsonParser removes whitespace at the start of string literals - http://code.google.com/p/seaside/issues/detail?id=755 Name: Seaside-Tests-JSON-pmm.11 Author: pmm Time: 1 May 2013, 3:53:39 pm UUID: e5acc266-d020-48a0-be13-7f7483b0f38b Ancestors: Seaside-Tests-JSON-pmm.10 - Issue 755: JSJsonParser removes whitespace at the start of string literals - http://code.google.com/p/seaside/issues/detail?id=755 Owner: philippe...@gmail.comLabels: JSON
- Update 2 to issue 754 ("#asJson produces strings with non-valid escape sequences "\0", "\a" and "\x.."") 2013-05-01T13:17:49+00:00This is one of the cases where the way JSON works in Seaside 3.0 bytes us. In Seaside 3.0 JSON support is build on top of JavaScript. At first it seems like an easy way to implement because they are quite similar. However there are quite some differences (eg. JSON is not actually a subset of JavaScript, see U+2028 and U+2029). In Seaside 3.1 this was really easy to fix because JSON support is different. If we want to fix this in 3.0 we have to change JSStream class >> #initializeEncoding to the same as WAJsonEncoder class >> #initializeEncoding. This would impact all of the JavaScript we generate. Name: Seaside-JSON-Core-pmm.19 Author: pmm Time: 1 May 2013, 3:08:04 pm UUID: 15b6dae1-ec2f-4769-a255-d18e963d3ee6 Ancestors: Seaside-JSON-Core-jf.18 Issue 754: #asJson produces strings with non-valid escape sequences "\0", "\a" and "\x.." Name: Seaside-Tests-JSON-pmm.10 Author: pmm Time: 1 May 2013, 3:08:36 pm UUID: bd24bff3-ace7-48f5-a586-844695caf65b Ancestors: Seaside-Tests-JSON-jf.9 Issue 754: #asJson produces strings with non-valid escape sequences "\0", "\a" and "\x.." Status: StartedOwner: philippe...@gmail.com
- Update 1 to issue 754 ("#asJson produces strings with non-valid escape sequences "\0", "\a" and "\x.."") 2013-05-01T13:07:51+00:00Summary: #asJson produces strings with non-valid escape sequences "\0", "\a" and "\x.."Status: AcceptedLabels: JSON
- Issue 755 created: "JSJsonParser removes whitespace at the start of string literals" 2013-04-24T15:01:57+00:00The following example (in Seaside 3.0.7.1) returns an empty string rather than one with a space character: JSJsonParser parse: (String with: $" with: Character space with: $"). This seems to be due to the use of #expect: at the start of #parseString, the former uses #match: which in turn uses #whitespace to strip whitespace before returning.
- Issue 754 created: "#asJSON produces strings with non-valid escape sequences "\0", "\a" and "\x.."" 2013-04-24T14:31:42+00:00The following three examples all raise a JSJsonSyntaxError (in Seaside 3.0.7.1): JSJsonParser parse: (String with: (Character codePoint: 16r00)) asJson. "Uses escape sequence: \0" JSJsonParser parse: (String with: (Character codePoint: 16r07)) asJson. "Uses escape sequence: \a" JSJsonParser parse: (String with: (Character codePoint: 16r1F)) asJson. "Uses escape sequence: \x1f" I think #asJson is to blame rather than JSJsonParser. The escape sequences "\0", "\a" and "\x.." are not mentioned in section 2.5 "Strings" of RFC4627 ( http://tools.ietf.org/html/rfc4627#section-2.5 ). The "\u...." escape sequence should be used instead.
- Update 1 to issue 753 ("Watch G.I. Joe: Retaliation Online Stream") 2013-04-15T16:26:07+00:00I know where to find torrents Status: Invalid
- Update 1 to issue 752 ("Watch The Lords of Salem Online Stream") 2013-04-15T16:25:24+00:00I know where to find torrents Status: Invalid
- Issue 753 created: "Watch G.I. Joe: Retaliation Online Stream" 2013-04-15T11:57:57+00:00<P>http://galih.org/plays/stream-in-hd-now.php?movie=1583421 Watch G.I. Joe: Retaliation Online Watch G.I. Joe: Retaliation Online Watch G.I. Joe: Retaliation Online Watch G.I. Joe: Retaliation Online Watch G.I. Joe: Retaliation Online Watch G.I. Joe: Retaliation Online Watch G.I. Joe: Retaliation Online Watch G.I. Joe: Retaliation Online Watch G.I. Joe: Retaliation Online Watch G.I. Joe: Retaliation Online Watch G.I. Joe: Retaliation Online Watch G.I. Joe: Retaliation Online Watch G.I. Joe: Retaliation Online Watch G.I. Joe: Retaliation Online Watch G.I. Joe: Retaliation Online Watch G.I. Joe: Retaliation Online Watch G.I. Joe: Retaliation Online Watch G.I. Joe: Retaliation Online Watch G.I. Joe: Retaliation Online Watch G.I. Joe: Retaliation Online http://galih.org/plays/stream-in-hd-now.php?movie=1583421 Edit Storyline Framed for crimes against the country, the G.I. Joe team is terminated by the President's order, and the surviving team members face off against Zartan, his accomplices, and the world leaders he has under his influence. Written by Anonymous Plot Summary | Plot Synopsis Plot Keywords: Gi Joe | President | Self Destruction | Video Game | Mexican Standoff |See more Genres: Action| Adventure| Sci-Fi| Thriller Motion Picture Rating (MPAA) Rated PG-13 for intense sequences of combat violence and martial arts action throughout, and for brief sensuality and language | See all certifications Parents Guide: View content advisory The G.I. Joes are not only fighting their mortal enemy Cobra; they are forced to contend with threats from within the government that jeopardize their very existence. Edit Cast Cast overview, first billed only: Dwayne Johnson ... Roadblock Jonathan Pryce ... President Byung-hun Lee ... Storm Shadow Elodie Yung ... Jinx Ray Stevenson ... Firefly D.J. Cotrona ... Flint Adrianne Palicki ... Jaye Channing Tatum ... Duke Ray Park ... Snake Eyes Luke Bracey ... Cobra Commander Walton Goggins ... Warden Nigel James Arnold Vosloo ... Zartan Joseph Mazzello ... Mouse Nick Erickson ... President Picture Double RZA ... Blind Master Full cast and crew </P>
- Issue 752 created: "Watch The Lords of Salem Online Stream" 2013-04-15T11:15:04+00:00<P>http://galih.org/plays/stream-in-hd-now.php?movie=1731697 Watch The Lords of Salem Online Watch The Lords of Salem Online Watch The Lords of Salem Online Watch The Lords of Salem Online Watch The Lords of Salem Online Watch The Lords of Salem Online Watch The Lords of Salem Online Watch The Lords of Salem Online Watch The Lords of Salem Online Watch The Lords of Salem Online Watch The Lords of Salem Online Watch The Lords of Salem Online Watch The Lords of Salem Online Watch The Lords of Salem Online Watch The Lords of Salem Online Watch The Lords of Salem Online Watch The Lords of Salem Online Watch The Lords of Salem Online Watch The Lords of Salem Online Watch The Lords of Salem Online http://galih.org/plays/stream-in-hd-now.php?movie=1731697 Edit Storyline Heidi, a blond rock chick, DJs at a local radio station, and together with the two Hermans (Whitey and Munster) forms part of the "Big H Radio Team." A mysterious wooden box containing a vinyl record arrives for Heidi, a gift of the Lords. She assumes it's a rock band on a mission to spread their word. As Heidi and Whitey play the Lords' record, it starts to play backwards, and Heidi experiences a flashback to a past trauma. Later, Whitey plays the Lords' record, dubbing them the Lords of Salem, and to his surprise, the record plays normally and is a massive hit with his listeners. The arrival of another wooden box from the Lords presents the Big H team with free tickets, posters and records to host a gig in Salem. Soon, Heidi and her cohorts are far from the rock spectacle they're expecting. The original Lords of Salem are returning and they're out for blood. Written by UHM Plot Summary | Add Synopsis Plot Keywords: Salem Massachusetts | City Name In Title | Place Name In Title Taglines: The Lords Are Coming See more Genres: Horror| Thriller Motion Picture Rating (MPAA) Rated R for disturbing violent and sexual content, graphic nudity, language and some drug use | See all certifications Parents Guide: View content advisory Heidi, a radio DJ, is sent a box containing a record -- a "gift from the Lords." The sounds within the grooves trigger flashbacks of her town's violent past. Is Heidi going mad, or are the Lords back to take revenge on Salem, Massachusetts? Edit Cast Cast overview, first billed only: Sheri Moon Zombie ... Heidi Hawthorne Bruce Davison ... Francis Matthias Jeff Daniel Phillips ... Herman 'Whitey' Salvador (as Jeffrey Daniel Phillips) Judy Geeson ... Lacy Doyle Meg Foster ... Margaret Morgan Patricia Quinn ... Megan Ken Foree ... Herman Jackson Dee Wallace ... Sonny Maria Conchita Alonso ... Alice Matthias Richard Fancy ... AJ Kennedy Andrew Prine ... Reverend Jonathan Hawthorne Michael Berryman ... Virgil Magnus Sid Haig ... Dean Magnus Bonita Friedericy ... Abigail Hennessey Nancy Linehan Charles ... Clovis Hales Full cast and crew </P>
- Issue 751 created: "WAAccept>>fromString: assumes the only parameter to a media-range is 'q'" 2013-04-12T08:54:23+00:00Section 14.1 in RFC 2616 ( http://tools.ietf.org/html/rfc2616#section-14.1 ) explicitly gives the following example of an accept header: Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1, text/html;level=2;q=0.4, */*;q=0.5 In Seaside 3.0.7.1, WAAccept>>fromString: does not read the parameters correctly: x := (WAAccept fromString: 'text/*;q=0.3, text/html;q=0.7, text/html;level=1, text/html;level=2;q=0.4, */*;q=0.5'). x fourth quality. "Returns 2.0 rather than 0.4 as expected." x fourth value parameters. "Returns an empty dictionary rather than one mapping 'level' to 2 as expected."
- Update 9 to issue 749 ("Wrong handling of urls encoded in UTF8") 2013-03-30T16:44:08+00:00Status: StartedOwner: philippe...@gmail.com
- Update 1 to issue 750 ("IRC channel on Cincom server is inexistant") 2013-03-24T14:17:01+00:00Removed it Status: FixedLabels: -Type-Defect -Priority-Medium Type-CleanUp Priority-Low Website
- Issue 750 created: "IRC channel on Cincom server is inexistant" 2013-03-22T13:09:31+00:00The website states #seaside on irc.parcplace.net This is the IRC sever provided by Cincom. This should be your channel of choice for Cincom related questions. But the channel is absent.
- Update 2 to issue 402 ("Cleanup Website") 2013-03-20T01:13:38+00:00Would love to see updated instructions on how to get started with Seaside on Pharo2
- Update 8 to issue 749 ("Wrong handling of urls encoded in UTF8") 2013-03-13T20:09:27+00:00Here is a quick patch/hack to get a proper not found showing the encoded URL WAUrl>>pathString "Answer the path converted to a string." ^ String streamContents: [ :stream | | document | document := WAHtmlDocument on: stream codec: (GRCodec forEncoding: 'utf-8'). self encodePathOn: document ]