sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Status bar tooltip - add support for specifying a list of commands
Labels: help wanted,feature-request,api,workbench-status

It would be nice if extensions would be able to specify a list of commands which would then be passed on to the HoverService so that they are rendered in the hover status bar.
Repository: rust
Issue: Tracking Issue for `const_array_each_ref`
Labels: T-libs-api,C-tracking-issue

Feature gate: `#![feature(const_array_each_ref)]`

This is a tracking issue for supporting the `each_ref` and `each_mut` methods in `[T; N]` in constant expressions.

### Public API

```rust
impl<T, const N: usize> [T; N] {
    pub const fn each_ref(&self) -> [&T; N];

    pub const fn each_mut(&mut self) -> [&mut T; N];
}
```

- [x] Implementation: #133288
- [ ] Final comment period (FCP)
- [ ] Stabilization PR

### Unresolved Questions

- None yet.
Repository: excalidraw
Issue: Saving to the same file leads to data loss
Labels: discussion

**Reproduction**
1. save "old scene"
2. delete all elements (to start from scratch)
3. press ctrl + s

**Actual result**
- Backed up "old scene" got just overridden
Repository: pytorch
Issue: `torch.cond` example raises an AssertionError due to wrong return values from `true_fn` inside class
Labels: oncall: pt2,oncall: export,module: pt2-dispatcher

### 📚 The doc issue

Hi folks,

