1. Bitbucket Website
  2. Public Issue Tracker
  3. master

Issues

Issue #9027 wontfix

Commit log graph isn't always continuous between all pages

shin ohira
created an issue

sample url

https://bitbucket.org/export/hgflow-graph/commits/all?page=3

I found a bug that commit log graph at feft side of pege, is not correct .

36d8931 flow: Closed <feature> '0.f17'.

Please Try other tools ex. tortoiseHg , You can see a good graph.

sample repo is bellow.

hg clone ssh://hg@bitbucket.org/export/hgflow-graph

Comments (12)

  1. shin ohira reporter

    Yes, Line has been cut off.(to parent node) not only 36d8931 .

    The same phenomenon occurs in the following parts:

    shin ohira
    0e73598
    flow: Closed <feature> '0.f19'.
    ブランチfeature/0.f19
    3 days ago
    Default avatarshin ohira
    d235d96 M
    flow: Merged <feature> '0.f17' to <develop> ('develop').
    ブランチdevelop
    3 days ago
    Default avatarshin ohira
    36d8931
    flow: Closed <feature> '0.f17'.
    ブランチfeature/0.f17
    3 days ago
    Default avatarshin ohira
    bee0b5e M
    flow: Merged <feature> '0.f15' to <develop> ('develop').
    ブランチdevelop
    3 days ago
    Default avatarshin ohira
    9ae3ea0
    flow: Closed <feature> '0.f15'.
    ブランチfeature/0.f15
    3 days ago
    Default avatarshin ohira
    f2d6335 M
    flow: Merged <feature> '0.f13' to <develop> ('develop').
    ブランチdevelop
    3 days ago
    Default avatarshin ohira
    af438f1
    flow: Closed <feature> '0.f13'.
    ブランチfeature/0.f13
    3 days ago
    Default avatarshin ohira
    569e8c7 M
    flow: Merged <feature> '0.f11' to <develop> ('develop').
    ブランチdevelop
    3 days ago
    Default avatarshin ohira
    42f0e27
    flow: Closed <feature> '0.f11'.
    
  2. Brodie Rao

    This is a known limitation in our commit history page. It's too computationally expensive for us to render the graph properly from the first page all the way to the page you're currently on, so every few pages the graph will get reset.

    If you need to see a full graph for your repository, I'd recommend using an offline tool like TortoiseHg (or running hg log -G).

  3. Log in to comment