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

• Issue 596 created: "uptime reporting on /status may be wrong" 2010-08-24T17:19:10+00:00
  Hi, The following code is not good enough (Seaside 3): WAImageStatus>>#renderValuesOn: html | image upTime | image := SmalltalkImage current. upTime := Duration milliseconds: Time millisecondClockValue. self renderLabel: 'Uptime' value: (self printDuration: upTime) on: html. ... The uptime wraps around on long running images, and since all Seaside applications have enormeous uptimes, it is a pity that this is not reported correctly. I have a fix by registering the class with the image startUpList, setting the startUpTime in a class variable. Sven 3. What is the expected output? What do you see instead? Please use labels and text to provide additional information.
• Update 5 to issue 554 ("WABuilder>>codec should try WACurrentRequestContext first before using GRNullCodec") 2010-08-24T17:13:31+00:00
  Name: Seaside-Core-pmm.659 Author: pmm Time: 24 August 2010, 7:11:56 pm UUID: ea1f27af-fe84-4b41-b751-25b68d1c5b75 Ancestors: Seaside-Core-lr.658 - Issue 554: WABuilder>>codec should try WACurrentRequestContext first before using GRNullCodec - refactor the #perform: out of it so that the file library is responsible for returning the size of a file - http://code.google.com/p/seaside/issues/detail?id=554 Name: Seaside-Environment-pmm.71 Author: pmm Time: 24 August 2010, 7:12:51 pm UUID: 61de3f45-2c6a-4c24-9981-2e5b21c3af29 Ancestors: Seaside-Environment-jf.70 - Issue 554: WABuilder>>codec should try WACurrentRequestContext first before using GRNullCodec - refactor the #perform: out of it so that the file library is responsible for returning the size of a file - http://code.google.com/p/seaside/issues/detail?id=554 Status: FixedLabels: Version-Seaside3.0
• Update 4 to issue 554 ("WABuilder>>codec should try WACurrentRequestContext first before using GRNullCodec") 2010-08-24T16:49:32+00:00
  Looking again at the code I think falling back to the context instead of always having to pass in is better because you don't have to update a lot of cases and will actually do the right thing in most cases. Status: StartedOwner: philippe.marschallLabels: -Type-Defect -Priority-Medium Type-Other Priority-Low
• Update 3 to issue 511 ("WASwazooAdaptor fails WAUploadFunctionalTest and WAEncodingFuntionalTest") 2010-08-24T05:03:12+00:00
  The remaining problem was only the character by character rendering (#renderCharacterByCharacter:on:). This is expected to break for the NullCodec and a multi byte encoding like utf-8 because in this case it degrades to a byte by byte rendering. So it looks like this has been fixed some time ago. Anyway I disabled the character by character rendering test for the NullCodec because IMHO they don't make sense in this case. Name: Seaside-Tests-Functional-pmm.124 Author: pmm Time: 24 August 2010, 6:58:45 am UUID: 2dee6780-ab7f-41d9-b86d-a98b682b0a07 Ancestors: Seaside-Tests-Functional-lr.123 - don't test character by character rendering for null codec Status: FixedOwner: philippe.marschall
• Update 2 to issue 511 ("WASwazooAdaptor fails WAUploadFunctionalTest and WAEncodingFuntionalTest") 2010-08-23T04:59:05+00:00
  The current state of affairs is only fails well to set the codec to (none) and configure the application to use utf-8. Otherwise it works. Labels: -Priority-Medium Priority-Low
• Update 2 to issue 451 ("generated canvas documentation") 2010-08-23T04:43:39+00:00
  http://seafox.seasidehosting.st/ ?
• Update 1 to issue 354 ("WACheckboxTag callbacks holding onto the tag") 2010-08-23T04:40:52+00:00
  The same is now true for WAMultiSelectTag
• Update 2 to issue 595 ("Deselection from a multi selection field does not work") 2010-08-22T14:27:41+00:00
  Name: Seaside-Canvas-lr.98 Author: lr Time: 22 August 2010, 4:26:51 pm UUID: 741501a0-71fc-4fa1-bc0c-9bdb9ac96f18 Ancestors: Seaside-Canvas-lr.97 - fixes "Issue 595: Deselection from a multi selection field does not work" Name: Seaside-Tests-Canvas-lr.50 Author: lr Time: 22 August 2010, 4:27:08 pm UUID: 40236d87-2afa-4ebc-9bb0-f4e492be0a91 Ancestors: Seaside-Tests-Canvas-pmm.49 - fixes "Issue 595: Deselection from a multi selection field does not work" Status: FixedOwner: renggli
• Update 1 to issue 595 ("Deselection from a multi selection field does not work") 2010-08-22T12:27:21+00:00
  Looks like the same issue with the checkbox. If nothing is selected the browser just omits the field. We'll probably have to do a similar hack.
• Issue 595 created: "Deselection from a multi selection field does not work" 2010-08-22T11:37:29+00:00
  What steps will reproduce the problem? 1. Got to WAInputGetFunctionalTest, WAInputPostFunctionalTest or WAInputPostMultipartFunctionalTest 2. Select "Haskell" 3. Hit Submit 4. Deselect "Haskell" 5. Hit Submit What is the expected output? Nothing is selected. What do you see instead? Haskell" is selected. This is at least with Comanche.
• Update 5 to issue 591 ("WAComboResponse - a combined buffered / streaming response") 2010-08-21T18:52:14+00:00
  I am voting for a solution to this, because I am troubled that I can (and have got) get a walkback in my image due to Socket>>waitForDataFor: which raises an exception. I would like to see some solution to prevent this - at the very least I shouldn't get an a debugger - and just something in a log file.
• Update 2 to issue 547 ("replace #asSortedCollection with #sorted:") 2010-08-19T20:52:18+00:00
  I guess. :) Status: Fixed