I noticed that the examples for data-dependent control flow raises an error with the example test case (using the `DynamicShapeCondPredicate(nn.Module)` class [here](https://pytorch.org/docs/stable/cond.html#examples).

Should the function `true_fn()` inside `forward()` actually read (as follows)?

```
    def forward(self, x: torch.Tensor) -> torch.Tensor:
        def true_fn(x: torch.Tensor):
            return x.cos() + x.sin()
```

Thanks in advance! (and thank you for this project).

### Suggest a potential alternative/fix

```
import torch

def true_fn(x: torch.Tensor):
    return x.cos() + x.sin()

def false_fn(x: torch.Tensor):
    return x.sin()

class DynamicShapeCondPredicate(torch.nn.Module):
    """
    A basic usage of cond based on dynamic shape predicate.
    """

    def __init__(self):
        super().__init__()

    def forward(self, x: torch.Tensor) -> torch.Tensor:
        def true_fn(x: torch.Tensor):
            return x.cos() + x.sin()

        def false_fn(x: torch.Tensor):
            return x.sin()

        return torch.cond(x.shape[0] > 4, true_fn, false_fn, (x,))
```

cc @chauhang @penguinwu @avikchaudhuri @gmagogsfm @zhxchen17 @tugsbayasgalan @angelayi @suo @ydwu4 @zou3519 @bdhirsh @yf225
Repository: PowerToys
Issue: C:\Users\DELL\AppData\Local\Microsoft\PowerToys\PowerToys Run\Logs\0.85.1.0\2024-11-21.txt
Labels: Issue-Bug,Product-PowerToys Run,Needs-Triage

### Microsoft PowerToys version

0.85.1.0

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

General

### Steps to reproduce

Version: 0.85.1.0
OS Version: Microsoft Windows NT 10.0.22631.0
IntPtr Length: 8
x64: True
Date: 2024/11/21 19:33:41
Exception:
System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
   at System.Collections.Generic.List`1.Enumerator.MoveNext()
   at System.Windows.Shell.WindowChromeWorker._WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at System.Windows.Interop.HwndSource.PublicHooksFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)



### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: go
Issue: cmd/compile: implement type-based alias analysis
Labels: Performance,NeedsInvestigation,compiler/runtime

### Go version

go version devel go1.24-3ca78afb3b Mon Nov 18 04:56:52 2024 +0000 linux/arm64

### Output of `go env` in your module/workspace:

```shell
AR='ar'
CC='gcc'
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_ENABLED='1'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
CXX='g++'
GCCGO='gccgo'
GO111MODULE=''
GOARCH='arm64'
GOARM64='v8.0'
GOAUTH='netrc'
GOBIN=''
GOCACHE='/home/abokhanko/.cache/go-build'
GODEBUG=''
GOENV='/home/abokhanko/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOGCCFLAGS='-fPIC -pthread -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build625133068=/tmp/go-build -gno-record-gcc-switches'
GOHOSTARCH='arm64'
GOHOSTOS='linux'
GOINSECURE=''
GOMOD='/dev/null'
GOMODCACHE='/home/abokhanko/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/home/abokhanko/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/home/abokhanko/goroot'
GOSUMDB='sum.golang.org'
GOTELEMETRY='local'
GOTELEMETRYDIR='/home/abokhanko/.config/go/telemetry'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/home/abokhanko/goroot/pkg/tool/linux_arm64'
GOVCS=''
GOVERSION='devel go1.24-3ca78afb3b Mon Nov 18 04:56:52 2024 +0000'
GOWORK=''
PKG_CONFIG='pkg-config'
```


### What did you do?

Test case:

```
package test

func Foo(x **int, y *int) int {
  *y = 10
  *x = nil
  return *y + 20
}
```
Compiled with `go build -a -gcflags='-d ssa/all/dump=Foo' test.go`.

### What did you see happen?

Read of `*y` memory location and thus, the subsequent addition of a constant are not eliminated:

```
$ cat Foo_51__trim.dump
...
    (+6) v17 = MOVDload <int> v8 v15 : R1
    (6) v19 = ADDconst <int> [20] v17 : R0
    (6) v20 = MakeResult <int,mem> v19 v15 : <>
```

### What did you expect to see?

Read of `*y` eliminated; subsequent addition of two constant values (`10`, which is the value of `*y` and `20`) folded.
Repository: storybook
Issue: "View external storybook" & "Read composition docs" controls are not accessible using keyboard in Windows and Mac.
Labels: bug,help wanted,accessibility

### Describe the bug

Title: "View external storybook" & "Read composition docs" controls are not accessible using keyboard in Windows and Mac.

User Impact: 
Keyboard users, including those with motor disabilities or who rely on assistive technologies, will be unable to interact with these controls, impacting their ability to access important documentation and resources and therefore they will not be able to complete their desired task. 

Actual Result: 
"View external storybook" & "Read composition docs" controls are not accessible through keyboard in Windows and Mac.

Refer Attachment: MAC_View external storybook & Read composition docs controls are not accessible using keyboard

![Image](https://github.com/user-attachments/assets/fe10cbb8-4683-4333-b99c-c7ba1fe6949d)
https://github.com/user-attachments/assets/ddfa40cb-e388-4a89-87d5-8f5cb05e93a8




Expected Result: 
"View external storybook" & "Read composition docs" controls should be accessible through keyboard using tab key/up and down arrow keys in Windows and Mac.

### Reproduction link

About / Introduction - Page ⋅ Storybook (ambitious-cliff-0c8148010.2.azurestaticapps.net) 

### Reproduction steps

1. Open URL: [About / Introduction - Page ⋅ Storybook (ambitious-cliff-0c8148010.2.azurestaticapps.net)](https://ambitious-cliff-0c8148010.2.azurestaticapps.net/?path=/story/about-introduction--page) in latest edge browser. Home page will be displayed
2. Press tab key to move to the icon beside 'React Wrappers' control and activate it using enter key.
3. Verify on pressing tab keys whether the "View external storybook" & "Read composition docs" controls are accessible through keyboard or not.

### System

```bash
Test Environment: 
OS: Windows 11 Version 24H2 OS build 26100.1742
Browser: Microsoft New Edge Version129.0.2792.52(Official build) (64-bit)
Product: Horizon Framework
URL: About / Introduction - Page ⋅ Storybook (ambitious-cliff-0c8148010.2.azurestaticapps.net)

Mac Test Environment:
OS: macOS Sequoia 15.0.1
Browser: Microsoft New Edge Version130.0.2849.56 (Official build) (64-bit)
Product: Horizon Framework
URL: About / Introduction - Page ⋅ Storybook (ambitious-cliff-0c8148010.2.azurestaticapps.net)
```

### Additional context

_No response_
Repository: go
Issue: os: TestRootConsistencyLstat/dotdot_in_path_after_symlink failures [consistent failure]
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "os" && test == "TestRootConsistencyLstat/dotdot_in_path_after_symlink"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8730669498615587937)):

    === RUN   TestRootConsistencyLstat/dotdot_in_path_after_symlink
        root_test.go:793: with root:    res=
        root_test.go:794:               err=statat a/../target: inappropriate file type or format
        root_test.go:795: without root: res=name:"target" size:8 mode:-rw-r--r-- isdir:false
        root_test.go:796:               err=<nil>
        root_test.go:797: want consistent results, got mismatch
        root_test.go:807: without root, expected PathError; got: statat a/../target: inappropriate file type or format
    --- FAIL: TestRootConsistencyLstat/dotdot_in_path_after_symlink (0.01s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: next.js
Issue: The children of parallel routes page is displayed incorrectly when using browser navigation
Labels: bug

### Link to the code that reproduces this issue

https://github.com/vercel/next-app-router-playground

### To Reproduce

1. Open the url: https://app-router.vercel.app/patterns/breadcrumbs
2. The [Home] tab's children is 'Shared server-side UI that depends ....'
3. Click the [Electronics] tab, this tab's children is a sub breadcrumbs and a box list
4. Click the browser 's back navigation button
5. The [Home] tab's children is the box list of [Electronics] tab

<img width="321" alt="截屏2024-11-21 21 10 02" src="https://github.com/user-attachments/assets/074102a6-9556-406f-a227-6605c7c26c7a">
<img width="318" alt="截屏2024-11-21 21 10 10" src="https://github.com/user-attachments/assets/cfe07bc0-9e7a-4d05-a666-863ccdf74d59">
<img width="418" alt="截屏2024-11-21 21 09 54" src="https://github.com/user-attachments/assets/f6f7e406-60b6-48d8-9a39-0ffb6bc78e5b">



### Current vs. Expected behavior

After clicking the browser's back button, [Home] tab should show children correctly.
This problem can only be reproduced in the production environment, and cannot be reproduced in the development environment

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.1.0: Thu Oct 10 21:05:14 PDT 2024; root:xnu-11215.41.3~2/RELEASE_ARM64_T8103
  Available memory (MB): 16384
  Available CPU cores: 8
Binaries:
  Node: 20.17.0
  npm: 10.8.2
  Yarn: 1.22.19
  pnpm: 9.4.0
Relevant Packages:
  next: 15.0.4-canary.21 // Latest available version is detected (15.0.3).
  eslint-config-next: N/A
  react: 19.0.0-rc-65a56d0e-20241020
  react-dom: 19.0.0-rc-65a56d0e-20241020
  typescript: 5.5.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Not sure

### Which stage(s) are affected? (Select all that apply)

Vercel (Deployed), Other (Deployed)

### Additional context

_No response_
Repository: bitcoin
Issue: Avoid internet traffic from tests
Labels: Tests

### Current behaviour

Tests should not try to open connections to the internet because:

* they may succeed or fail unpredictably, depending on external environment
* are slow
* dox the developer to their ISP that they are running Bitcoin Core tests

### Expected behaviour

Tests should only open local connections (e.g. on the `lo` interface).

Enforce this in the CI, having it to detect non-local traffic and fail accordingly.

### Steps to reproduce

Run the functional tests and monitor the traffic.

### Relevant log output

_No response_

### How did you obtain Bitcoin Core

Compiled from source

### What version of Bitcoin Core are you using?

master@22ef95dbe3e467039e6cd18988e66557d94041d1

### Operating system and version

Ubuntu 28.04 LTS

---

This is being fixed in two parts:

* [x] Fix all tests as of Jan 15 2025: https://github.com/bitcoin/bitcoin/pull/31646
* [ ] Detect future regressions in CI: https://github.com/bitcoin/bitcoin/pull/31349
Repository: svelte
Issue: Add aria-description to HTML Attributes
Labels: types / typescript,a11y

### Describe the bug

Using `aria-description` triggers the `unknown property` warning. 

Aria description is global and should apply to all HTML tags: https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes#global_aria_attributes

Aria-description serves the same purpose as aria-described. However, the aria-description property should only be used when providing a visible description is not the desired user experience.

This is a regression since it should have been fixed here: https://github.com/sveltejs/svelte/issues/7301

### Reproduction

Just use aria-description to an HTML element and observe the compiler warning.

```
<div aria-description="hello">
	World
</div>
```

![image](https://github.com/user-attachments/assets/5393a6dc-a99e-4ce3-b26b-8eeff9d7d3a0)


### Logs

```shell
Object literal may only specify known properties, and '"aria-description"' does not exist in type 'HTMLProps<"div", HTMLAttributes<any>>'.js(2353)
```


### System Info

```shell
System:
    OS: Linux 6.8 Ubuntu 24.04.1 LTS 24.04.1 LTS (Noble Numbat)
    CPU: (32) x64 13th Gen Intel(R) Core(TM) i9-13900K
    Memory: 24.94 GB / 31.05 GB
    Container: Yes
    Shell: 5.2.21 - /bin/bash
  Binaries:
    Node: 20.17.0 - ~/.nvm/versions/node/v20.17.0/bin/node
    npm: 10.8.2 - ~/.nvm/versions/node/v20.17.0/bin/npm
    pnpm: 9.8.0 - ~/.local/share/pnpm/pnpm
  Browsers:
    Chrome: 131.0.6778.85
  npmPackages:
    svelte: 5.0.0 => 5.0.0
```


### Severity

annoyance
Repository: next.js
Issue: Backport request: Server action that fails in middleware fails silently
Labels: bug,Middleware,Runtime

### Link to the code that reproduces this issue

https://github.com/nphmuller/next-server-action-middleware-error

### To Reproduce

1. `npm run dev`
2. Click button

Code from repro:

middleware.ts:
```
export default async function Middleware(request: NextRequest) {
  if (request.method === "POST") {
    return NextResponse.json("Example: token invalid", { status: 401 });
  }
}
```

page.tsx:
```
export default function Home() {
  return (
    <button
      onClick={async () => {
        try {
          await actionThatThrowsViaMiddleware();
        } catch {
          console.log("Caught error");
        }
      }}
    >
      Click for action that throws
    </button>
  );
}

```

actions.ts:
```
"use server";

export const actionThatThrowsViaMiddleware = async () => {};
```

### Current vs. Expected behavior

Expected: Console logs `Caught error`

Actual Next 14: No console log
Actual Next 15: Console logs `Caught error`

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.1.0: Thu Oct 10 21:03:15 PDT 2024; root:xnu-11215.41.3~2/RELEASE_ARM64_T6000
  Available memory (MB): 32768
  Available CPU cores: 10
Binaries:
  Node: 20.13.0
  npm: 10.9.0
  Yarn: N/A
  pnpm: 9.6.0
Relevant Packages:
  next: 14.2.18 // An outdated version detected (latest is 15.0.3), upgrade is highly recommended!
  eslint-config-next: 15.0.3
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.6.3
Next.js Config:
  output: N/A
 ⚠ An outdated version detected (latest is 15.0.3), upgrade is highly recommended!
   Please try the latest canary version (`npm install next@canary`) to confirm the issue still exists before creating a new issue.
   Read more - https://nextjs.org/docs/messages/opening-an-issue
```


### Which area(s) are affected? (Select all that apply)

Middleware, Runtime

### Which stage(s) are affected? (Select all that apply)

next dev (local), next start (local), Vercel (Deployed), Other (Deployed)

### Additional context

This has been fixed sometime during Next 15 development. Some of my apps are currently stuck on Next 14 (due to dependencies that are still incompatible with React 19), so it would be really nice to have this fix in Next 14.
Repository: vscode
Issue: Disabling smooth scrolling doesn't work
Labels: bug,editor-scrollbar

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->

- VS Code Version: 1.95.3
Commit: f1a4fb101478ce6ec82fe9627c43efbf9e98c813
Date: 2024-11-13T14:50:04.152Z
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Linux x64 6.11.5-1-default

OS: opensuse tumbleweed 
package: from zypper code-1.95.3-1731513157.el8.x86_64

Steps to Reproduce:

1. code --disable-extensions --disable-smooth-scrolling
2. configuration:
```
{
    "workbench.colorTheme": "Solarized Dark",
    "editor.unicodeHighlight.nonBasicASCII": false,
    "[python]": {
        "editor.formatOnType": true
    },
    "search.useGlobalIgnoreFiles": true,
    "search.useIgnoreFiles": true,
    "search.exclude": {
        "**": true
    },
    "python.defaultInterpreterPath": "/home/ashaposhnikov/local.venv",
    "[sql]": {
        "editor.defaultFormatter": "adpyke.vscode-sql-formatter"
    },
    "files.watcherExclude": {
        "**/.git/objects/**": true,
        "**/.git/subtree-cache/**": true,
        "**/node_modules/*/**": true
    },
    "editor.smoothScrolling": false,
    "window.zoomLevel": -1
}
```

3. scroll in text editor using mouse wheel

Some time ago disabling smooth scrolling worked as expected, scrolling was instant.

Now scrolling animation exists (which is smooth scrolling in my understanding) no matter the position of setting.

I tried setting window.zoomLevel -1, 0, 1 and 2 without success.
Repository: go
Issue: x/tools/gopls/internal/test: spurious failures due to EBADF on netbsd/arm
Labels: OS-NetBSD,NeedsInvestigation,Tools

```
#!watchflakes
default <- pkg ~ `golang.org/x/tools/gopls/internal/test` && `bad file descriptor` && goos == "netbsd" && goarch == "arm"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8730748669696124305)):

    === RUN   TestPackageCompletion/package_completion_on_terminal_newline/default
        completion_test.go:220: completion item mismatch (-want +got):
              []string{
            - 	"package apple",
            - 	"package apple_test",
              	"package fruits",
              	"package fruits_test",
              	"package main",
              }
            
    ...
    [Trace - 15:23:48.479 PM] Received notification 'textDocument/publishDiagnostics'.
    Params: {"uri":"file:///home/swarming/.swarming/w/ir/x/t/gopls-test-1475936701/TestPackageCompletion/package_completion_on_terminal_newline/default/work/fruits/testfile6.go","version":1,"diagnostics":[]}
    
    
    [Trace - 15:23:48.486 PM] Received notification '$/progress'.
    Params: {"token":"8761737497789441884","value":{"kind":"end","message":"Done."}}
    
    
    #### End Gopls Test Logs for "TestPackageCompletion/package_completion_on_terminal_newline/default"
    --- FAIL: TestPackageCompletion/package_completion_on_terminal_newline/default (1.40s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: rust
Issue: Nightly-only cfg gating like `#[cfg(target_has_atomic)]` is confusing
Labels: C-enhancement,A-stability,T-compiler,requires-nightly,A-cfg

EDIT: this is *intended* that `cfg(target_has_atomic)` is nightly-only (not feature-gated), but I find it still very confusing.

---

Note that `#[cfg(target_has_atomic)]` is not to be confused with `#[cfg(target_has_atomic = "8")]`.

Given a snippet (just `rustc --crate-type="lib"`, no additional `--cfg` flags)

```rs
#[cfg(target_has_atomic)]
fn foo() {}
```

- On stable 1.82.0 this produces no warnings.
- On nightly 2024-11-20 this produces a `dead_code` warning indicating `target_has_atomic` cfg is enabled.

```
warning: function `foo` is never used
 --> src/lib.rs:2:4
  |
2 | fn foo() {}
  |    ^^^
  |
  = note: `#[warn(dead_code)]` on by default
```

AFAICT there is no test coverage for the intended behavior of *just* `#[cfg(target_has_atomic)]` alone, other test coverage is mostly for check-cfg.

cc @Urgau since you worked on builtin-cfg rejection do you know anything about if this is intended, and if so, what is the intended behavior here?
Repository: pytorch
Issue: Enable CI and Build Support for PyTorch on PPC64LE Architecture
Labels: module: build,triaged,enhancement,module: POWER

**Description:**
We propose extending PyTorch support to the POWER/PPC64LE architecture to facilitate builds and CI workflows tailored to this platform.

**Background:**

1. We forked the pytorch/pytorch repository and successfully generated and tested wheels using a self-hosted CI runner on an OSU PPC64LE machine.

2. The changes in our forked repository include:

**Workflows:** Added a new job for PPC64LE in .github/workflows/ppc64le.yaml.
**Dockerfiles:** Created .github/workflows/dockerfile.ppc64le.
**Build Script:** Added .github/scripts/ppc64le-build.sh.
These changes were part of a proof-of-concept (POC) to demonstrate feasibility.

3. Currently, we are working on incorporating these modifications into common files such as .github/workflows/_linux-build.yml to align with existing workflows.

**Fork Information:**

**Repository:** [sandeepgupta12/pytorch](https://github.com/sandeepgupta12/pytorch/tree/using-dockerfile-buildscript-first-success).

**Request:**
We seek your input on:

- The overall feasibility and design of the proposed changes.

- Best practices for integrating architecture-specific workflows.

- Any additional considerations for upstreaming support for PPC64LE.

**Additional Information:**
We are ready to provide any further information or assistance required to facilitate this integration. Please let us know if there are additional steps or requirements to move forward.

cc @malfet @seemethere