sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: svelte
Issue: Nested animate acts weirdly
Labels: awaiting submitter

### Describe the bug

Basically the movement isn't as it should be when you have nested animate
you may ask why nested animate? well for a grid list with columns you need to animate the columns and rows like in the repo

### Reproduction

[repo](https://svelte-5-preview.vercel.app/#H4sIAAAAAAAACn1U247bNhD9lSkTwDaii9ftvsjWos1bgLR5SN-sLZYrjW12KVIgR7tZCPr3gNTVclEYsD2jM3POHA3ZsJOQaFlybJjiJbKE_VFVLGD0XrnAvqIkZAGzuja5yxxsbkRFILk6pxkjm7GHTGUkykobggZOvMAAbM4lQgsno0tYdW1iMlxZQUKr1f66RopqCeZKlJxwgdTqT10rWoA9SGUkkaDgxCGFj5Y44bpx6YwsaSPQJnB8DLrMs9YvPnZhu5k16LGQwrEBZ0oCq--kzTvcrQJ41sX7lPDhCtrHWb3vfFX9WeuXeXEXL2ud8Ggi7__tx0dDX_874xOqwB_TxHfDLL1V6_UG0gcYjED6W5So60X-hl7VUu67Z20Av26326FvRrlW1vESmlcunVakL320bOvVffo01naatSy-9LI9YH-lYnQwiqIpEcBg6JM38GMzdGmfBmtvnvj802Ty_3uw4J-C6CQkoVmvBWHpa9yfyMmBX9L0PxRtxpHaAHZX9mU0wMJwsvjuCmOQaqNgoS-XyM3o9PACBqp2P-7yIe6OqTua6tAdkuSCvPBn9SCFeoGLwVOasQtRZZM4rlX1co5yXcbEhXwTqsit_f2fXVwIS2MuKoWKcmszBgZlmjFL7xLtBZH8RXCIF2Sq-cDfuOjOZevZq4evmhdCnaMoOsTVQ6aahC6oZpBaQi65tWnGThJ_ALcV5hS-igI1XML7HZx5Fe6gCnf9_ZNR8wF5foFvz_9iThEqcpu8dj034-s7Wszd_fMXL90l1QWP3uQ-2AC3cPRLOQFg7RObdngRBymgv6ASd3mlTVPUhjtwAr9tt20L4wDP59BgEd5vt_AW3ju9MO3b9awGJSfxiuCHdl9hrmU36zjn8Onn7TU62W4nYT1u5iR35LqVDVe6YS78LTzVUt7weu6R5JYjlmKpNHZKr5CHuJYz1KxoBu5BTZJzyi-AxmgzrFDTRf3-xH7HWhawUhfiJLBgCZka28f2J6I7vRXjBgAA)

### Logs

_No response_

### System Info

```shell
System:
    OS: Windows 11 10.0.22631
    CPU: (12) x64 AMD Ryzen 5 7600X 6-Core Processor
    Memory: 21.29 GB / 31.22 GB
  Binaries:
    Node: 20.13.1 - C:\Program Files\nodejs\node.EXE
    npm: 10.5.2 - C:\Program Files\nodejs\npm.CMD
    pnpm: 9.1.3 - ~\AppData\Local\pnpm\pnpm.EXE
    bun: 1.1.9 - ~\.bun\bin\bun.EXE
  Browsers:
    Edge: Chromium (126.0.2592.61)
    Internet Explorer: 11.0.22621.3527
```


### Severity

annoyance
Repository: node
Issue: Means to detect if the current code is run via `--import` 
Labels: feature request,esm,loaders,stale

### What is the problem this feature will solve?

Code might want to determine if it's running via main app entry point or via a module imported via `--import`. For example, a library might instruct users to run the code via `--import` and might want to warn users if this is not the case.

### What is the feature you are proposing to solve the problem?

Not sure what the API should be, maybe `process.isEntryPoint` or something like that?

The entry point is already marked on `globalThis` via a private symbol:
https://github.com/nodejs/node/blob/aca49fc7d16ae87876fec6285b658868e04b1cf7/lib/internal/modules/esm/module_job.js#L255-L257

### What alternatives have you considered?

Currently the only way I can think to detect this would be to parse `new Error().stack` to find the entry point file and then parse and compare to `process.execArgv`. This is not trivial since you'd need to resolve bare specifiers to their actual source files.
Repository: ollama
Issue: Model Cold Storage and user manual management possibility
Labels: feature request

![image](https://github.com/user-attachments/assets/5cdcde7e-1b1e-4d62-af03-a925751d1b1d)

# model management
its nearly impossible to manage models by manual method, and it generates hash values, 

what i was trying to do was to move some models to cold storage, ie HDD, and some to SSD. but couldnt find a way rather than full repo movement , and im faced with this 

![image](https://github.com/user-attachments/assets/1483f7ff-8dd3-4d2a-a441-372957bd1509)


its take lot of time to do this type of management due to sheer volume of transfer, and why does one model generate 100s of blobs? cant it be stored to a folder per model rather than littering everywhere? my best bet is to check date modified time and perform the job.

# proposed

` ollama archive <model_name> <Disk_or_path>`

`ollama pull <Disk_or_path>` will show options which models to revive to cache.

# urgent request


# observations

some users reported that ollama pull takes long time #2850 #5361 etc, i suspect the nature of SSDs to avoid creation of huge reserved space, as first few seconds in task manager it shown 1GB/s , then fall to 200, the pathetic 5MB/s. it could be the write protection mechanism. maybe chunked download and merge? or use huggingface like loader like _part001 _part002 for layers loading?

@bmizerany @drnic @anaisbetts @sqs @lstep
Repository: go
Issue: net/http: TestWriteDeadlineExtendedOnNewRequest/h2 failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "net/http" && test == "TestWriteDeadlineExtendedOnNewRequest/h2"
```

Issue created automatically to collect these failures.

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

    === RUN   TestWriteDeadlineExtendedOnNewRequest/h2
        clientserver_test.go:210: server log: http: TLS handshake error from 127.0.0.1:53917: read tcp 127.0.0.1:53916->127.0.0.1:53917: i/o timeout
        serve_test.go:971: http2 Get #1: Get "https://127.0.0.1:53916": unexpected EOF
    --- FAIL: TestWriteDeadlineExtendedOnNewRequest/h2 (0.27s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: deno
Issue: File with just `+` does not report syntax error
Labels: bug,swc

Create a file `main.ts`.

```ts
+
```

Then run `deno info main.ts`

No diagnostic is raised.

Change the file to:

```ts
a+
```

Running `deno info main.ts` now:

```
error: The module's source code could not be parsed: Expression expected at file:///home/lucacasonato/Downloads/publishing_tasks_903afdc4-681b-403c-bc23-1768af7eaad9/index.ts:1:2

  a+
   ~
```
Repository: ollama
Issue: Support to Intel NPU by Intel NPU Acceleration Library
Labels: feature request,intel

Should be great to add support to the new and future Intel Neural Processing Units

There is already a library for this https://github.com/intel/intel-npu-acceleration-library and i.e. for Phi-3 is great.

I am sure that NPUs will be everywhere, and they will be a viable alternative to CUDA and Nvidia GPUs, imho.
Repository: ollama
Issue: ShipIt folder taking 1GB
Labels: bug,macos

### What is the issue?

Running a junk file scanner it detected the folder com.electron.ollama.ShipIt taking almost 1GB in ~/Library/Caches. This should be automatically cleared.

### OS

macOS

### GPU

_No response_

### CPU

_No response_

### Ollama version

_No response_
Repository: ollama
Issue: how to run in only GPU mode
Labels: bug,nvidia,needs more info

### What is the issue?

my model sometime run half on cpu half on gpu，when I run ollam ps command it shows 49% on cpu 51% on GPU，how can I   config to run model always only on gpu mode but disable on cpu？
pls help me 

### OS

Linux

### GPU

_No response_

### CPU

_No response_

### Ollama version

_No response_
Repository: flutter
Issue: Better postmortem analysis support
Labels: c: new feature,tool,framework,c: proposal,a: error message,P2,team-framework,triaged-framework

### Use case

Often we encounter in Sentry stacktraces like this one https://github.com/flutter/flutter/issues/151834
In the whole stack trace does not appear one of the source files or our app which is probably due to the fact that the error is happening in the Element tree that is created based on our widget definitions but not in our widgets code.


### Proposal

It would be incredibly helpful and time-saving if the flutter framework would offer more information about which widget was the source of a crash. If this information would not need to be included in any exception that the framework throws, It would be enough if we could query some post mortem info before we send the error to sentry.
Repository: deno
Issue: No way to specify specific abstract socket name with `--allow-read/write`.
Labels: permissions,suggestion

Version: Deno 1.44.2

Abstract sockets play very nice with Deno's sandboxing module because `--allow-read=foo.sock --allow-write=foo.sock` allows the process to delete the socket and replace it with a file of the same name. With abstract sockets you can provide unix socket access without providing filesystem access! Neat! However, there is no way to name a specific abstract socket path using the command line arguments. 

Source:
```ts
Deno.serve(
  {
    path: "\0sdfas",
    transport: "unix",
    onListen: async (s) => {
      const conn = await Deno.connect({
        path: "\0sdfas",
        transport: "unix",
      });
      console.log(s, conn.remoteAddr);
    },
  },
  (req: Request) => {
    return new Response("Hello, world!");
  }
);
```

What works:
```
$ deno run ./deno.ts
┌ ⚠️  Deno requests read access to "\0sdfas".
├ Requested by `Deno.serve()` API.
├ Run again with --allow-read to bypass this prompt.
└ Allow? [y/n/A] (y = yes, allow; n = no, deny; A = allow all read permissions) > ^C

$ deno run --allow-read ./deno.ts
┌ ⚠️  Deno requests write access to "\0sdfas".
├ Requested by `Deno.serve()` API.
├ Run again with --allow-write to bypass this prompt.
└ Allow? [y/n/A] (y = yes, allow; n = no, deny; A = allow all write permissions) > ^C

$ deno run --allow-read --allow-write ./deno.ts
{ transport: "unix", path: null } { transport: "unix", path: null }
```

What doesn't:
```
$ deno run --allow-read=\0sdfas --allow-write=\0sdfas ./deno.ts
┌ ⚠️  Deno requests read access to "\0sdfas".
├ Requested by `Deno.serve()` API.
├ Run again with --allow-read to bypass this prompt.
└ Allow? [y/n/A] (y = yes, allow; n = no, deny; A = allow all read permissions) >

$ deno run --allow-read=\x00sdfas --allow-write=\x00sdfas ./deno.ts
┌ ⚠️  Deno requests read access to "\0sdfas".
├ Requested by `Deno.serve()` API.
├ Run again with --allow-read to bypass this prompt.
└ Allow? [y/n/A] (y = yes, allow; n = no, deny; A = allow all read permissions) >
```

I believe this is an OS issue and not a deno issue, but maybe the interface could be expanded to somehow allow the naming of abstract sockets?

For prior art, `echo` has the flag `-e` that "enables the interpretation of backslash escapes". So "\0sdfas" would work with that flag set: 

```
$ echo -e "\0foo" | hexdump -C
00000000  00 66 6f 6f 0a                                    |.foo.|
00000005
$ echo "\0foo" | hexdump -C
00000000  5c 30 66 6f 6f 0a                                 |\0foo.|
00000006
```

Although I can think of no other Deno command line arguments that would be benefitted by this addition :/
Repository: flutter
Issue: [native_assets] `flutter clean` should delete all native assets
Labels: P2,team-tool,triaged-tool

Sometimes the native assets can be in a weird state (for example if a user had misreported dependencies in their hook), and it would be nice if the native assets can just be all deleted to start from scratch. The cleanest solution would be to this as part of `flutter clean`.

It's probably cleanest to provide an API in `package:native_assets_builder` that can be called for this purpose. (The implementation of that API would most likely simply delete `.dart_tool/native_assets_builder/` recursively.)

Somewhat related:

* https://github.com/dart-lang/native/issues/1353
Repository: deno
Issue: Import error on startup when a Fresh project is a workspace member
Labels: bug,workspaces

If a Fresh project is a workspace member, an import error occurs on startup.  Here's how to reproduce it:

```sh
echo '{"workspace": ["fresh"]}' > deno.json
deno run -A -r https://fresh.deno.dev fresh
cd fresh/
deno task start
```

Here's the error message:

```
error: Relative import path "preact" not prefixed with / or ./ or ../ and not in import map from "https://esm.sh/v135/preact-render-to-string@6.3.1/X-ZS8q/denonext/preact-render-to-string.mjs"
    at https://esm.sh/v135/preact-render-to-string@6.3.1/X-ZS8q/denonext/preact-render-to-string.mjs:2:46
```
Repository: react
Issue: Feature Request: ESLint hooks rule for accessing previous state when deriving new state 
Labels: Status: Unconfirmed,Component: ESLint Rules

https://github.com/facebook/react/issues/21448
> A very common mistake and source of bugs in React applications is not using the updater function when deriving new state from old state.
> 
> When using class components, there is a handy [lint rule](https://github.com/yannickcr/eslint-plugin-react/blob/master/docs/rules/no-access-state-in-setstate.md?rgh-link-date=2021-05-06T14%3A34%3A05Z) for this in the eslint-plugin-react project.
> 
> However, their rule does not work for functional components that utilize useState, and they have [suggested](https://github.com/yannickcr/eslint-plugin-react/issues/2539#issuecomment-620879842) that [eslint-plugin-react-hooks](https://github.com/facebook/react/blob/master/packages/eslint-plugin-react-hooks/README.md?rgh-link-date=2021-05-06T14%3A34%3A05Z) would be a more appropriate home for an equivalent lint rule that _does_ work with hooks.
> 
> I've seen this mistake made countless times, and I even fall victim to it every once in awhile, so having an officially sanctioned lint rule would be amazing!

Conversation was locked so we couldn't bump the issue. Note that I'd prefer that issue be re-opened and this one here closed to keep participants, followers, upvotes, creation date, etc.

CC @martdavidson @palfrey @johncmunson, @dangerismycat, @mathieutu, @vlnguyen, @aldenquimby, @schyler-freewill, @Stephen2
Repository: deno
Issue: `deno test --watch` should always print the full test output
Labels: feat,testing,--watch

When running a suite of tests with `deno test --watch ./tests/`, all tests are run initially. As soon as a file is changed on disk, only the affected tests are re-run. This is great.

What is less great is that the output is now trimmed down to only the tests that were executed. This means that I lose the overview over all tests as soon as I touch one of them. I have to either cancel the watch mode and start it again, or manually save a bunch of unchanged test files to slowly reveal all output again.

Consider the following workflow:

1. Run all test in watch mode
2. See that two test files each have a failing test
3. Fix the first test, triggering a re-run
4. [Now I want to see all tests again to find out where the second test was failing]
5. Fix the second test
6. [Now I want to be sure that the entire test suite is green]

I suggest to keep the output from previous test runs in memory and to merge it with the new output. This would combine the best of both worlds: only affected tests are run, and the output of `deno test --watch` still reveals the results of the entire test suite.
Repository: TypeScript
Issue: 'TypeScript and JavaScript Language Features' Formatter hangs
Labels: Bug

I tried to save this file after pasting in the content and it's been hanging for minutes now:

![image](https://github.com/user-attachments/assets/f88ef94f-d5e5-4917-acdd-08464921b2a4)

File stats:

- 241 lines
- 1032768 chars

Problem file content:

[file.json](https://github.com/user-attachments/files/16268315/file.json)

TypeScript log file:

[ts.log](https://github.com/user-attachments/files/16268293/ts.log)
Repository: storybook
Issue: [Bug]: Boolean controls break when attributes names use hyphens(-) in Lit
Labels: bug,needs triage

### Describe the bug

When using Storybook in combination with Lit, hyphenated attribute names (eg: not-interactive), defined using the Lit @property decorator, break the Story book Controls. 

In this PR, I defined the non-interactive attribute like so: 
```
@property({ type: Boolean, reflect: true, attribute: 'not-interactive' }) notInteractive = false;
```
Adding the attribute property breaks the control after the first activation: 

https://github.com/user-attachments/assets/c6eb732e-cbaf-4c5a-9997-2a4c06d1cd21

When I remove the attribute property, this issue is resolved. Though the attribute name is not ideal: 

```
@property({ type: Boolean, reflect: true }) notInteractive = false;
```

https://github.com/user-attachments/assets/c791380f-26d7-4293-8edd-552cca4206f1






### Reproduction link

https://github.com/solid-design-system/solid

### Reproduction steps

1. Navigate to top link
2. Install pnpm (not npm)
3. Install dependencies ('pnpm i')
4. Navigate to packages/components and run dev server ('pnpm dev')
5. Navigate to the 'dialog' component on the Storybook and test the 'no-close-button' attribute
6. Find dialog.ts ((packages/components/components/) and remove the attribute property from the @property decorator. This version should work. 

### System

```bash
Storybook Environment Info:
(node:99778) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)

  System:
    OS: macOS 14.5
    CPU: (8) arm64 Apple M1
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 21.6.2 - /opt/homebrew/bin/node
    npm: 10.2.4 - /opt/homebrew/bin/npm
    pnpm: 8.15.4 - /opt/homebrew/bin/pnpm <----- active
  Browsers:
    Chrome: 126.0.6478.183
    Safari: 17.5
  npmPackages:
    @storybook/addon-essentials: ^8.1.10 => 8.1.10 
    @storybook/addon-interactions: ^8.1.10 => 8.1.10 
    @storybook/addon-links: ^8.1.10 => 8.1.10 
    @storybook/addon-mdx-gfm: ^8.1.10 => 8.1.10 
    @storybook/addons: ^7.5.3 => 7.6.17 
    @storybook/blocks: ^8.1.10 => 8.1.10 
    @storybook/test: ^8.1.10 => 8.1.10 
    @storybook/theming: ^8.1.10 => 8.1.10 
    @storybook/web-components: ^8.1.10 => 8.1.10 
    @storybook/web-components-vite: ^8.1.10 => 8.1.10 
    chromatic: ^11.5.4 => 11.5.4 
    storybook: ^8.1.10 => 8.1.10 
    storybook-addon-designs: 6.3.1 => 6.3.1
```


### Additional context

_No response_
Repository: pytorch
Issue: Improve detail / Create tutorial for torch.distributions 
Labels: module: distributions,module: docs,triaged

### 🚀 The feature, motivation and pitch

The current documentation at https://pytorch.org/docs/stable/distributions.html#  feels a bit sparse and underdeveloped to me. 

It seems that most people, when training VAEs, seem to rely on a custom coded implementation of the kl divergence (often the original by Kingma) and avoid using the built-in torch.distributions functions due to insufficient documentation/examples. If a bit more explanation were added for various things like why the rsample method is used with the pathwise derivative, it would probably get more use.

Many of the distributions available don't even have a mathematical function associated with them for mathematical explicitness. 



### Alternatives

_No response_

### Additional context

_No response_

cc @fritzo @neerajprad @alicanb @nikitaved @svekars @brycebortree
Repository: go
Issue: x/tools/go/packages: use the correct go version for the analyzed project
Labels: NeedsInvestigation,Tools

When the system Go version is newer than the GOTOOLCHAIN go version, we observed the x/tools/go/packages picks up the system Go version as the go version. This can cause the package to use the incompatible `go list` command. @matloob found this is because `x/tools/internal/gocommand.GoVersion` called by `x/tools/go/packages.(*golistState).getGoVersion`, uses `GO111MODULE=off` which prevents correct go version computation depending on toolchain switch.

This bug prevents gopls (v0.15.3, v0.16.0, v0.16.1) from operating with old go versions like go1.19 if the system Go version is newer. (e.g. using `-pgo` flag that doesn't exist in go1.19)

This will potentially break the future gopls versions if users rely on the GOTOOLCHAIN to switch to go versions and go/packages ends up using new `go list` flags that do not exist in the GOTOOLCHAIN version but exist in the system Go version.

We first need to understand why GoVersion uses `GO111MODULE=off`.

cc @golang/tools-team @matloob @findleyr
Repository: storybook
Issue: [Bug]: error when starting `storybook` using `postcss-url` plugin to inline assets
Labels: bug,needs triage

### Describe the bug

When using `PostCSS` plugin ([postcss-url](https://www.npmjs.com/package/postcss-url)) to inline assets using base64 encoding in `url()` error pops up during `storybook` start:
```shell
Unhandled promise rejection: TypeError [ERR_INVALID_ARG_VALUE]: The argument 'path' must be a string or Uint8Array without null bytes. Received '/home/projects/github-txbnpe-gdeiug/\x00/sb-common-assets/nunito-sans-regular.woff2'
```

Feels like the issue has been introduced while doing https://github.com/storybookjs/storybook/pull/27110


### Reproduction link

https://stackblitz.com/edit/github-txbnpe-gdeiug?file=postcss.config.js

### Reproduction steps

1. add `PostCSS` configuration in `postcss.config.js`:
```js
import url from 'postcss-url';

/** @type {import('postcss-load-config').Config} */
const config = {
  extract: false,
  inject: true,
  plugins: [
    url({
      url: 'inline',
    }),
  ],
  sourceMap: true,
};

export default config;
```
2. run `storybook dev -p 6006`

### System

```bash
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.20.3 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm <----- active
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    @storybook/addon-essentials: ^8.3.0-alpha.1 => 8.3.0-alpha.1 
    @storybook/addon-interactions: ^8.3.0-alpha.1 => 8.3.0-alpha.1 
    @storybook/addon-links: ^8.3.0-alpha.1 => 8.3.0-alpha.1 
    @storybook/addon-onboarding: ^8.3.0-alpha.1 => 8.3.0-alpha.1 
    @storybook/blocks: ^8.3.0-alpha.1 => 8.3.0-alpha.1 
    @storybook/react: ^8.3.0-alpha.1 => 8.3.0-alpha.1 
    @storybook/react-vite: ^8.3.0-alpha.1 => 8.3.0-alpha.1 
    @storybook/test: ^8.3.0-alpha.1 => 8.3.0-alpha.1 
    storybook: ^8.3.0-alpha.1 => 8.3.0-alpha.1
```


### Additional context

_No response_
Repository: electron
Issue: [Bug]: NVDA screen reader no longer works since 30.0.0-beta.8
Labels: platform/windows,bug :beetle:,status/confirmed,a11y,30-x-y,31-x-y,32-x-y

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a bug report that matches the one I want to file, without success.

### Electron Version

30.0.0-beta.8

### What operating system(s) are you using?

Windows

### Operating System Version

Windows 11 22631.3880

### What arch are you using?

x64

### Last Known Working Electron version

30.0.0-beta.7

### Expected Behavior

NVDA screen reader can properly read elements in Electron app.

### Actual Behavior

NVDA screen reader fails to read elements in Electron app.

### Testcase Gist URL

_No response_

### Additional Information

Reproduce steps:
1. Download NVDA (https://www.nvaccess.org/download/) and run
2. Make sure the mouse tracking is enabled (by default it was for me), even without running through the setup the software would begin working
3. Move the mouse over the standard Electron app
4. Observe on `30.0.0-beta.8` and later that this doesn't really follow the mouse and just detects the 4 item list group heading
5. In prior versions (`30.0.0-beta.7`) and earlier this will properly read each text element the mouse moves over

It appears this change https://github.com/electron/electron/pull/41256 broke the behavior. Looking at the accessibility tree in MSAA (Microsoft Active Accessibility) mode within the Inspect.exe tool (available in the Windows SDK) it looks like the extra pane and sibling are shown from the above change - when I mouse over elements the empty pane is incorrectly discovered, which I suspect is leading to this behavior.

Note: This could be a NVDA bug as well, but reporting here for visibility and in case there's a known fix that could be done.