Eleanor, could your patch for bug 1969363 be responsible for this (comment 16 has great str)? It looks like after the FolderPopulation refactor landed in 143, folder discovery basil on the first child error (for example when a Windows MAX_PATH limit is hit) instead of continuing, so other folders or siblings disappear from the tree. nsMsgDBFolder::AddSubfolder doesn’t append to mSubFolders when CreateFolderAndCache returns NS_MSG_FOLDER_EXISTS, even though it returns a valid folder. Do you think switching PopulateFolderHierarchy to “log & continue” on errors, and always appending when we have a valid folder pointer, would restore the 142 behavior?
Bug 1990571 Comment 25 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Eleanor, could your patch for bug 1969363 be responsible for this (comment 16 has great str)? It looks like after the FolderPopulation refactor landed in 143, folder discovery bails on the first child error (for example when a Windows MAX_PATH limit is hit) instead of continuing, so other folders or siblings disappear from the tree. nsMsgDBFolder::AddSubfolder doesn’t append to mSubFolders when CreateFolderAndCache returns NS_MSG_FOLDER_EXISTS, even though it returns a valid folder. Do you think switching PopulateFolderHierarchy to “log & continue” on errors, and always appending when we have a valid folder pointer, would restore the 142 behavior?