sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: [Compiled Autograd] unnecessasy Memcpy DtoD in backward graph 
Labels: needs reproduction,module: performance,triaged,oncall: pt2

### 🐛 Describe the bug

We are using compiled autograd to get the backward graph through this way:
```
loss = model(**inputs).loss
torch.cuda.synchronize()
time1 = time.time()
with torch._dynamo.compiled_autograd.enable(torch.compile(backend=my_compiler, fullgraph=True)):
    loss.backward()
```
However, the timeline shows that there are many unnecessary Memcpy D2D in the graph:
<img width="1059" alt="截屏2024-11-06 下午3 10 16" src="https://github.com/user-attachments/assets/b2a83b10-a42b-4943-9936-2044a3bf69c7">
The expected timeline without compiled autograd is as follows:
<img width="800" alt="截屏2024-11-06 下午3 12 14" src="https://github.com/user-attachments/assets/473667b7-3145-443e-a301-7416749cdb1a">


### Versions

[pip3] mypy-extensions==1.0.0
[pip3] numpy==1.26.4
[pip3] nvidia-cublas-cu12==12.1.3.1
[pip3] nvidia-cuda-cupti-cu12==12.1.105
[pip3] nvidia-cuda-nvrtc-cu12==12.1.105
[pip3] nvidia-cuda-runtime-cu12==12.1.105
[pip3] nvidia-cudnn-cu12==8.9.2.26
[pip3] nvidia-cufft-cu12==11.0.2.54
[pip3] nvidia-curand-cu12==10.3.2.106
[pip3] nvidia-cusolver-cu12==11.4.5.107
[pip3] nvidia-cusparse-cu12==12.1.0.106
[pip3] nvidia-nccl-cu12==2.19.3
[pip3] nvidia-nvjitlink-cu12==12.6.20
[pip3] nvidia-nvtx-cu12==12.1.105
[pip3] optree==0.13.0
[pip3] torch==2.6.0a0+git0c525b6
[pip3] torchaudio==2.5.0.dev20241024+cpu
[pip3] torchdistx==0.3.0.dev0+cu121
[pip3] torchvision==0.20.0.dev20241024+cpu
[pip3] triton==3.0.0+gitebce7f3a
[pip3] triton-nightly==3.0.0.post20240716052845

cc @msaroufim @ezyang @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire @aakhundov @xmfan
Repository: ui
Issue: [bug]: pictures height inconsistancy and unalingment in firefox browser
Labels: bug

### Describe the bug

