This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/pip/dev-support/git-jira-release-audit/gitpython-3.1.37
in repository https://gitbox.apache.org/repos/asf/hbase.git
omit 06cc046692d Bump gitpython in /dev-support/git-jira-release-audit
add 921a5706a13 HBASE-28144 Canary publish read failure fails with NPE if
region location is null (#5456)
add 0d15d03d69a HBASE-28133 TestSyncTimeRangeTracker fails with OOM with
small -Xms values (#5450)
add 991d4aab518 HBASE-28147 Bump gitpython from 3.1.35 to 3.1.37 in
/dev-support/flaky-tests (#5458)
add 27f74116150 Bump gitpython in /dev-support/git-jira-release-audit
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (06cc046692d)
\
N -- N -- N
refs/heads/dependabot/pip/dev-support/git-jira-release-audit/gitpython-3.1.37
(27f74116150)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
dev-support/flaky-tests/python-requirements.txt | 2 +-
.../org/apache/hadoop/hbase/tool/CanaryTool.java | 30 ++++++++++++----------
.../regionserver/TestSyncTimeRangeTracker.java | 2 +-
3 files changed, 18 insertions(+), 16 deletions(-)
