-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Fix handler and systemd activation errors #5158
Conversation
324b7b1
to
2ca9837
Compare
@vrothberg I changed your package name because I added another file not related to generation. |
I feel rather against changing the package name and adding somehow unrelated code to that package. I believe we have code to check what |
There is no similar code to |
@vrothberg I believe I understand what you are saying but do we need that granularity? Or are other developers just know it's systemd related "So let's go there?" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Personlly I think the directory should be pkg/systemd. I agree with @jwhonce that I as a developer would be looking for the top level directory for all systemd shared code.
If you want to keep the generate code separate then create a sub-dir
pkg/systemd/generate or pkg/systemd/unit
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jwhonce, rhatdan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Why is this [CI:DOCS]? There is actually changed code here and we should be running the tests suites on it. |
☔ The latest upstream changes (presumably #5093) made this pull request unmergeable. Please resolve the merge conflicts. |
On panic from handler: log warning and stack trace, report InternalServerError to client When using `podman system service` make determining the listening endpoint deterministic. // When determining _*THE*_ listening endpoint -- // 1) User input wins always // 2) systemd socket activation // 3) rootless honors XDG_RUNTIME_DIR // 4) if varlink -- adapter.DefaultVarlinkAddress // 5) lastly adapter.DefaultAPIAddress Fixes containers#5150 Fixes containers#5151 Signed-off-by: Jhon Honce <jhonce@redhat.com>
LGTM |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks @jwhonce !
/lgtm |
On panic from handler: log warning and stack trace, report
InternalServerError to client
Set timeouts to allow large files to be sent to/from server. Refactor idle window to support new timeouts.
When using
podman system service
make determining the listening endpoint deterministic.// When determining THE listening endpoint --
// 1) User input wins always
// 2) systemd socket activation
// 3) rootless honors XDG_RUNTIME_DIR
// 4) if varlink -- adapter.DefaultVarlinkAddress
// 5) lastly adapter.DefaultAPIAddress
Fixes #5150
Fixes #5151
Fixes #5224
Signed-off-by: Jhon Honce jhonce@redhat.com