By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 1131 - kate - opening project with remote files should not create a connection dialog for each file
Summary: kate - opening project with remote files should not create a connection dialo...
Status: CONFIRMED
Alias: None
Product: TDE
Classification: Unclassified
Component: tdebase (show other bugs)
Version: R14.0.x [Trinity]
Hardware: All Linux
: P5 normal
Assignee: Calvin Morrison
URL:
Depends on:
Blocks:
 
Reported: 2012-07-28 10:09 CDT by David C. Rankin
Modified: 2018-05-27 11:00 CDT (History)
3 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David C. Rankin 2012-07-28 10:09:12 CDT
Bug,

  When opening multiple files in kate via fish:// or sftp://, kate displays a 'connection' dialog for each remote 'file' opened. When opening a project with 100 files, this causes kate to flood the screen with individual asynchronous connection windows for each and every 'file'. (literally the screen is filled with failed connection dialogs) This exhausts connection resources causing file opening to fail. (generally starting at about file 80) This leaves the screen covered with failed connection dialogs that must be individually canceled in order to get back to the first connection dialog that failed (and is hung). You must then go through each file in the kate document list named 'untitled' and perform a refresh (F5) to load the file contents and update the filename in kate.

How it should work:

  When opening the same project locally, kate displays a single dialog that shows the progress of opening files as they are sequentially opened. The open of remote files should work exactly the same way. A single dialog that displays a progress meter for files opened (what ever it does for local files, it should do for files opened via fish or sftp) The opening should be sequential as well. Attempting to open multiple files asynchronously from a single remote location saves NO time or bandwidth. Just read them one at a time. 

The super-duper solution - kate could open one connection per remote site if project files spanned multiple sites. This would preserve the load time advantage of creating multiple connections to different remote sites, but the transfers from each remote site should still be sequential and through a single per-remote-location connection dialog. (I think this is overkill where source files are generally less than 50k (most times less than 5k).
Comment 1 Calvin Morrison 2012-12-03 19:43:21 CST
is this a kate issue or a KIO problem?
Comment 2 Darrell 2012-12-03 19:52:20 CST
> is this a kate issue or a KIO problem?

David has not been on the dev list for several months. I wish he was. :( Possibly try to contact him personally.

I can try to duplicate this using my web site. I haven't used fish in a long time so might take me a while to test.
Comment 3 Darrell 2013-05-09 17:52:58 CDT
I tested this with fish and a virtual machine. Attempting to open many files does indeed result in multiple dialogs and kate stalling.

The same thing happens when opening multiple files with kwrite through fish.

Opening the same batch of files with kedit through fish does not result in a stall.

I am using the latest GIT as of 2013-05-09.