25 comments
Comment actions Permalink

Here I thought you were going to say background SVN/CVS Update/Commit, a feature which bestrides the cosmos, searing unsuspecting eyeballs with the blinding radiance of its manifest coolness.

Plus, hey, color-coded source roots in the project panel!

--Dave Griffith

0
Comment actions Permalink

You're right, the background SVN/CVS is truly a pants soiling feature. Now where's that spare pair I set aside months ago for just this kind of eventuality....

0
Comment actions Permalink

It would be good... if it worked :( The first time I tried it I got "50%
Update Directory: Login" in the status bar for a while, and was unable to
do anything in the editor until the update finished. The second time I tried,
IDEA displayed the same thing in the status bar and then hung solid (the
cursor stays fixed as the "I-bar", and nothing I click on does anything,
including the big square red stop button in the status bar).

Anyone else seeing this behaviour?

You're right, the background SVN/CVS is truly a pants soiling feature.
Now where's that spare pair I set aside months ago for just this kind
of eventuality....



0
Comment actions Permalink

Ditto. I'm bailing on this build.

0
Comment actions Permalink

Hello Chris,

What version control you're using?
Can I please have a thread dump, while UI is frozen?

-


Maxim Shafirov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

It would be good... if it worked :( The first time I tried it I got
"50%
Update Directory: Login" in the status bar for a while, and was
unable to
do anything in the editor until the update finished. The second time I
tried,
IDEA displayed the same thing in the status bar and then hung solid
(the cursor stays fixed as the "I-bar", and nothing I click on does
anything, including the big square red stop button in the status bar).

Anyone else seeing this behaviour?

>> You're right, the background SVN/CVS is truly a pants soiling
>> feature. Now where's that spare pair I set aside months ago for just
>> this kind of eventuality....
>>


0
Comment actions Permalink

i'm using CVS over SSH

0
Comment actions Permalink

Hi Maxim,

I'm not quite understand about updating/committing in background. When it will happen? After I save any files? After an interval time? Do I have an option to turn it off if I want? If it happens after an interval time, can I change value for it?

Thanks

0
Comment actions Permalink

Hello Chris,

CM> It would be good... if it worked :( The first time I tried it I got "50%
CM> Update Directory: Login" in the status bar for a while, and was unable to
CM> do anything in the editor until the update finished. The second time
I tried,
CM> IDEA displayed the same thing in the status bar and then hung solid
CM> (the cursor stays fixed as the "I-bar", and nothing I click on does
CM> anything, including the big square red stop button in the status
CM> bar).
CM>
CM> Anyone else seeing this behaviour?

Are you using CVS? There is a known problem with CVS which can result in
similar behavior, and which will be fixed in the next EAP.

--
Dmitry Jemerov
Software Developer
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

Hello t800t8,

t> I'm not quite understand about updating/committing in background.
t> When it will happen? After I save any files? After an interval time?
t> Do I have an option to turn it off if I want? If it happens after an
t> interval time, can I change value for it?

It doesn't happen automatically. You invoke the actions in the regular way,
and they don't block the UI while they run.

--
Dmitry Jemerov
Software Developer
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

I'm using CVS. A thread dump is attached.

Hello Chris,

>

What version control you're using?
Can I please have a thread dump, while UI is frozen?
------------------
Maxim Shafirov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"



Attachment(s):
cvs-hang.txt
0
Comment actions Permalink

Hello Chris,

Yep, that's fixed, thank.

-


Maxim Shafirov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

I'm using CVS. A thread dump is attached.

>> Hello Chris,
>>
>> What version control you're using?
>> Can I please have a thread dump, while UI is frozen?
>> -


>> Maxim Shafirov
>> JetBrains, Inc
>> http://www.jetbrains.com
>> "Develop with pleasure!"


0
Comment actions Permalink

What's the deal with background commit? What happens if I start editing
a file that's in the commit queue, will my changes be committed or not?
Does it depend on whether or not they're saved before the file reaches
the head of the queue? That would be ... not cool.
R

0
Comment actions Permalink

Hello Robert,

RG> What's the deal with background commit? What happens if I start editing
RG> a file that's in the commit queue, will my changes be committed or not?
RG> Does it depend on whether or not they're saved before the file reaches
RG> the head of the queue? That would be ... not cool.

Right now there is no special handling for this situation, so "not cool"
it is. We'll discuss what can be done about this in the final release.

It looks like the solution that will work most reliably for all VCSes is
to forbid editing of files which are being committed while the commit is
in progress.

--
Dmitry Jemerov
Software Developer
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

Dmitry Jemerov wrote:

It looks like the solution that will work most reliably for all VCSes is
to forbid editing of files which are being committed while the commit is
in progress.


Can't you make a labeled snapshot in the local VCS and then commit that
snapshot?

0
Comment actions Permalink

Hello Jonas,

>> It looks like the solution that will work most reliably for all VCSes
>> is to forbid editing of files which are being committed while the
>> commit is in progress.
>>
JK> Can't you make a labeled snapshot in the local VCS and then commit
JK> that snapshot?

The integrations which work by running external executables (Perforce and
SourceSafe) require actual real files to be on disk in order to perform the
commit.

--
Dmitry Jemerov
Software Developer
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

Hello Dmitry,

DJ> The integrations which work by running external executables
DJ> (Perforce and SourceSafe) require actual real files to be on disk in
DJ> order to perform the commit.

How about queuing the files saving part as well and not performing it until
after the commit? And if there's another action that needs the file on the
disk (like compiling), queue that as well.

Andrei


0
Comment actions Permalink

Hello Andrei,

DJ>> The integrations which work by running external executables
DJ>> (Perforce and SourceSafe) require actual real files to be on disk
DJ>> in order to perform the commit.
DJ>>
AO> How about queuing the files saving part as well and not performing
AO> it until after the commit? And if there's another action that needs
AO> the file on the disk (like compiling), queue that as well.

I don't know if it's a good idea in general, but in any case we won't be
able to make this complicated scheme work reliably in the short time that
we have remaining before the 6.0 release.

--
Dmitry Jemerov
Software Developer
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

Hello Dmitry,

DJ> I don't know if it's a good idea in general, but in any case we
DJ> won't be able to make this complicated scheme work reliably in the
DJ> short time that we have remaining before the 6.0 release.

I don't see why that would be so hard (but I'm sure you know better how achievable
this would be in IDEA), but as long as you're not putting the blocking progress
dialog back any solution would do, for me. :)

I'm just glad I can at least browse the code while commiting/updating...

Best,
Andrei


0
Comment actions Permalink

Hello Maxim,

is there any work around to keep using the last EAP with CVS ?

thanks
Alejandro Gomez

0
Comment actions Permalink

Dmitry Jemerov wrote:

It looks like the solution that will work most reliably for all VCSes is
to forbid editing of files which are being committed while the commit is
in progress.


That sounds OK, but watch out for race conditions between components - I
have sometimes seen one part of Idea take a while to "catch up" with
another part (sorry, no bug details it's usually just cosmetic).
Honestly, I would rather have the modal dialog box than the possibility
of committing half-formed code ...
R
PS But +10 on the non-blocking update :)

0
Comment actions Permalink

So I guess, if we use cvs + ssh, the current build isn't usable, regarding cvs features (gui freeze). Will we get a quick bugfix release regarding this one? I won't use a build, where cvs integration is broken.

Kind regards

Thomas Gülden
Munich, Germany

0
Comment actions Permalink

Hello Thomas,

T> So I guess, if we use cvs + ssh, the current build isn't usable,
T> regarding cvs features (gui freeze). Will we get a quick bugfix
T> release regarding this one? I won't use a build, where cvs
T> integration is broken.

Yes, we plan to release a new EAP very soon.

--
Dmitry Jemerov
Software Developer
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

Great, thanks a lot.

Thomas Gülden
Munich, Germany

0
Comment actions Permalink

Chris Miller wrote:

I'm using CVS. A thread dump is attached.


Happened to me during a cvs commit as well. It's about time for a new build.

Sascha

0

Please sign in to leave a comment.