Skip to content

Conversation

@UdjinM6
Copy link

@UdjinM6 UdjinM6 commented Aug 23, 2023

Issue being fixed or feature implemented

fix buid errors like https://gitlab.com/dashpay/dash/-/jobs/4933232262

What was done?

reorder initializations

How Has This Been Tested?

local build with -werror

Breaking Changes

n/a

Checklist:

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have added or updated relevant unit/integration/functional/e2e tests
  • I have made corresponding changes to the documentation
  • I have assigned this pull request to a milestone (for repository code-owners and collaborators only)

fix buid errors after 5531 + 5540
@UdjinM6 UdjinM6 added this to the 20 milestone Aug 23, 2023
Copy link
Member

@PastaPastaPasta PastaPastaPasta left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK for squash merge

@UdjinM6 UdjinM6 changed the title fix(build): reorder initializations fix: reorder initializations Aug 23, 2023
@UdjinM6 UdjinM6 requested review from knst and kwvg August 23, 2023 20:16
Copy link
Collaborator

@knst knst left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@PastaPastaPasta PastaPastaPasta merged commit 3e1c6dd into dashpay:develop Aug 23, 2023
@UdjinM6 UdjinM6 deleted the post_5531_5540 branch August 23, 2023 23:26
knst added a commit to knst/dash that referenced this pull request Sep 1, 2023
Seems as old command `git merge-base --fork-point` doesn't work for some cases of tree structure
Particularly it didn't worked for PR dashpay#5546:
>  @kwvg kwvg force-pushed the utilbps branch from 82d8a61 to f1bc1c3

Firstly, `git merge-base --fork-point develop 82d8a61` returned me wrong commit.
After pulling origin/develop it returns just an empty string.

But `git show-branch --merge-base develop 82d8a61` worked and returned correct commit:
  "3e1c6dd731 fix: reorder initializations (dashpay#5545)" which is the last commit for develop
PastaPastaPasta pushed a commit that referenced this pull request Sep 9, 2023
## Issue being fixed or feature implemented
Seems as old command `git merge-base --fork-point` doesn't work for some
cases of tree structure

Particularly it didn't worked for PR #5546:
>  @kwvg kwvg force-pushed the utilbps branch from 82d8a61 to f1bc1c3

Basically, one of the step `gfb` script -- `git merge-base --fork-point
develop 82d8a61` returned me wrong
commit. After pulling origin/develop it returns just an empty string.

But `git show-branch --merge-base develop
82d8a61` worked and returned correct
commit:
"3e1c6dd731 fix: reorder initializations (#5545)" which is the last
common commit with develop branch


## What was done?
Updated recommended function `function gfd()` in doc

## How Has This Been Tested?
Tested on PR #5546 that failed before and returned wrong diff for me


## Breaking Changes
N/A

## Checklist:
- [x] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have added or updated relevant unit/integration/functional/e2e
tests
- [ ] I have made corresponding changes to the documentation
- [x] I have assigned this pull request to a milestone
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants