Marek Parfianowicz added a comment - 08/Jul/2024 1:29 PM Atlassian Update – 8 July 2024 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Not Being Considered . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Fisheye&Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Implementation of New Features Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Kind regards Marek Parfianowicz Principal Engineer

David Mason added a comment - 30/Apr/2021 3:16 PM Supplying a directory for spool files was found to be an apparent solution to the problem of Fisheye getting stuck "expanding paths for revision X", while experiencing repeated connection resets: svn: E175002: Connection reset when using the http: protocol. This did not happen using file:/// or svn://