Skip to content

AUTOSCALE-543: Add lint and e2e tests for kedacore-http-add-on - #82805

Draft
linkvt wants to merge 2 commits into
openshift:mainfrom
linkvt:add-http-addon-ci-tests
Draft

AUTOSCALE-543: Add lint and e2e tests for kedacore-http-add-on#82805
linkvt wants to merge 2 commits into
openshift:mainfrom
linkvt:add-http-addon-ci-tests

Conversation

@linkvt

@linkvt linkvt commented Aug 3, 2026

Copy link
Copy Markdown
Member

TODO

  • make sure E2E tests also use tls and o11y profiles
  • review coderabbit comments
  • update ci image in .ci-operator.yaml in http addon repo and revert changes here

Requires: openshift/kedacore-http-add-on#6

Add CI test configuration for the HTTP add-on: a lint presubmit using the golangci-lint CI image, and an e2e test on AWS that installs KEDA via Helm, deploys the http-add-on from CI-built images, and runs the default profile tests.

Changes

  • Add grpc-echo test image build
  • Add golangci-lint base image and lint presubmit test
  • Add http-addon-e2e-aws inline multi-stage test (setup/run/clean)

Summary by CodeRabbit

  • Updates OpenShift CI for kedacore-http-add-on.
  • Builds the grpc-echo test image.
  • Uses the OpenShift RHEL 9 Go 1.26 build image.
  • Adds a golangci-lint presubmit test with documentation-only skip conditions.
  • Adds an AWS end-to-end workflow with setup, test, and cleanup steps.
  • Passes CI-built operator, scaler, and grpc-echo images to the AWS test.
  • Configures AWS post-processing, ReportPortal result submission, and GOLANGCI_LINT_CACHE.
  • TLS and observability profiles are not included.
  • The changes require kedacore-http-add-on PR #6.

@openshift-ci-robot

openshift-ci-robot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

@linkvt: This pull request references AUTOSCALE-543 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

TODO

  • make sure E2E tests also use tls and o11y profiles

Requires: openshift/kedacore-http-add-on#6

Add CI test configuration for the HTTP add-on: a lint presubmit using the golangci-lint CI image, and an e2e test on AWS that installs KEDA via Helm, deploys the http-add-on from CI-built images, and runs the default profile tests.

Changes

  • Add grpc-echo test image build
  • Add golangci-lint base image and lint presubmit test
  • Add http-addon-e2e-aws inline multi-stage test (setup/run/clean)

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 3, 2026
@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 3, 2026
@openshift-ci

openshift-ci Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@coderabbitai

coderabbitai Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: 9bb4e9f6-6db3-47af-bedc-878269c508ab

📥 Commits

Reviewing files that changed from the base of the PR and between fb7da88 and 0f4266e.

📒 Files selected for processing (1)
  • ci-operator/config/openshift/kedacore-http-add-on/openshift-kedacore-http-add-on-main.yaml
🚧 Files skipped from review as they are similar to previous changes (1)
  • ci-operator/config/openshift/kedacore-http-add-on/openshift-kedacore-http-add-on-main.yaml

Walkthrough

The OpenShift CI configuration changes the build root, adds the gRPC echo image to build outputs, and defines conditional lint and AWS end-to-end workflows.

Changes

CI workflow configuration

Layer / File(s) Summary
Build inputs, outputs, and lint validation
ci-operator/config/openshift/kedacore-http-add-on/openshift-kedacore-http-add-on-main.yaml
The configuration uses the OpenShift RHEL 9 Go 1.26 image stream, adds the gRPC echo image, and runs make lint unless documentation-only or metadata-only changes occur.
AWS end-to-end workflow
ci-operator/config/openshift/kedacore-http-add-on/openshift-kedacore-http-add-on-main.yaml
The workflow defines conditional execution, AWS cluster configuration, cleanup, result reporting, image dependencies, and 100m CPU requests. Setup consumes operator, interceptor, and scaler images. Execution consumes the gRPC echo image and runs from src.

Estimated code review effort: 2 (Simple) | ~10 minutes

Sequence Diagram(s)

