Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

multi: take over multiple small stale PRs #4790

Merged
merged 5 commits into from
Nov 24, 2020

Conversation

guggero
Copy link
Collaborator

@guggero guggero commented Nov 21, 2020

This PR contains multiple independent changes collected from old, stale PRs.
Replaces:

Original PR authors are attributed where possible.

Because 4 of the 5 replaced PRs somehow involve Docker and development builds, I added a commit of my own to finally clear up this discussion (by tacking my own personal opinion on top of it).

To make it possible to communicate over gRPC with an instance
running in Docker we need to expose the correct RPC interface.
Copy link
Collaborator

@carlaKC carlaKC left a comment

Choose a reason for hiding this comment

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

Great cleanup!

@@ -1836,8 +1838,6 @@ out:
}
}

p.wg.Done()
Copy link
Collaborator

Choose a reason for hiding this comment

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

Slight behaviour change here:

  • Previously: wg.Done then disconnect
  • Now: disconnect then wg.Done

Seems like this new ordering is the right way, but perhaps just check that nothing strange happens with the change?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Ah, good catch! I looked at the initial commit message that added the p.wg.Done() there and it explicitly mentioned a deadlock. So I reverted this change and replaced it with that comment instead.

docs/DOCKER.md Outdated Show resolved Hide resolved
Copy link
Collaborator

@bhandras bhandras left a comment

Choose a reason for hiding this comment

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

LGTM

docs/DOCKER.md Outdated
- `Dockerfile`: Used for production builds. Checks out the source code from
GitHub during build. The build argument `--build-arg checkout=v0.x.x-beta`
can be used to specify what git tag or commit to check out before building.
- `Dockerfile.dev` Used for development or testing builds. Uses the local code
Copy link
Collaborator

Choose a reason for hiding this comment

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

nit: dev.Dockerfile

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Oh. Thanks, fixed!

federicobond and others added 4 commits November 23, 2020 14:48
To finally end the discussion what Dockerfile should be used for what
and whether we should build from local source or check out from git, we
place both Dockerfiles next to each other and explicitly document their
purpose.
@guggero guggero modified the milestones: 0.13.0, 0.12.0 Nov 23, 2020
@guggero guggero added this to In progress in v0.12.0-beta via automation Nov 23, 2020
@guggero guggero moved this from In progress to Reviewer approved in v0.12.0-beta Nov 23, 2020
@Roasbeef Roasbeef merged commit 7f9f4a7 into lightningnetwork:master Nov 24, 2020
v0.12.0-beta automation moved this from Reviewer approved to Done Nov 24, 2020
@guggero guggero deleted the old-pr-cleanup branch November 24, 2020 08:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code health Related to code commenting, refactoring, and other non-behaviour improvements docker Docker-related PRs/Issues documentation Documentation changes that do not affect code behaviour refactoring
Projects
No open projects
v0.12.0-beta
  
Done
Development

Successfully merging this pull request may close these issues.

None yet

8 participants