fisheye error while communicating with vcs Meridale New York

Address 34 Morgan Ave, Oneonta, NY 13820
Phone (607) 435-7673
Website Link http://www.upstatetechnology.com
Hours

fisheye error while communicating with vcs Meridale, New York

Navigate to Maintenance Tab and select Re-Index under Repository Source Index Wait for the re-index to complete and check if the error still persist. See questions about this article Powered by Confluence and Scroll Viewport Atlassian Support Ask the community Provide product feedback Contact technical support Atlassian Privacy Policy Terms of use Security Copyright © thanksindexingrepositoryfisheyeCommentTom Davies [Atlassian]Jul 11, 2014Does 'git rev-list --reverse --date-order 262fb8392ab85a51903ccb7d5cf162d2b7cc379c..37c272c1541607ba3df69855324ca80398552ced' run OK on the command line? Report a bug Atlassian News Atlassian Skip to content Skip to breadcrumbs Skip to header menu Skip to action menu Skip to quick search Linked ApplicationsLoading… Quick Search Help About Confluence

Would it be possible for you to re-index this repository from scratch? If the repository is not too large it would be worth reindexing it.CommentAdd your comment...2 answers10-1Alex GoodchildOct 21, 2015still the same fix as of 3.7.0 (on an individual repo)CommentCommentAdd your comment...10-1Alex git symbolic-ref HEAD Resolution To fix this issue, you'll need to update your repository's HEAD to a valid ref, e.g.: git symbolic-ref HEAD refs/heads/my-branch Where my-branch is the "default" branch of And this activity looks like an endless loop.

See questions about this article Powered by Confluence and Scroll Viewport Atlassian Support Ask the community Provide product feedback Contact technical support Atlassian Privacy Policy Terms of use Security Copyright © Thanks, Chris *************************** Repository index failed due to error com.cenqua.fisheye.rep.RepositoryClientException: com.atlassian.fisheye.dvcs.handler.DvcsProcessException: Error while communicating with VCS: com.atlassian.fisheye.dvcs.handler.DvcsProcessException: Error while communicating with VCS: com.atlassian.utils.process.ProcessException: While executing: "c:\Program Files (x86)\git\bin\git.exe whatchanged --always --reverse I don't have anymore ideas, Thanks for helping me, Kevin.gitfisheyeCommentCommentAdd your comment...2 answers10-1ARNOUX KevinMay 15, 2013Hi! You can check what your repository's HEAD is currently referencing this by running the followingcommand on the command line from within the git repository being indexed by FishEye.

Constantly getting the error below. The next time an incremental index is triggered (either after the next polling period for a Git repository with Updates enabled, or after the next push for an Internal Git Repository) Please notice this is fixed since FishEye 3.1.5, so an Upgrade would solve this.CommentViachaslauJun 03, 2014Thnak you all. And this commit dosn't contain commit message at all.

This will sometimes happen if you are have cygwin installed on the local machine but are running FishEye from the Windows command shell. Please also check that your Git version is among the supported versions for FishEye. com.atlassian.fisheye.dvcs.handler.DvcsProcessException: Error while communicating with VCS: fatal: Not a valid object name HEAD at com.atlassian.fisheye.dvcs.client.DvcsContext.executeCommand(DvcsContext.java:214) at com.atlassian.fisheye.git.GitScanner.updateMailMap(GitScanner.java:242) at com.atlassian.fisheye.git.GitScanner.slurpCommits(GitScanner.java:934) at com.atlassian.fisheye.dvcs.DvcsScanner.processBranch(DvcsScanner.java:401) at com.atlassian.fisheye.dvcs.DvcsScanner.processRevisions(DvcsScanner.java:254) at com.cenqua.fisheye.rep.BaseRepositoryScanner.slurpRepository(BaseRepositoryScanner.java:255) at com.cenqua.fisheye.rep.BaseRepositoryScanner.doSlurpTransaction(BaseRepositoryScanner.java:223) at com.cenqua.fisheye.rep.BaseRepositoryScanner.ping(BaseRepositoryScanner.java:182) at com.cenqua.fisheye.rep.BaseRepositoryEngine.doSlurp(BaseRepositoryEngine.java:92) So obviously there is something wrong in processing changes that contain filenames with unicode characters.

Linked ApplicationsLoading…DashboardsProjectsIssuesCaptureGetting Started Give feedback to Atlassian Help JIRA Core help Keyboard Shortcuts About JIRA JIRA Credits Log In FishEyeFE-3621FishEye failed to index Mercurial repository if one of commits have no I tried to re-index from scratch,but that does not help. Was this helpful? Why was this unhelpful?