• Update 6 to issue 474 ("Using Halos - CSS Style Editor to update CSS of a component breaks versions view with 'subscript is out of bounds: x'.") 2010-08-19T20:38:13+00:00
  I reviewed, but I have no clue. :)
• Update 2 to issue 568 ("Email sending abstraction for Pharo not deployable (3.0a5)") 2010-08-16T12:01:40+00:00
  Shouldn't that be upstream? Pharo 2813
• Update 1 to issue 568 ("Email sending abstraction for Pharo not deployable (3.0a5)") 2010-08-16T11:06:52+00:00
  Since this is a Pharo/Squeak issue, can we set this WontFix?
• Update 2 to issue 570 ("iso-8859-1 doesn't show up in the encoding list of the server adapter") 2010-08-16T11:03:03+00:00
  Name: Grease-Pharo-Core-pmm.26 Author: pmm Time: 16 August 2010, 12:54:25 pm UUID: d9f7eda2-9872-4ee7-984f-bf022648aba8 Ancestors: Grease-Pharo-Core-pmm.25 - Issue 570: iso-8859-1 doesn't show up in the encoding list of the server adapter - http://code.google.com/p/seaside/issues/detail?id=570 Name: Grease-Tests-Pharo-Core-pmm.8 Author: pmm Time: 16 August 2010, 12:58:10 pm UUID: 7bb03449-cc68-4546-afb5-bdd2af40438f Ancestors: Grease-Tests-Pharo-Core-jok.7 - Issue 570: iso-8859-1 doesn't show up in the encoding list of the server adapter - http://code.google.com/p/seaside/issues/detail?id=570 Name: Seaside-Tests-Pharo-Core-pmm.14 Author: pmm Time: 16 August 2010, 1:00:58 pm UUID: 82e88c68-45f8-495e-bade-e01bcc700e99 Ancestors: Seaside-Tests-Pharo-Core-pmm.13 - Issue 570: iso-8859-1 doesn't show up in the encoding list of the server adapter - http://code.google.com/p/seaside/issues/detail?id=570 Status: FixedLabels: Version-Seaside3.0
• Update 6 to issue 9 ("Add switch to WAFileLibrary such that #/ also generates static paths") 2010-08-16T07:00:50+00:00
  Summary: Add switch to WAFileLibrary such that #/ also generates static paths
• Update 7 to issue 525 ("WALegacyRedirectionHandler loses url parameters during redirection") 2010-08-16T06:43:39+00:00
  Can no longer reproduce. The filter keeps the parameters in the browser. I wrote a unit test and it works as well. Reopen with more specific steps to reproduce if not fixed. Name: Seaside-Tests-Environment-pmm.24 Author: pmm Time: 16 August 2010, 8:41:11 am UUID: f62b95bc-49c2-4c35-a96e-3e2b91d63c5f Ancestors: Seaside-Tests-Environment-lr.23 - regression test - Issue 525: WALegacyRedirectionHandler loses url parameters during redirection - http://code.google.com/p/seaside/issues/detail?id=525 Status: FixedLabels: -Platform-Pharo
• Update 1 to issue 570 ("iso-8859-1 doesn't show up in the encoding list of the server adapter") 2010-08-15T22:52:59+00:00
  Status: Started
• Update 1 to issue 547 ("replace #asSortedCollection with #sorted:") 2010-08-15T22:14:37+00:00
  I can't find a sender of #asSortedCollection, can we close this?