ANN: PerforcePlugin 0.9.5
The plugin for pallada is available from the plugin manager. Working on
backporting the plugin to Aurora and will post a version soon.
This version contains some performance fixes. Many thanks to Jason Boehle
for finding major bottlenecks in the code and submitting fixes for them.
Here is the changelist for details.
-Dash.
a.. Fixed the caching problem with vcs, so the status commands are much
faster now.
b.. Improved the revision history performance by getting all the
information in one call
c.. Not querying perforce for non-project files.[Dash]
d.. Removing redundant fstat calls after changes to the file.[Dash]
Please sign in to leave a comment.
I keep getting this exception but not sure how to reproduce it. It happens at some point after opening the Perforce log window. I was getting it in 0.9.4 too and I'm using build 2218.
Error message: Access is allowed from event dispatch thread only. Current thread=Thread[Thread-6,6,Idea Thread Group], ourDispatch=Thread[AWT-EventQueue-1,6,Idea Thread Group]
java.lang.Throwable
at com.intellij.openapi.diagnostic.Logger.error(Logger.java:61)
at com.intellij.openapi.d.a.c.assertIsDispatchThread(c.java:386)
at com.intellij.openapi.wm.impl.c.registerToolWindow(c.java:131)
at com.devbrat.vcs.perforce.ui.PerforceToolWindowManager.getP4LogWindow(PerforceToolWindowManager.java:65)
at com.devbrat.vcs.perforce.PerforceVcs.command(PerforceVcs.java:478)
at com.perforce.api.P4Process.notifyCommandListener(P4Process.java:253)
at com.perforce.api.P4Process.exec(P4Process.java:203)
at com.perforce.api.FileEntry.getFiles(FileEntry.java:543)
at com.devbrat.vcs.perforce.FileEntryProvider.loadFileEntries(FileEntryProvider.java:226)
at com.devbrat.vcs.perforce.FileEntryProvider.refreshCache(FileEntryProvider.java:165)
at com.devbrat.vcs.perforce.FileEntryProvider$2.run(FileEntryProvider.java:52)
at com.intellij.openapi.d.a.c.runReadAction(c.java:114)
at com.devbrat.vcs.perforce.FileEntryProvider$1.run(FileEntryProvider.java:50)
at java.util.TimerThread.mainLoop(Timer.java:432)
at java.util.TimerThread.run(Timer.java:382)
I should have said that it happens sometime after opening >>then closing<< the Perforce log window.
Okay, this build seems to be a "downgrade". Along with my other post I'll add:
Revision descriptions are cut off at about 30 chars.
Check in project doesn't check in all files and after running that command it thinks the files it didn't check in aren't checked out anymore(that probably didn't make sense) so I have to open P4Win and check them in.
I'm not seeing the supposed performance improvements either.
Just thought I'd let you know your plugin is a lifesaver though.
I got that just after I posted the plugin... Doh! Will check why that is
happening.
-Dash.
"Brad" <no_mail@jetbrains.com> wrote in message
news:1489622.1090444053734.JavaMail.itn@is.intellij.net...
the Perforce log window.
My bad... posted the wrong jar file. :(
will update it soon, will try to fix the tool window problem before that.
-Dash.
"Brad" <no_mail@jetbrains.com> wrote in message
news:4393441.1090446043497.JavaMail.itn@is.intellij.net...
add:
>
it thinks the files it didn't check in aren't checked out anymore(that
probably didn't make sense) so I have to open P4Win and check them in.
Thanks for using it, and giving feedback :)
-Dash.
"Brad" <no_mail@jetbrains.com> wrote in message
news:8565450.1090446099321.JavaMail.itn@is.intellij.net...
Fixing problems reported by Brad. available from plugin manager.
-Dash.
"Debabrata Dash" <dash@arcsightnospam.com> wrote in message
news:cdm1iq$rpu$1@is.intellij.net...
>
>
>
>
>
About the checkin problem please give the new plugin a shot, may be it will
fix it. otherwise could you tell me the steps to reprduce it here.
Thanks,
dash.
"Debabrata Dash" <dash@arcsightnospam.com> wrote in message
news:cdmuhl$9ff$1@is.intellij.net...
>
>
>
I'll
command
>
>
Any progress on the sync issue with files changing status outside the
plugin?
"Debabrata Dash" <dash@arcsightnospam.com> wrote in message
news:cdmvll$oin$1@is.intellij.net...
>
>
Boehle
much
>
>
Sorry.. .unfortunately the answer is no... I played with it a little bit,
but couldn't come up with a solution. Will try a bit harder next.
-Dash.
"Charles" <ceubanks@alphablox.com> wrote in message
news:cdn80f$53g$1@is.intellij.net...
>
on
them.
>
>
Debabrata Dash wrote:
>>My bad... posted the wrong jar file. :(
>>
>>will update it soon, will try to fix the tool window problem before that.
>>
>>-Dash.
>>
>>"Brad" <no_mail@jetbrains.com> wrote in message
>>news:4393441.1090446043497.JavaMail.itn@is.intellij.net...
>>
>>>Okay, this build seems to be a "downgrade". Along with my other post
>>add:
>>
>>>Revision descriptions are cut off at about 30 chars.
>>>Check in project doesn't check in all files and after running that
>>it thinks the files it didn't check in aren't checked out anymore(that
>>probably didn't make sense) so I have to open P4Win and check them in.
>>
>>>I'm not seeing the supposed performance improvements either.
>>
>>
Well, I can't reproduce it today so either the new build did the trick
or I was just screwing something up. Thanks again. It's getting to the
point that I don't need P4Win anymore. One less app competing for memory
with IDEA:)
Debabrata Dash wrote:
>>Okay, this build seems to be a "downgrade". Along with my other post I'll
>>Revision descriptions are cut off at about 30 chars.
>>Check in project doesn't check in all files and after running that command
>>I'm not seeing the supposed performance improvements either.
Quick question: Why did you decide to cut off the revision description
in the list at 30 chars? I have a big enough monitor that I can see most
of the descriptions without selecting one.