JetBrains / JetBrains/clearcase

NullPointerException while fetching Histroy of a java file

Open
#1 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
3
Forks
8
PR merge metrics
No merged PRs in 30d

Description

Whenever I try to fetch History of a file or folder in clearcase project I get NullPointerException

Error in Event log - Problems while loading file history: java.lang.NullPointerException

system/log/idea.log

2019-03-06 17:52:59,374 [ 320684]   INFO - sourceforge.transparent.Runner - |cleartool ls -directory N:/vtm/dvp/java/AccessibleCategory.java  
2019-03-06 17:52:59,598 [ 320908]   INFO - sourceforge.transparent.Runner - |cleartool ls -directory N:/vtm/dvp/java/AccessibleCategory.java  
2019-03-06 17:53:08,600 [ 329910]   INFO - sourceforge.transparent.Runner - |cleartool lshistory -fmt 0%d
1%Fu
2%e
3%l
4%n
5%Nc
 N:/vtm/dvp/java/AccessibleCategory.java  
2019-03-06 17:53:09,298 [ 330608]   INFO - sourceforge.transparent.Runner - |cleartool ls -directory N:/vtm/dvp/java/AccessibleCategory.java

Seems like the clearcase lshistory command is not properly formed. -fmt format should be within quotes

Any pointer how this can be fixed?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the ClearCase history-fetch path that emits the cleartool lshistory command shown in the log, especially the command formatting around -fmt. Reproduce history loading for a file or folder in a ClearCase project, then verify that the command is formed correctly, the history loads, and the NullPointerException no longer occurs.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.