We updated the fisheye link. I have removed the file and added mailmap.file in the gitconfig and still no luck (this doesn't use the file at all). It wasn't accurate It wasn't clear It wasn't relevant Submit feedback Cancel Have a question about this article? Anyone else hit a similar issue and have another avenue of investigation I can go down?

Skip to content Skip to breadcrumbs Skip to header menu Skip to action menu Skip to quick search Linked ApplicationsLoading… Quick Search Help About Confluence Log in Sign up QuestionsTopicsLeaderboardRewardsRepository Was this helpful? Why was this unhelpful? You will then need tore-index your repository.

Clear the environment variable by typing: set TMPDIR= 2. Hope its can help somebody else, Kevin.CommentCommentAdd your comment...10-1Chin Kim LoongMay 10, 2013Hi Kevin, It seem the problem only happen in Fe v2.7.4 and as you mentioned not able to reproduce Environment variables modified using setwill only retain their updated values until the command shell window is closed.To permanently fix this problem, you'll need to permanently clear the TMPDIR environment variable - I searched for something related to this and, based on the log, it is possible you are facing the bug described by https://jira.atlassian.com/browse/FE-4335.

Was this helpful? Report a bug Atlassian News Atlassian Linked ApplicationsLoading…DashboardsProjectsIssuesCaptureGetting Started Give feedback to Atlassian Help JIRA Core help Keyboard Shortcuts About JIRA JIRA Credits Log In CrucibleCRUC-6770Error when indexing git commits containing For example: 2011-09-09 11:40:06,790 ERROR [InitialPinger1 your-repository] fisheye.app BaseRepositoryScanner-handleSlurpException - Problem processing revisions from repo your-repository due to class com.cenqua.fisheye.rep.RepositoryClientException - com.atlassian.fisheye.dvcs.handler.DvcsProcessException: Error while communicating with VCS: com.cenqua.fisheye.rep.RepositoryClientException: com.atlassian.fisheye.dvcs.handler.DvcsProcessException: Error while It might be that the repository URL and/or path defined in FishEye are incorrect.

AttachmentsIssue Links duplicates FE-3596 HG: Commits with no commit message break indexing Closed Activity People Assignee: Unassigned Reporter: Andrey Larionov Participants: Andrey Larionov Votes: 0 Vote for this issue Watchers: 0 WARN message contains "Cannot resolve changeset parent id cdd39425cc664b656d07ac8840199a7170ab9488 for changeset c535e907c7a233cd9931157da412f0e7751cb83a in REPO-NAME". I am trying to Add existing Git repository (via SCM manager) to Fisheye (v2.7.4 on Win Server), but this error occurs: Error Repository index failed due to errorcom.cenqua.fisheye.rep.RepositoryClientException: com.atlassian.fisheye.dvcs.handler.DvcsProcessException: Error while If this is not the case, please consider the suggestion of opening a support ticket at https://support.atlassian.comfor a further investigation on this.CommentCommentAdd your comment...10-1Gustavo Refosco [Atlassian]Jun 03, 2014Viachaslau, In addition to

Restarted the server, created fresh clones numorous times - nothing. Now are getting the following error: {quote} Repository index failed due to error com.cenqua.fisheye.rep.RepositoryClientException: com.atlassian.fisheye.dvcs.handler.DvcsProcessException: Error while communicating with VCS: fatal: Invalid revision range 262fb8392ab85a51903ccb7d5cf162d2b7cc379c..37c272c1541607ba3df69855324ca80398552ced com.atlassian.fisheye.dvcs.handler.DvcsProcessException: Error while communicating with VCS: Yes No Thanks for your feedback! Can you please confirm if you've set any include/exclude path for this repository?

Linked ApplicationsLoading…DashboardsProjectsIssuesCaptureGetting Started Give feedback to Atlassian Help JIRA Core help Keyboard Shortcuts About JIRA JIRA Credits Log In FishEyeFE-3551Exception during index processLog In ExportXMLWordPrintableDetails Type: Task Status: Closed Priority: Highest Restart FishEye/Crucible. Thanks, John CommentCommentAdd your comment...Sign up or log in to answerWatchRelated questions Powered by Atlassian Confluence 5.7.3, Team Collaboration Software Printed by Atlassian Confluence 5.7.3, Team Collaboration Software. Error message is Repository index failed due to error com.cenqua.fisheye.rep.RepositoryClientException: com.atlassian.fisheye.dvcs.handler.DvcsProcessException: Error while communicating with VCS: com.atlassian.fisheye.dvcs.handler.DvcsProcessException: Error while communicating with VCS: com.atlassian.utils.process.ProcessException: While executing: "hg --config extensions.felog=/usr/lib/yandex/crucible/python/hg/hgfelog/hgfelog.py --config ui.verbose=false felog

You may file a ticket here:https://support.atlassian.com Hope its help. If the problem still happening, I believe you can raise a ticket to us for further investigate. Kind regards,Felipe KraemerAtlassian SupportCommentCommentAdd your comment...Sign up or log in to answerWatchRelated questions Powered by Atlassian Confluence 5.7.3, Team Collaboration Software Printed by Atlassian Confluence 5.7.3, Team Collaboration Software. AttachmentsIssue Links duplicates FE-5176 git rename detection breaks on files with non ASCII characters in their names Closed Activity People Assignee: Unassigned Reporter: Michael Weinrich Participants: Michael Weinrich, Piotr Swiecicki (in

Report a bug Atlassian News Atlassian Skip to content Skip to breadcrumbs Skip to header menu Skip to action menu Skip to quick search Linked ApplicationsLoading… Quick Search Help About Confluence In order to check this, I suggest you to look into your logs for a WARN containing a message "Parent not found". On 3.1.5, git 1.8.3 and windows server 2008. Diagnosis To check if this is the case, type the following at the command-line: set TMPDIR If the output is something like /cygdrive/c/blah or the environment variable otherwise references a non-existent

This should confirm this is the issue. Committers will not be mapped. It wasn't accurate It wasn't clear It wasn't relevant Submit feedback Cancel Have a question about this article? Gustavo,is that what you mean?Magnus HedemarkJan 05, 2016Still seeing FE-4926 in 3.10.1.CommentAdd your comment...10-1Felipe KraemerJun 02, 2014Hi Viachaslau, It looks like the caches in this repository have become corrupted someway.

If this is the case, I would suggest removing the include/exclude paths defined, or adding this same repository (with a different name) without setting the include/exclude path for testing purposes, in Why was this unhelpful? Finally, I have resolved this issue: I changed the version of msysGit used by Fisheye to v1.8.1.2 and all works fine on my Fisheye v2.7.4 Thanks for trying to help me... I am using 3.4.0 version.

See questions about this article Powered by Confluence and Scroll Viewport Atlassian Support Ask the community Provide product feedback Contact technical support Atlassian Privacy Policy Terms of use Security Copyright ©