Skip to main content

GitEye KB: Version 1.9 update fails


Issue

GitEye version 1.9.x may fail with a time out error during its update procedure.

The error reported may resemble the example below.
An error occurred while collecting items to be installed
session context was:(profile=DefaultProfile, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
Unable to read repository at http://downloads.open.collab.net/git/giteye/release/plugins/org.eclipse.core.databinding_1.4.2.v20140729-1044.jar.
Read timed out
Unable to read repository at http://downloads.open.collab.net/git/giteye/release/plugins/org.eclipse.core.filesystem_1.4.100.v20140514-1614.jar.
Read timed out

Cause

The reason why this happens isn't easily identified.  The indication of a timeout issue though leads suspicion towards things like a slow data connection or too many packages to update for the allotted time the package manager has specified.


Solution

Repeated attempts to update the software may eventually resolve the issue.


Environment


Version GitEye Version 1.8.x
OS Windows 7
Browser Not applicable


Details

The issue doesn't appear to be stemming from a problem with the code since eventually the packages are able to finish installing and the program works once completed.  The URLs indicated in the error messages are downloadable directly from a Web browser.  This goes to support the execution time running long more than an attempt to retrieve the necessary JARs failing.

Depending on how far the current update is advancing your install, there may be quite a few entries in this error message.  Dismiss the dialog and repeat the update process.  With each successive attempt, the listing in the error dialog should shrink.  Eventually, the update will complete successfully.
Labels:

Comments

Post a Comment

Popular posts from this blog

Remove control of Chrome being managed by organization on personal devices

Chrome may indicate that it's being managed by a user's organization. This warning is provided by the Chrome Policies feature of the browser. To know if an instance of Chrome is managed by an organization, there will be an entry at the bottom of the browser’s hamburger menu (three dot menu), on the right side of the browser window that reads, "Managed by your organization." This is likely due to an entry in the Chrome Policies listing, which can be found by loading this page in the browser: chrome://policy The policies listed in this section are stored in the computer's file system in one of the following locations as JSON files. /usr/share/chromium/policies/managed /usr/share/chromium/policies/recommended Remove the offending JSON files, and click the Reload policies button. The Managed by your organization entry in the browser menu should be gone. A notice like this on instances of Chrome for work, school, library, or other devices that belong to an organizati...
Post a Comment
Read more

Allow Windows authentication using SQL Server driver with DBeaver

DBeaver will allow Microsoft Windows single sign on access when connecting to Microsoft SQL Server using the SQL Server driver (rather than jTDS ).  From the driver properties settings, set the integratedSecurity flag to true . Open the Connection configuration panel and choose the Driver properties section. Set the integratedSecurity flag to true . A subtle, but important step is to not provide username and password credentials to the connection.
7 comments
Read more

Connecting to SQL Server with jTDS using Windows Authentication

UPDATE:   At one point the tip in this article to set the USENTLV2 flag to true was accurate, but it appears it is no longer necessary, at least as far as DBeaver 's use of the driver is concerned.  If it solves an authentication problem, then great.  The expectation is that, an update in one of the packages that make this sort of connection possible has resolved the issue that at one time made this flag necessary. Connecting to Microsoft SQL Server using jTDS with a username and password that's managed by the database manager is pretty straightforward.  It may become a little more problematic however, when trying to use Windows authentication when connecting from a Windows machine. Do not supply a username and password. Set the USENTLMV2 property to true. NOTE:   Step 1 assumes a connection being made from a Windows machine.  If the connection is being made from something else, user credentials may actually be necessary. If the connect...
7 comments
Read more