454101 - "Not enough arguments [nsIMsgFolder.createSubfolder]" selecting search folder of rss feeds

Status: RESOLVED FIXED

(MailNews Core :: Feed Reader, defect)

Description

[Bob Clary [:bc] (inactive)]

1. Subscribe to several RSS feeds.
2. Create a saved search folder for items < 8 days that searches each of the RSS feeds.
3. Select saved search folder

Expected results: display items in the folder.

Actual results: nothing displays

Error: [Exception... "Not enough arguments [nsIMsgFolder.createSubfolder]"  nsresult: "0x80570001 (NS_ERROR_XPC_NOT_ENOUGH_ARGS)"  location: "JS frame :: file:///Users/bclary/Desktop/Shredder.app/Contents/MacOS/components/folderLookupService.js :: fls_getFolderById :: line 73"  data: no]
Source File: file:///Users/bclary/Desktop/Shredder.app/Contents/MacOS/components/folderLookupService.js
Line: 73

...

regressed in the 2008-09-06-03 trunk build.

Comment 1

[Bob Clary [:bc] (inactive)]

http://hg.mozilla.org/comm-central/rev/b5776223fe06 looks like a good candidate. 

Note this is not a problem with saved searches of other types such as local or news folders.

Comment 2

[Joey Minta]

Fix is in bug 453908, but I can factor it out if necessary. See https://bugzilla.mozilla.org/attachment.cgi?id=337285&action=diff#a/mailnews/base/src/folderLookupService.js_sec1

Comment 3

[Bob Clary [:bc] (inactive)]

Joey, I can live with it until its fixed. One correction is that it appears not only with saved searches of RSS feeds but also saved searches that search across imap accounts. It doesn't appear for saved searches of local folders though. I'll apply the patch and see if it fixes everything for me.

Comment 4

[Mark Banner (:standard8)]

Bob, bug 441437 has been backed out, do you still see this in today's nightly?

Comment 5

[Bob Clary [:bc] (inactive)]

Mark, nope. Works for me in today's build. Shall we close this one out?

Comment 6

[Mark Banner (:standard8)]

(In reply to comment #5)
> Mark, nope. Works for me in today's build. Shall we close this one out?

Yes I think so, given where the bug appeared to be and what seems to have fixed it.

Therefore fixed by the backout of bug 441437, see bug 441437 comment 16.