pictures of album component in music section of examples are unaligned(desktop view). but in chrome every thing is aligned.
![Screenshot (95)](https://github.com/user-attachments/assets/2a02a1c0-4b22-4cda-8d96-ecaa10c9c97d)


### Affected component/components

AlbumArtwork

### How to reproduce

1-Open fire fox
2- Go to [https://ui.shadcn.com/examples/music](https://ui.shadcn.com/examples/music)

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
windows 11 64bit - firefox Version 132.0.1 (64-bit)
```


### Before submitting

- [X] I've searched for existing issues
- [X] I've made research efforts and searched the documentation
Repository: go
Issue: x/tools/gopls: feature: offer a quickfix to define a struct field on "has no field or method" error
Labels: FeatureRequest,gopls,Tools

### gopls version

v0.16.2

### go env

```shell
-
```


### What did you do?

Having a cursor on a non defined field doesn't suggest a quickfix to declare a new struct field.
Recently a similar feature was merged https://github.com/golang/go/issues/69692 to define a missing method.
However, the ability to make a field is missing.
<img width="653" alt="Screenshot 2024-11-06 at 09 07 37" src="https://github.com/user-attachments/assets/154988e6-013c-4ce9-a2a7-184fb461ee05">



### What did you see happen?

no action suggested
<img width="761" alt="Screenshot 2024-11-06 at 09 07 48" src="https://github.com/user-attachments/assets/3baaede0-8508-4783-99bb-bfc7719f81bc">


### What did you expect to see?

A suggested quick fix "Define a struct field" exists and create a field
<img width="338" alt="Screenshot 2024-11-06 at 09 08 09" src="https://github.com/user-attachments/assets/fe3e4128-ded4-4198-935e-1479a42ea56f">


### Editor and settings

-

### Logs

-
Repository: ollama
Issue: Error: could not connect to ollama app, is it running?
Labels: bug,windows,nvidia,needs more info

### What is the issue?

Tried versions v0.4.0, v0.3.14, and v0.3.13, all yielded the same exact results.
![image_2024-11-06_031207237](https://github.com/user-attachments/assets/0984f689-2351-48f7-a3bd-5bfd98deb484)

Attempted to start the app through start menu, file explorer, and the ollama serve command (in separate windows), all yielded the same results.

I checked the app.log, and every single launch was showing the same thing:

"time=2024-11-06T03:02:50.988-05:00 level=WARN source=server.go:163 msg="server crash 1 - exit code 2 - respawning""

And it'd go so on for server crash 1 - 30 so and so.
I hate making my own issue posts if I can help it but I've spent all night trying to fix this so I'd like some help.


### OS

Windows

### GPU

Nvidia

### CPU

Intel

### Ollama version

0.4.0-rc8
Repository: next.js
Issue: `response.body?.cancel()` of `fetch` causes unexpected behaviors in App Router
Labels: bug

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/lucid-cohen-8r5tyq?workspaceId=cf95a29a-9e60-48fa-8cf5-0d217db0d3c6

### To Reproduce

1. Build and start server (`npm run build && npm run start`)
2. Access `/`

### Current vs. Expected behavior

### Expected:
- The `ReadableStream` (`response.body`) is successfully cancelled.

### Current:
- `response.body?.cancel()` does not resolve, causing the page to not return.
- Once `response.body?.cancel()` is called, the Next.js server does not terminate when `Ctrl + C` is pressed in the terminal.


### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP Fri Mar 29 23:14:13 UTC 2024
  Available memory (MB): 39993
  Available CPU cores: 20
Binaries:
  Node: 22.11.0
  npm: 10.9.0
  Yarn: 1.22.15
  pnpm: 9.10.0
Relevant Packages:
  next: 15.0.2 // Latest available version is detected (15.0.2).
  eslint-config-next: 15.0.2
  react: 19.0.0-rc-02c0e824-20241028
  react-dom: 19.0.0-rc-02c0e824-20241028
  typescript: 5.6.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)

next start (local), Other (Deployed)

### Additional context

Reproduced with not only Next.js v15.0.2 but also v14.2.17 at least.
I know the way to get only header or consume body in other way. This issue focuses on the bug with `response.body.cancel`.
Repository: ui
Issue: [bug]: Sidebar on mobile requires a DialogTitle
Labels: bug

### Describe the bug

When I open the sidebar on mobile I get this error:

```
hook.js:608 `DialogContent` requires a `DialogTitle` for the component to be accessible for screen reader users.

If you want to hide the `DialogTitle`, you can wrap it with our VisuallyHidden component.
```

### Affected component/components

Sidebar

### How to reproduce

Add a sidebar, implement a trigger, emulate a mobile device and open the sidebar. The console log should display this error.

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
MacOS, Chrome
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: ui
Issue: [feat]: Custom breakpoint for mobile sidebar
Labels: area: request

### Feature description

It would be nice to be able to use a different breakpoint than the hardcoded 768px value. I'm building a dashboard and the current breakpoint is too small for my use cases.

### Affected component/components

Sidebar

### Additional Context

Additional details here...

### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues and PRs
Repository: PowerToys
Issue: Honour SHORTCUTS documents  in the AppData\Local\Microsoft\PowerToys\NewPlus\Templates
Labels: Needs-Triage,Product-New+

### Description of the new feature / enhancement

This is a brilliantly useful thing!

Just one key suggestion from me...

I think that if a SHORTCUT to a document is placed in the `AppData\Local\Microsoft\PowerToys\NewPlus\Templates` then that shortcut should be honoured and the **linked document should be instantiated**, not the shortcut.

### Scenario when this would be used?

The current version essentially requires you manage a separate set of templates from those that you may have around your system in a variety of different places.

So, currently, if you update one of your templates you then have to COPY it over to the `AppData\Local\Microsoft\PowerToys\NewPlus\Templates` folder all over again.
Repository: PowerToys
Issue: Would love to personalise notifications
Labels: Needs-Triage

### Description of the new feature / enhancement

I would love to be able to make notifications more personalized. For example making the UI more round or cute, something like that. Also a way to choose where to see the notification would be nice. Being able to not have the mesage box be 100% opacity so it's less intrusive, as well as more sound options to better work with notifications.

### Scenario when this would be used?

I have adhd/autism and need constant reminders to drink (and sometimes eat), but the main notifications of W11 are very intrusive. It could be usable on a daily basis for pretty much anyone I'd think. I now pretty much avoid the main notification feature of W11 as I find it really intrusive.

### Supporting information

_No response_
Repository: tailwindcss
Issue: The `theme()` function from the Tailwind config is not expanded in arbitrary values
Labels: v3

**What version of Tailwind CSS are you using?**

3.4.14

**Reproduction URL**

https://play.tailwindcss.com/jhNKe63ed5

**Describe your issue**

`tailwind.config.js`
```
module.exports = {
  theme: {
    boxShadow: {
      base: '0 0 0 theme(spacing.2) green inset',
    },
  },
}
```

`HTML`
```
<div class="[box-shadow:_theme(boxShadow.base)]">❌</div>

<div class="shadow-base">✅</div>
```

<img width="958" alt="image" src="https://github.com/user-attachments/assets/d2283f1f-f97f-46da-a4c5-27ee76edb8fd">

The `theme()` function does not expand to its actual value when an arbitrary property is used with `theme()`.
Repository: PowerToys
Issue: UI binding with `EnableDataDiagnostics` is buggy between Settings and OOBE pages
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.86

### Installation method

GitHub

### Running as admin

None

### Area(s) with issue?

Settings

### Steps to reproduce

- Open Settings > General > Diagnostics
- Also open OOBE > Diagnostics
- alternately switch both of the ToggleSwitches

### ✔️ Expected Behavior

Both ToggleSwitches reacting, following the setting in the background

### ❌ Actual Behavior

Switching in Settings isn't reflected in OOBE
https://github.com/user-attachments/assets/f39ed557-7fe4-447a-ad7f-b5b9cb1d32f3

After closing and re-opening OOBE window, toggleswitch _is_ correct state

### Other Software

_No response_
Repository: pytorch
Issue: Modify CMake files to support Clang for Windows when building Libtorch-dependent apps
Labels: module: build,module: windows,triaged

### 🚀 The feature, motivation and pitch

I'm using Clang for MSVC on Windows with Ninja to build a Libtorch app. Although I do not see any mention of Clang for Windows in the install instructions of LibTorch, everything should work fine because Clang is ABI compatible with MSVC. The only issue is that some compilation flags are set for the Windows platform which are not recognized by Clang (/Z7, /EHsc, /bigobj), so it's not possible to compile unless I change some lines in the Caffe2Targets.cmake file. What I did was to change from 

```
set_target_properties(torch_cpu PROPERTIES
INTERFACE_COMPILE_DEFINITIONS "USE_DISTRIBUTED;USE_C10D_GLOO"
INTERFACE_COMPILE_OPTIONS "\$<\$<COMPILE_LANGUAGE:CXX>:;\$<\$<OR:\$<CONFIG:Debug>,\$<CONFIG:RelWithDebInfo>>:/Z7>;/EHsc;/bigobj>"
INTERFACE_INCLUDE_DIRECTORIES "${_IMPORT_PREFIX}/include"
INTERFACE_LINK_LIBRARIES "protobuf::libprotobuf;c10;caffe2::mkl"
)
```

to 

```
if (MSVC)
    set_target_properties(torch_cpu PROPERTIES
    INTERFACE_COMPILE_DEFINITIONS "USE_DISTRIBUTED;USE_C10D_GLOO"
    INTERFACE_COMPILE_OPTIONS "\$<\$<COMPILE_LANGUAGE:CXX>:;\$<\$<OR:\$<CONFIG:Debug>,\$<CONFIG:RelWithDebInfo>>:/Z7>;/EHsc;/bigobj>"
    INTERFACE_INCLUDE_DIRECTORIES "${_IMPORT_PREFIX}/include"
    INTERFACE_LINK_LIBRARIES "protobuf::libprotobuf;c10;caffe2::mkl"
    )
else()
    set_target_properties(torch_cpu PROPERTIES
    INTERFACE_COMPILE_DEFINITIONS "USE_DISTRIBUTED;USE_C10D_GLOO"
    INTERFACE_COMPILE_OPTIONS "-fexceptions"
    INTERFACE_INCLUDE_DIRECTORIES "${_IMPORT_PREFIX}/include"
    INTERFACE_LINK_LIBRARIES "protobuf::libprotobuf;c10;caffe2::mkl"
    )
endif()
```

Then it works perfectly. I think it could be beneficial to Windows users if the Pytorch team added support for the Clang compiler on Windows (which *I think* only requires the above fix ?).

Thanks in advance. 

### Alternatives

Right now a Clang-for-Windows user has to manually modify the Caffe2Targets.cmake file to be able to compile an app that links to Libtorch.



### Additional context

_No response_

cc @malfet @seemethere @peterjc123 @mszhanyi @skyline75489 @nbcsm @iremyux @Blackhex
Repository: PowerToys
Issue: Fancy Zones vertical pixel limit lower than 2 vertical screens height
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.86

### Installation method

PowerToys auto-update

### Running as admin

No

### Area(s) with issue?

FancyZones Editor

### Steps to reproduce

Fancy zones editor don't allow to use full height of 2 screens positioned vertically. 


### ✔️ Expected Behavior

Zone editor should utilise full combined screen size. 

### ❌ Actual Behavior

Editor limit of 3040px is below my setup. You can't drag or expand the zone below 3040px point so you end up with bottom screen zone covering half of the screen. 

### Other Software

_No response_
Repository: angular
Issue: bug(timepicker): Timepicker integration with datepicker does not work when Reactive forms are used
Labels: area: forms

### Is this a regression?

- [ ] Yes, this behavior used to work in the previous version

### The previous version in which this bug was not present was

_No response_

### Description

The new timepicker component does not integrate well with datepicker when Reactive forms are used because of Angular's bad support of binding a FormControl to multiple inputs.

Related issues:
https://github.com/angular/angular/issues/58300
https://github.com/angular/angular/issues/51239
https://github.com/angular/angular/issues/50957

### Reproduction

[StackBlitz link](https://stackblitz.com/edit/7zqfws)
Steps to reproduce:
1. Set time input in the "Reactive" fieldset and blur it.
2. Date does not update


### Expected Behavior

Should behave like the `[(ngModel)]` version. 

### Actual Behavior

Date input does not update.

### Environment

Angular CLI: 19.0.0-rc.0
Node: 18.20.3
Package Manager: npm 10.2.3
OS: linux x64

Angular: 19.0.0-rc.0
... animations, cdk, cli, common, compiler, compiler-cli, core
... forms, localize, material, material-moment-adapter
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1900.0-rc.0
@angular-devkit/build-angular   19.0.0-rc.0
@angular-devkit/core            19.0.0-rc.0 (cli-only)
@angular-devkit/schematics      19.0.0-rc.0
@schematics/angular             19.0.0-rc.0
rxjs                            7.4.0
typescript                      5.5.4
zone.js                         0.15.0
Repository: flutter
Issue: Mac_x64 build_tests_2_4 is 2.13% flaky
Labels: P2,c: flake,team-tool,triaged-tool

<!-- meta-tags: To be used by the automation script only, DO NOT MODIFY.
{
  "name": "Mac_x64 build_tests_2_4"
}
-->

The post-submit test builder `Mac_x64 build_tests_2_4` had a flaky ratio 2.13% for the past (up to) 100 commits, which is above our 2.00% threshold.

One recent flaky example for a same commit: https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_x64%20build_tests_2_4/4260
Commit: https://github.com/flutter/flutter/commit/22a7afd99aeb34eb59abb01eb01bdaf30eb7d0b1

Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_x64%20build_tests_2_4/4260
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_x64%20build_tests_2_4/4188

Recent test runs:
https://flutter-dashboard.appspot.com/#/build?taskFilter=Mac_x64%20build_tests_2_4

Please follow https://github.com/flutter/flutter/blob/master/docs/infra/Reducing-Test-Flakiness.md#fixing-flaky-tests to fix the flakiness and enable the test back after validating the fix (internal dashboard to validate: go/flutter_test_flakiness).
Repository: pytorch
Issue: Allow using context managers in torch.fx
Labels: triaged,module: fx,module: python frontend

### 🚀 The feature, motivation and pitch

I'm working on automatically adding profiling to a module graph, and as `torch.autograd.profiler.profile` returns a context manager, it is not possible to do that by wrapping the modules into `torch.fx.GraphModule`s that call the module.

It is possible to invoke most ops in https://github.com/pytorch/pytorch/blob/d622b490d62e5439295bab2b89986eefae8ee5fc/aten/src/ATen/core/interned_strings.h with one workaround or another, e.g.

```python
import builtins
import operator

# prim::GetAttr (foo.bar)
graph.call_function(builtins.getattr, (foo, "bar"))
# prim::__get_item__ (foo["bar"])
graph.call_function(operator.getitem, (foo, "bar"))
```

But there doesn't seem to be a way to call `prim::Enter` or `prim::Exit`.

### Alternatives

Alternatively this particular use case could be solved by the profiler API exposing a built-in way of wrapping a module into a wrapper module that calls the module with a profiler context. The wrappers would have to support arbitrary signatures for the modules to be useful though, a `Tensor -> Tensor` requirement like in `torch.nn.Sequential` is quite limiting.

### Additional context

_No response_

cc @ezyang @SherlockNoMad @EikanWang @jgong5 @wenzhe-nrv @albanD
Repository: react
Issue: [DevTools Bug] Cannot remove node "2546" because no matching node was found in the Store.
Labels: Type: Bug,Status: Unconfirmed,Component: Developer Tools

### Website or app

e-comerce

### Repro steps

login

### How often does this bug happen?

Every time

### DevTools package (automated)

react-devtools-extensions

### DevTools version (automated)

6.0.1-c7c68ef842

### Error message (automated)

Cannot remove node "2546" because no matching node was found in the Store.

### Error call stack (automated)

```text
at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1173889
    at v.emit (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1140783)
    at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1142390
    at bridgeListener (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1552529)
```


### Error component stack (automated)

_No response_

### GitHub query string (automated)

```text
https://api.github.com/search/issues?q=Cannot remove node  because no matching node was found in the Store. in:title is:issue is:open is:public label:"Component: Developer Tools" repo:facebook/react
```
Repository: rust
Issue: Rustc fails to compile a program with ThinLTO and split-debuginfo = "packed"
Labels: A-debuginfo,A-codegen,T-compiler,C-bug,A-LTO

Hi!

A person on Reddit [posted](https://www.reddit.com/r/rust/comments/1gj57up/comment/lvd5rvj/) a strange build error when ThinLTO is enabled. I performed additional build tests in different configurations and I can confirm the error on current Rustc compilers (see the versions below). My environment is Fedora 41 + AMD Ryzen 5900x (x86-64). The test project is https://github.com/anza-xyz/agave on the `master` branch with `144925eda5eba98ef28a47a659be68b93211cdb2`. The test command is `cargo +stable test --profile release-with-debug`/`cargo +nightly test --profile release-with-debug`.

The original report is when ThinLTO is enabled, some binaries fail to be built with the `duplicate split compilation unit` error. I performed the build in multiple configurations and here are my results:

Build ok:
```
[profile.release-with-debug]
inherits = "release"
debug = true
#split-debuginfo = "packed"
lto = "thin"
```
Build ok:
```
[profile.release-with-debug]
inherits = "release"
debug = true
split-debuginfo = "packed"
#lto = "thin"
```
Build ok:
```
[profile.release-with-debug]
inherits = "release"
debug = true
split-debuginfo = "packed"
lto = "fat"
```
Build ok:
```
[profile.release-with-debug]
inherits = "release"
debug = true
split-debuginfo = "unpacked"
lto = "thin"
```
Build fails:
```
[profile.release-with-debug]
inherits = "release"
debug = true
split-debuginfo = "packed"
lto = "thin"
```
Build fails:
```
[profile.release-with-debug]
inherits = "release"
debug = true
split-debuginfo = "packed"
lto = "thin"
codegen-units = 1
```
According to the tests, the buggy is only the combination of ThinLTO and `split-debuginfo = "packed"`. Disabling one of these options or enabling Fat LTO instead of ThinLTO resolves the issue.

I expected to see this happen: the build with `lto = "thin"` + `split-debuginfo = "packed"` is successful

Instead, this happened: the build fails with the `duplicate split compilation unit` error

### Meta
The issue is reproduced on both Rustc versions: stable and current nightly

`rustc --version --verbose`:
```
rustc 1.82.0 (f6e511eec 2024-10-15)
binary: rustc
commit-hash: f6e511eec7342f59a25f7c0534f1dbea00d01b14
commit-date: 2024-10-15
host: x86_64-unknown-linux-gnu
release: 1.82.0
LLVM version: 19.1.1
```

`rustc +nightly --version --verbose`
```
rustc 1.84.0-nightly (fbab78289 2024-11-04)
binary: rustc
commit-hash: fbab78289dd8c6e8860034e0048cfb538f217700
commit-date: 2024-11-04
host: x86_64-unknown-linux-gnu
release: 1.84.0-nightly
LLVM version: 19.1.3
```
Providing `RUST_BACKTRACE=1` doesn't give more information so no backtraces here.
Repository: PowerToys
Issue: Batch convert from HEIC to JPEG or PNG
Labels: Needs-Triage

### Description of the new feature / enhancement

It would be great to have a tool for batch photo conversion from HEIC to JPEG or PNG file formats.

### Scenario when this would be used?

Many existing applications doesn't support yet HEIC.
to convert files today it takes a several manual steps- right click an HEIC file, edit in photos app, save as JPG.

### Supporting information

_No response_
Repository: tensorflow
Issue: tf.autodiff.ForwardAccumulator._watch(primal, tangent) erroneously refers to dtype.is_floating which does not exist for a Keras layer.
Labels: stat:awaiting response,type:bug,stale,comp:apis,2.17

### Issue type

Bug

### Have you reproduced the bug with TensorFlow Nightly?

No

### Source

binary

### TensorFlow version

2.17.0

### Custom code

No

### OS platform and distribution

Linux ubuntu 24.04

### Mobile device

_No response_

### Python version

3.12.3

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

The bug is that in tf.autodiff.ForwardAccumulator._watch(primal, tangent), it refers to the attribute primal.dtype.is_floating, but this causes a crash, as primal.dtype is now a string type variable, and so does not have the attribute "is_floating".

Here is the error message I see, from the standalone code below.

  File "/home/me/.local/lib/python3.12/site-packages/tensorflow/python/eager/forwardprop.py", line 411, in _watch
    if not primal.dtype.is_floating:
           ^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'str' object has no attribute 'is_floating'


### Standalone code to reproduce the issue

```shell
import tensorflow as tf 
x = tf.constant([[2.0, 3.0], [1.0, 4.0]])
targets = tf.constant([[1.], [-1.]])
dense = tf.keras.layers.Dense(1)
dense.build([None, 2])
with tf.autodiff.ForwardAccumulator(
   primals=dense.kernel,
   tangents=tf.constant([[1.], [0.]])) as acc:
  loss = tf.reduce_sum((dense(x) - targets) ** 2.)
print(acc.jvp(loss))
```


### Relevant log output

_No response_