RE: [mylar-dev] problems in new dev build

["Mik Kersten" <beatmik@xxxxxxx>]

Yes, we still have the problem of JIRA polluting the error log:

JDB-109: Jira connector polluting Eclipse log on connection failures
http://developer.atlassian.com/jira/browse/JDB-109

So we're stuck there.  We could try to test the repository before doing
synch operations, but that gets slippery.  What I think we should do, and
what we've needed for a long time is the ability of putting repositories
offline, for this and other use cases that involve people being in a
situation where they can't access a particular repository.  Our new
connection status overlays in the Task List can also make this offline
status explicit.  That said, for the common case we still need to make
working offline not require any change of mode.

165809: allow a repository to be put into offline mode
https://bugs.eclipse.org/bugs/show_bug.cgi?id=165809

Btw, great detective work on finding that constant hitting of the keyring,
we now cache the username.

Mik

> -----Original Message-----
> From: mylar-dev-bounces@xxxxxxxxxxx [mailto:mylar-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Eugene Kuleshov
> Sent: Friday, November 24, 2006 10:02 AM
> To: Mylar developer discussions
> Subject: Re: [mylar-dev] problems in new dev build
> 
> 
>   Apparently I have couple queries on offline jira instances (require
> vpn). Mylar now is tying to synchronize each task in those queries and
> as a result, error message about unknown host written to the Eclipse
> .log (old issue in jira core services). So, I see hundreds of those now
> on every synchronization. I've seen it before that excessive logging can
> kill Eclipse, so that may be it.
> 
>   I've attached thread dump to that issue, though I don't see anything
> very suspicious there, except that we should probably cache user name in
> repository to avoid hitting Eclipse keyring.
> 
>   regards,
>   Eugene
> 
> 
> Mik Kersten wrote:
> > That doesn't sound too pleasant.  We removed a lot of the Task List
> refresh,
> > so I see only a small fraction of the flickering that was happening with
> > 0.9, but it sounds like there is still a scenario where multiple full
> > refreshes are requested.  I wonder if it could be the presence of many
> JIRA
> > queries or the web connector since I'm not seeing it.  Please reopen the
> > following bug:
> >
> > 159223: reduce amount of refresh required by Task List
> > https://bugs.eclipse.org/bugs/show_bug.cgi?id=159223
> >
> > And provide details on:
> > * The text in the Status bar when this is happening.
> > * Whether by flicker you mean that the whole view blinks, or that the
> labels
> > get redrawn (e.g. [bugs.eclispe.org] disappears and reappears.
> > * How many queries you have and which kinds of queries.
> >
> > Mik
> >
> >
> 
> _______________________________________________
> mylar-dev mailing list
> mylar-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mylar-dev