sequenceDiagram
  participant CIWorkflow
  participant SourceContainer
  participant BuildOutputs
  participant AWSCluster
  CIWorkflow->>SourceContainer: Run AWS end-to-end setup from src
  SourceContainer->>BuildOutputs: Consume operator, interceptor, and scaler images
  SourceContainer->>AWSCluster: Configure AWS cluster
  CIWorkflow->>SourceContainer: Run AWS end-to-end command from src
  SourceContainer->>BuildOutputs: Consume gRPC echo image
  SourceContainer->>AWSCluster: Execute end-to-end tests
  CIWorkflow->>AWSCluster: Run cleanup and report results
Loading
🚥 Pre-merge checks | ✅ 14 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Ipv6 And Disconnected Network Test Compatibility ⚠️ Warning The AWS e2e setup uses the public Helm repository https://kedacore.github.io/charts and the job posts results to external ReportPortal, so disconnected CI cannot run it. Run /payload-job periodic-ci-openshift-release-master-nightly-4.22-e2e-metal-ipi-ovn-ipv6; mirror dependencies or add [Skipped:Disconnected] when external access cannot be removed.
✅ Passed checks (14 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly summarizes the main changes: adding lint and end-to-end test configuration for kedacore-http-add-on.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed The PR changes only CI YAML; all configured names (lint, http-addon-e2e-aws, e2e-setup, e2e-run, e2e-clean) are static, with no dynamic Ginkgo titles.
Test Structure And Quality ✅ Passed The PR changes only CI YAML and generated Prow jobs; no Ginkgo test files, It blocks, or cluster test implementation were added or modified, so this check is not applicable.
Microshift Test Compatibility ✅ Passed The PR changes only CI YAML and generated Prow job files; it adds no Ginkgo test source or OpenShift API/resource references to assess for MicroShift compatibility.
Single Node Openshift (Sno) Test Compatibility ✅ Passed The PR changes only one YAML CI configuration file; it adds no Ginkgo test declarations or test source that could make SNO-incompatible assumptions.
Topology-Aware Scheduling Compatibility ✅ Passed Only the CI YAML changed; it adds image builds, test steps, post-processing, and CPU requests, with no topology, affinity, node, toleration, replica, or PDB scheduling constraints.
Ote Binary Stdout Contract ✅ Passed The complete PR diff changes only three YAML files; it adds no Go/source code or process-level stdout/logging calls.
No-Weak-Crypto ✅ Passed The PR changes only one CI YAML file, and the exact added lines contain no MD5, SHA1, DES, RC4, Blowfish, ECB, custom crypto, or secret-comparison code.
Container-Privileges ✅ Passed The changed CI YAML adds no privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, allowPrivilegeEscalation, or root security settings; referenced AWS steps also define none.
No-Sensitive-Data-In-Logs ✅ Passed The PR adds CI commands and image references only; no sensitive values are logged, and the ReportPortal step exits for this repository before credential handling.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@openshift-ci

openshift-ci Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: linkvt

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 3, 2026

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (1)
ci-operator/config/openshift/kedacore-http-add-on/openshift-kedacore-http-add-on-main.yaml (1)

6-9: 🔒 Security & Privacy | 🔵 Trivial | ⚡ Quick win

Pin the golangci-lint base image.

tag: latest allows the lint toolchain to change without a configuration change. The supplied mirror entries are versioned, and the supplied context does not show ci/golangci-lint:latest. Use an existing versioned tag, or verify that the latest ImageStreamTag is intentionally maintained. ci-operator imports base images as ImageStreamTags, so a missing tag prevents the lint job from starting. (docs.ci.openshift.org)

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@ci-operator/config/openshift/kedacore-http-add-on/openshift-kedacore-http-add-on-main.yaml`
around lines 6 - 9, Update the golangci-lint image configuration to use an
existing versioned ImageStreamTag instead of tag: latest, matching the available
mirror entries and preserving the ci/golangci-lint image reference so
ci-operator can start the lint job.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In
`@ci-operator/config/openshift/kedacore-http-add-on/openshift-kedacore-http-add-on-main.yaml`:
- Around line 94-101: Move the e2e-clean step from steps.test to steps.post so
it runs after failures and before AWS cluster teardown. When overriding the
workflow post list, retain both ipi-aws-post and send-results-to-reportportal,
alongside e2e-clean.

---

Nitpick comments:
In
`@ci-operator/config/openshift/kedacore-http-add-on/openshift-kedacore-http-add-on-main.yaml`:
- Around line 6-9: Update the golangci-lint image configuration to use an
existing versioned ImageStreamTag instead of tag: latest, matching the available
mirror entries and preserving the ci/golangci-lint image reference so
ci-operator can start the lint job.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: c48cd26e-c737-44d3-b4e8-cb28d6a2049c

📥 Commits

Reviewing files that changed from the base of the PR and between 93510f9 and 17dfd73.

⛔ Files ignored due to path filters (2)
  • ci-operator/jobs/openshift/kedacore-http-add-on/openshift-kedacore-http-add-on-main-postsubmits.yaml is excluded by !ci-operator/jobs/**
  • ci-operator/jobs/openshift/kedacore-http-add-on/openshift-kedacore-http-add-on-main-presubmits.yaml is excluded by !ci-operator/jobs/**
📒 Files selected for processing (1)
  • ci-operator/config/openshift/kedacore-http-add-on/openshift-kedacore-http-add-on-main.yaml

@linkvt
linkvt force-pushed the add-http-addon-ci-tests branch from 17dfd73 to db6a808 Compare August 3, 2026 13:20

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In
`@ci-operator/config/openshift/kedacore-http-add-on/openshift-kedacore-http-add-on-main.yaml`:
- Around line 64-71: Update the custom steps.post list in the OpenShift KEDA
HTTP add-on configuration to retain e2e-clean and append both ipi-aws-post and
send-results-to-reportportal in that order, preserving AWS cluster
gathering/deprovisioning and result reporting.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: e3bdb0bf-42fc-447f-b696-fb58e31d4482

📥 Commits

Reviewing files that changed from the base of the PR and between 17dfd73 and db6a808.

⛔ Files ignored due to path filters (2)
  • ci-operator/jobs/openshift/kedacore-http-add-on/openshift-kedacore-http-add-on-main-postsubmits.yaml is excluded by !ci-operator/jobs/**
  • ci-operator/jobs/openshift/kedacore-http-add-on/openshift-kedacore-http-add-on-main-presubmits.yaml is excluded by !ci-operator/jobs/**
📒 Files selected for processing (1)
  • ci-operator/config/openshift/kedacore-http-add-on/openshift-kedacore-http-add-on-main.yaml

@linkvt

linkvt commented Aug 7, 2026

Copy link
Copy Markdown
Member Author

/pj-rehearse

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@linkvt: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@linkvt
linkvt force-pushed the add-http-addon-ci-tests branch from db6a808 to 8a9f5a0 Compare August 7, 2026 15:54
@coderabbitai

coderabbitai Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Note

GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer.

@linkvt

linkvt commented Aug 7, 2026

Copy link
Copy Markdown
Member Author

/pj-rehearse pull-ci-openshift-kedacore-http-add-on-main-http-addon-e2e-aws
/pj-rehearse pull-ci-openshift-kedacore-http-add-on-main-lint

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@linkvt: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@linkvt: requesting more than one rehearsal in one comment is not supported. If you would like to rehearse multiple specific jobs, please separate the job names by a space in a single command.

@linkvt

linkvt commented Aug 7, 2026

Copy link
Copy Markdown
Member Author

/pj-rehearse pull-ci-openshift-kedacore-http-add-on-main-lint

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@linkvt: your /pj-rehearse request was not processed because the request waited in queue for longer than 5 minutes. Please retry in a few minutes.

@linkvt

linkvt commented Aug 7, 2026

Copy link
Copy Markdown
Member Author

/pj-rehearse pull-ci-openshift-kedacore-http-add-on-main-lint

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@linkvt: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

Add CI test configuration for the HTTP add-on: a lint presubmit
using the golangci-lint CI image, and an e2e test on AWS that
installs KEDA via Helm, deploys the http-add-on from CI-built
images, and runs the default profile tests.

Changes:
- Add grpc-echo test image build
- Add golangci-lint base image and lint presubmit test
- Add http-addon-e2e-aws inline multi-stage test (setup/run/clean)

Signed-off-by: Vincent Link <vlink@redhat.com>
@linkvt
linkvt force-pushed the add-http-addon-ci-tests branch from 8a9f5a0 to fb7da88 Compare August 7, 2026 18:04
@coderabbitai

coderabbitai Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Note

GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer.

@linkvt

linkvt commented Aug 7, 2026

Copy link
Copy Markdown
Member Author

/pj-rehearse pull-ci-openshift-kedacore-http-add-on-main-http-addon-e2e-aws pull-ci-openshift-kedacore-http-add-on-main-lint

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@linkvt: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

♻️ Duplicate comments (1)
ci-operator/config/openshift/kedacore-http-add-on/openshift-kedacore-http-add-on-main.yaml (1)

67-74: ⚠️ Potential issue | 🟠 Major

Preserve the ipi-aws post steps.

The local steps.post list contains only e2e-clean. Append ipi-aws-post and send-results-to-reportportal after e2e-clean. The ipi-aws workflow defines these steps for AWS cluster gathering, deprovisioning, and result reporting. The local configuration overrides workflow fields, so omitting them can leave AWS resources and omit test results. (steps.ci.openshift.org)

This is the same unresolved issue reported in the previous review comments.

Proposed fix
     - as: e2e-clean
       cli: latest
       commands: GOFLAGS="" make e2e-test-openshift-clean
       from: src
       resources:
         requests:
           cpu: 100m
+    - chain: ipi-aws-post
+    - ref: send-results-to-reportportal

Also applies to: 100-100

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@ci-operator/config/openshift/kedacore-http-add-on/openshift-kedacore-http-add-on-main.yaml`
around lines 67 - 74, Extend the local steps.post list after e2e-clean with the
ipi-aws-post and send-results-to-reportportal steps, preserving their
workflow-defined configuration so AWS cluster cleanup and result reporting
remain enabled.

Source: MCP tools

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Duplicate comments:
In
`@ci-operator/config/openshift/kedacore-http-add-on/openshift-kedacore-http-add-on-main.yaml`:
- Around line 67-74: Extend the local steps.post list after e2e-clean with the
ipi-aws-post and send-results-to-reportportal steps, preserving their
workflow-defined configuration so AWS cluster cleanup and result reporting
remain enabled.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: c418b281-7af3-4bbc-979b-b74bbffbd7db

📥 Commits

Reviewing files that changed from the base of the PR and between 2068cf2 and fb7da88.

⛔ Files ignored due to path filters (2)
  • ci-operator/jobs/openshift/kedacore-http-add-on/openshift-kedacore-http-add-on-main-postsubmits.yaml is excluded by !ci-operator/jobs/**
  • ci-operator/jobs/openshift/kedacore-http-add-on/openshift-kedacore-http-add-on-main-presubmits.yaml is excluded by !ci-operator/jobs/**
📒 Files selected for processing (1)
  • ci-operator/config/openshift/kedacore-http-add-on/openshift-kedacore-http-add-on-main.yaml

…CACHE

Signed-off-by: Vincent Link <vlink@redhat.com>
@linkvt

linkvt commented Aug 7, 2026

Copy link
Copy Markdown
Member Author

/pj-rehearse pull-ci-openshift-kedacore-http-add-on-main-http-addon-e2e-aws pull-ci-openshift-kedacore-http-add-on-main-lint

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@linkvt: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@linkvt: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-openshift-kedacore-http-add-on-main-http-addon-e2e-aws openshift/kedacore-http-add-on presubmit Presubmit changed
pull-ci-openshift-kedacore-http-add-on-main-lint openshift/kedacore-http-add-on presubmit Presubmit changed
pull-ci-openshift-kedacore-http-add-on-main-images openshift/kedacore-http-add-on presubmit Ci-operator config changed
Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@openshift-ci

openshift-ci Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

@linkvt: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/rehearse/openshift/kedacore-http-add-on/main/http-addon-e2e-aws 0f4266e link unknown /pj-rehearse pull-ci-openshift-kedacore-http-add-on-main-http-addon-e2e-aws

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants