sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: react-native
Issue: [iOS] Some weird animation happening on inputs and buttons when switching screens
Labels: Platform: iOS,Component: Button,Component: Switch,Needs: Author Feedback,Type: New Architecture

### Description

When switching between screens using simple unmount/mount logic like this:

```
      {activeTab === 1 && <TabOne />}
      {activeTab === 2 && <TabTwo />}
```
it seems like React Native is trying to "reuse" some inputs or components in some way.

**Result:** This causes strange animations or transitions between screens (and screen components like TextView or Button)

### Steps to reproduce

1. Run the provided example code (Expo Snack)
2. Click between "TAB ONE" and "TAB TWO"

### React Native Version

0.76.3

### Affected Platforms

Runtime - iOS

### Areas

Fabric - The New Renderer

### Output of `npx react-native info`

```text
I'm not entirely sure how to run this `npx react-native info ` on expo snack so I downloaded .zip from expo snack and run this command...

System:
  OS: macOS 15.1.1
  CPU: (12) arm64 Apple M4 Pro
  Memory: 131.67 MB / 24.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 20.16.0
    path: ~/.nvm/versions/node/v20.16.0/bin/node
  Yarn: Not Found
  npm:
    version: 10.8.1
    path: ~/.nvm/versions/node/v20.16.0/bin/npm
  Watchman:
    version: 2024.11.18.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.16.2
    path: /opt/homebrew/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 24.1
      - iOS 18.1
      - macOS 15.1
      - tvOS 18.1
      - visionOS 2.1
      - watchOS 11.1
  Android SDK: Not Found
IDEs:
  Android Studio: 2024.2 AI-242.23339.11.2421.12550806
  Xcode:
    version: 16.1/16B40
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.13
    path: /usr/bin/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli":
    installed: 15.1.2
    wanted: latest
  react:
    installed: 18.3.1
    wanted: 18.3.1
  react-native:
    installed: 0.76.3
    wanted: 0.76.3
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: Not found
  newArchEnabled: Not found
iOS:
  hermesEnabled: Not found
  newArchEnabled: Not found
```


### Stacktrace or Logs

```text
No errors in the console
```


### Reproducer

https://snack.expo.dev/@mbackonja/animation-issue

### Screenshots and Videos


https://github.com/user-attachments/assets/195804c8-e187-4221-9df2-3ae8f9838e9e
Repository: material-ui
Issue: [Tooltip] Stays visible when scrolling away
Labels: bug 🐛,component: tooltip,package: material-ui

### Steps to reproduce

Steps:
1. [Open this link to live example](https://stackblitz.com/edit/react-44fyjx?file=LastName.js)
2. Hover over one of the tooltips in the Last Name column
3. Scroll away (without moving the mouse)
4. You'll notice the tooltip stays open


### Current behavior

The tooltip stays open on scroll .

### Expected behavior

The tooltip should close when scrolled away from.

### Context

We are using a tooltip inside of a data grid. When a user hovers the tooltip, we have an api call that happens to populate the it's contents. This call takes milliseconds to complete. When a user hovers the tooltip, and scrolls in the Datagrid, the tool tip stays open even though the user's cursor is no longer hovering the tooltip.

Order ID: 80452

### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.
```
</details>


**Search keywords**: Tooltip, stays open, tooltip hover
Repository: flutter
Issue: Rebuild Autocomplete options at arbitrary time
Labels: a: text input,P2,team-text-input,triaged-text-input

### Use case

When the user finishes typing in the field, a user of Autocomplete might make two network requests: one to quickly fetch some approximate options and another, longer request to get more detailed results. Autocomplete should be able to update the options with the result of each request. Currently the optionsViewBuilder is only called in response to the completion of the future returned by optionsBuilder.

### Proposal

The hacky solution is probably to introduce a controller with a method to imperatively update the options: `AutocompleteController.setOptions`.

A better solution might require a breaking change. Really it seems like maybe the options should just be passed into Autocomplete as a parameter? That would also require the ability to listen to changes in the field.

### Related

There are other request to be able to display things in the options view at certain times, for example while loading: https://github.com/flutter/flutter/issues/147377. Solving this issue would probably also fix that.
Repository: flutter
Issue: Implement WidgetStateProperty Styling for Tab and TabBar Widgets
Labels: c: new feature,framework,f: material design,c: proposal,P3,customer: castaway,team-design,triaged-design

### Use case

In a TabBar, you can control certain visual aspects of the tabs through overlayColor, unselectedLabelStyle, and labelStyle. However, this is a very limiting in what you can do and also doesn't consider other states such as Focused or Disabled. 

### Proposal

My proposal would be to update Tab and TabBar widgets to implement WidgetStateProperty stylings (like FilledButton and many other widgets). This would both allow for a reduced set of properties as well as flexibility in customization for visual states.
Repository: TypeScript
Issue: rewriteRelativeImportExtensions does not rewrite the extension for an import expressions unless the file is detected to be a module
Labels: Needs Investigation

### 🔎 Search Terms

rewriteRelativeImportExtensions, import expression

### 🕗 Version & Regression Information

- This changed between versions 5.7


### ⏯ Playground Link

https://www.typescriptlang.org/play/?rewriteRelativeImportExtensions=true#code/PTAEEsFsAcHsCcAuoDkA6YAzWs2IM4oDcAsAFBRxIAU6WOehAlOUA

### 💻 Code

Test One
```ts
import('./foo.ts')
```
Test Two
```ts
import './foo.ts';
import('./foo.ts')
```


### 🙁 Actual behavior

JS Output

Test One
```ts
import('./foo.ts') // ❌
```
Test Two
```ts
import './foo.js'; // ✅
import('./foo.js') // ✅
```


### 🙂 Expected behavior

JS Output

Test One
```ts
import('./foo.js') // ✅
```
Test Two
```ts
import './foo.js'; // ✅
import('./foo.js') // ✅
```


### Additional information about the issue

_No response_
Repository: kubernetes
Issue: Add configuration property to delete cronjobs if it succeeds after retry
Labels: kind/feature,sig/apps,needs-triage

### What would you like to be added?

Add a boolean cronjob property `deleteFailedJobsOnSuccess` that, when set to `true`, will effectively delete the failed jobs history of that cronjob when it succeeds based on retries dependent on `backoffLimit`.

So e.g. `backoffLimit: 2` and the 1. run fails, but the 2. succeeds, the 1. failed job should not be kept in history.

### Why is this needed?

Sometimes cronjob fail because of temporary issues e.g. database not reachable for short amount of time, then the cronjob succeeds when it automatically runs again, but the failed job is still in the job history.

Setting `failedJobsHistoryLimit: 0` is not a solution as jobs are also not kept when the cronjob fails all the time.

Setting `ttlSecondsAfterFinished` (if possible for cronjobs) is also not a solution as the time is highly dependent on the schedule and has to be calculated to keep a failed job for some time until the next schedule, also the kept failed job might still be unnecessary as the cronjob could have been successful after a direct retry.
Repository: excalidraw
Issue: Arrow navigation in canvas search moves text cursor
Labels: bug

https://github.com/user-attachments/assets/a150489a-fca7-4b10-af40-a33cbe0b2228
Repository: vscode
Issue: Git - Git blame editor decoration appears before the folding ... one
Labels: bug,git

The ... should be before the git one

![Image](https://github.com/user-attachments/assets/8a7704f1-4a36-40db-94b4-4d80d448f9bc)
Repository: svelte
Issue: Svelte 5: Preserve local state during HMR
Labels: feature request

### Describe the bug

With a brand new SvelteKit project with Svelte 5, I realized that all my states are reset whenever HMR updates

Whenever I change anything in the HTML part of a Svelte file, HMR kicks in and resets all my `$state`, which makes it very cumbersome to develop a large and complex form

I read that earlier version support directives such as `@hmr:keep-all` or `preserveLocalState`, but according to https://github.com/sveltejs/kit/issues/12985, these are outdated and no longer used

So I am unsure what to do now to preserve states between HMR reloads - is this a bug or a feature request?

### Reproduction

Reproduction link in SvelteLab: https://www.sveltelab.dev/63iv5zkf3ed2806

Steps to reproduce:
1. Check the checkbox
2. Click the button
3. Change something in the HTML, like adding more text to the paragraph
5. All states get reset - the checkbox gets unchecked, and `text` resets to initial value 🚩

I understand that SvelteLab may not reflect real-world environments, but I tried it on my laptop inside WSL and the "bug" is still there

### Logs

_No response_

### System Info

```shell
System:
    OS: Linux 5.15 Ubuntu 22.04.4 LTS 22.04.4 LTS (Jammy Jellyfish)
    CPU: (8) x64 AMD Ryzen 7 8845HS w/ Radeon 780M Graphics
    Memory: 13.97 GB / 14.90 GB
    Container: Yes
    Shell: 5.1.16 - /bin/bash
  Binaries:
    Node: 23.3.0 - ~/.local/share/mise/installs/node/23/bin/node
    npm: 10.9.0 - ~/.local/share/mise/installs/node/23/bin/npm
    pnpm: 9.14.2 - ~/.local/share/mise/installs/node/23/bin/pnpm
  npmPackages:
    svelte: ^5.1.13 => 5.1.13
```


### Severity

annoyance
Repository: rust
Issue: `avr-rjmp-offset` is flaky on `x86_64-mingw`
Labels: A-LLVM,A-testsuite,T-compiler,O-windows-gnu,C-bug,O-AVR,A-run-make,A-linkers,C-external-bug,I-flaky-test

> This test seems to be failing somewhat often:
>
> * 2024-11-25 Hang: https://github.com/rust-lang/rust/pull/133465#issuecomment-2499233485
> * 2024-11-20 Error: https://github.com/rust-lang/rust/pull/132629#issuecomment-2490054965
> * 2024-11-13 Error: https://github.com/rust-lang/rust/pull/132997
> * 2024-11-08 Error: https://github.com/rust-lang/rust/pull/132757#issuecomment-2465793359
> * 2024-10-26 Error: https://github.com/rust-lang/rust/pull/131527#issuecomment-2439511330
> * 2024-10-23 Error: https://github.com/rust-lang/rust/pull/123550#issuecomment-2434164699

All on `x86_64-mingw`. Can we maybe disable it on `x86_64-mingw` until it is fixed?

_Originally posted by @ehuss in https://github.com/rust-lang/rust/issues/131755#issuecomment-2499254372_

I think the linker is crashing...
Repository: react-native
Issue: Bug in the height of the text input when it is multiline
Labels: Issue: Author Provided Repro,Type: New Architecture

### Description

When specifying the "multiline" and "numberOfLines" properties, the height of the text input acts differently in the new and old architecture.
In the new architecture the height remains the same as if the properties were not specified, while in the old architecture the height increases.

### Steps to reproduce

1. Clone the sample repository.
2. Enable or disable the new architecture.
3. Run "yarn android".
4. Display the text input on the device.

### React Native Version

0.76.3

### Affected Platforms

Runtime - Android

### Areas

Fabric - The New Renderer

### Output of `npx react-native info`

```text
System:
  OS: Windows 11 10.0.22631
  CPU: "(12) x64 AMD Ryzen 5 5600G with Radeon Graphics         "
  Memory: 4.79 GB / 29.79 GB
Binaries:
  Node:
    version: 20.14.0
    path: ~\AppData\Local\Temp\yarn--1732581775916-0.8361455801386266\node.CMD
  Yarn:
    version: 1.22.22
    path: ~\AppData\Local\Temp\yarn--1732581775916-0.8361455801386266\yarn.CMD
  npm:
    version: 10.7.0
    path: C:\Program Files\nodejs\npm.CMD
  Watchman: Not Found
SDKs:
  Android SDK:
    API Levels:
      - "28"
      - "30"
      - "33"
      - "34"
      - "35"
    Build Tools:
      - 30.0.3
      - 33.0.0
      - 34.0.0
      - 35.0.0
      - 35.0.0
    System Images:
      - android-23 | Google APIs Intel x86 Atom
      - android-29 | Google Play Intel x86 Atom
      - android-34 | Google Play Intel x86_64 Atom
    Android NDK: Not Found
  Windows SDK:
    AllowDevelopmentWithoutDevLicense: Enabled
    Versions:
      - 10.0.19041.0
      - 10.0.22000.0
      - 10.0.22621.0
IDEs:
  Android Studio: AI-241.18034.62.2411.12169540
  Visual Studio:
    - 17.10.34928.147 (Visual Studio Community 2022)
Languages:
  Java: 20.0.2
  Ruby: Not Found
npmPackages:
  "@react-native-community/cli":
    installed: 15.0.1
    wanted: 15.0.1
  react:
    installed: 18.3.1
    wanted: 18.3.1
  react-native:
    installed: 0.76.3
    wanted: 0.76.3
  react-native-windows: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: true
iOS:
  hermesEnabled: Not found
  newArchEnabled: Not found
```


### Stacktrace or Logs

```text
It is not necessary, the application does not crash or fail.
```


### Reproducer

https://github.com/cervisebas/react-native-bug-text-input

### Screenshots and Videos

### New Architecture
![new-architecture](https://github.com/user-attachments/assets/1ffff123-6926-40be-9cc0-ded4d644f777)

### Old Architecture
![old-architecture](https://github.com/user-attachments/assets/fcfc85f5-24ac-4674-8af6-6f8b1363ece7)
Repository: svelte
Issue: `$state(undefined)` is typed as never on svelte-check
Labels: types / typescript

### Describe the bug

On a project generated by `create-vite@5.5.5`, running a type check to the following code will get a result that `p` is typed as `never`.

```html
<script lang="ts">
  type Person = { name: string }

  let p: Person | undefined = $state(undefined)

  $effect(() => {
    // load person
    setTimeout(() => {
      p = { name: "bob" }
    }, 1000);
  });

  let displayName = $derived(p?.name ?? "anon") // => Error: Property 'name' does not exist on type 'never'. (ts)
</script>
<div>{ displayName }</div>
```

This is considered a bug because it does not occur when the following changes are made.

```diff
-  let p: Person | undefined = $state(undefined) // NG
+  let p: Person | undefined = $state() // OK
```


### Reproduction

https://github.com/ykrods/svelte-reproduction-state-type

### Logs

```shell
$ npm run check

> svelte-reproduction-state-type@0.0.0 check
> svelte-check --tsconfig ./tsconfig.json && tsc -p tsconfig.node.json


====================================
Loading svelte-check in workspace: /home/ykrods/work/svelte-reproduction-state-type
Getting Svelte diagnostics...

/home/ykrods/work/svelte-reproduction-state-type/src/App.svelte:13:33
Error: Property 'name' does not exist on type 'never'. (ts)

  let displayName = $derived(p?.name ?? "anon")
</script>


====================================
svelte-check found 1 error and 0 warnings in 1 file
```


### System Info

```shell
System:
    OS: Linux 6.10 Manjaro Linux
    CPU: (16) x64 AMD Ryzen 7 5700U with Radeon Graphics
    Memory: 8.43 GB / 14.98 GB
    Container: Yes
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.8.0 - /usr/bin/node
    npm: 10.8.3 - /usr/bin/npm
  Browsers:
    Chromium: 131.0.6778.85
  npmPackages:
    svelte: ^5.1.3 => 5.2.8
```


### Severity

annoyance
Repository: flutter
Issue: Replace use of ATK with accessing AT-SPI directly
Labels: engine,a: accessibility,platform-linux,c: proposal,P2,team-linux,triaged-linux

The Linux embedder currently uses the ATK library to provide accessibility. [GTK4 switched from using this library to accessing AT-SPI directly over D-Bus](https://gitlab.gnome.org/GNOME/gtk/-/commit/c63087a5631e72cd1c45bdc5a41bf605195be64c), this may also be a good more for Flutter as this removes the usage of an old library and removes a complex layer that makes using accessibility complicated. This would be a significant amount of work to implement.
Repository: vscode
Issue: Visual glitches in editor when hardware acceleration is disabled
Labels: bug,linux,editor-rendering,chromium,wayland

<!-- ⚠️⚠️ 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
- OS Version: Debian 12

Visual glitches appear when using enter/backspace keys to create or delete lines in a document, from lines 2-9.
Also, although inconsistent, switching lines using the mouse is laggy when going to a higher column position on another row (below line 10).
These bugs only appear when the --disable-gpu option is set, or the disable-hardware-acceleration option is true.

Steps to Reproduce:

1. Open VS Code in Debian (KDE Plasma as desktop environment, not sure if relevant) with the following options: --unity-launch --enable-features=UseOzonePlatform --ozone-platform=wayland --disable-gpu
2. Create a new document
3. Use enter key and backspace key to create/delete lines. Visual glitches with the cursor should appear, and line numbers may not show up.

(I am on line 3 in the image)
![Image](https://github.com/user-attachments/assets/9f7c42d8-df43-479d-8913-5b8362f08967)
Repository: transformers
Issue: Add support for causal language modeling for `DistilBertModel`
Labels: Feature request

### Feature request

HuggingFace Transformers currently supports causal language modeling (CLM) fine-tuning for BERT using`BertLMHeadModel` [as shown in the docs](https://huggingface.co/docs/transformers/model_doc/bert#transformers.BertLMHeadModel). My request is simply to extend this support to `DistilBertModel`.

### Motivation

I want to use a distilBERT model to initialize a `EncoderDecoderModel`, but I am getting an error message that says it does not support CLM.

```python
from transformers import EncoderDecoderModel

EncoderDecoderModel.from_encoder_decoder_pretrained(
  encoder_pretrained_model_name_or_path="distilbert/distilbert-base-multilingual-cased",
  decoder_pretrained_model_name_or_path="distilbert/distilbert-base-multilingual-cased",
)
```

Here is the error message:

```
ValueError: Unrecognized configuration class <class 'transformers.models.distilbert.configuration_distilbert.DistilBertConfig'> for this kind of AutoModel: AutoModelForCausalLM.
Model type should be one of BartConfig, BertConfig, BertGenerationConfig, BigBirdConfig, BigBirdPegasusConfig, BioGptConfig, BlenderbotConfig, BlenderbotSmallConfig, BloomConfig, CamembertConfig, LlamaConfig, CodeGenConfig, CohereConfig, CpmAntConfig, CTRLConfig, Data2VecTextConfig, DbrxConfig, ElectraConfig, ErnieConfig, FalconConfig, FuyuConfig, GemmaConfig, Gemma2Config, GitConfig, GPT2Config, GPT2Config, GPTBigCodeConfig, GPTNeoConfig, GPTNeoXConfig, GPTNeoXJapaneseConfig, GPTJConfig, JambaConfig, JetMoeConfig, LlamaConfig, MambaConfig, Mamba2Config, MarianConfig, MBartConfig, MegaConfig, MegatronBertConfig, MistralConfig, MixtralConfig, MptConfig, MusicgenConfig, MusicgenMelodyConfig, MvpConfig, NemotronConfig, OlmoConfig, OpenLlamaConfig, OpenAIGPTConfig, OPTConfig, PegasusConfig, PersimmonConfig, PhiConfig, Phi3Config, PLBartConfig, ProphetNetConfig, QDQBertConfig, Qwen2Config, Qwen2MoeConfig, RecurrentGemmaConfig, ReformerConfig, RemBertConfig, RobertaConfig, RobertaPreLayerNormConfig, RoCBertConfig, RoFormerConfig, RwkvConfig, Speech2Text2Config, StableLmConfig, Starcoder2Config, TransfoXLConfig, TrOCRConfig, WhisperConfig, XGLMConfig, XLMConfig, XLMProphetNetConfig, XLMRobertaConfig, XLMRobertaXLConfig, XLNetConfig, XmodConfig.
```

### Your contribution

I'm happy to contribute.
Repository: tensorflow
Issue: Aborted (core dumped) in `RaggedBincount`
Labels: stat:awaiting tensorflower,type:bug,comp:ops,2.17

### Issue type

Bug

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

Yes

### Source

source

### TensorFlow version

tf2.17.0 tf2.16.1

### Custom code

Yes

### OS platform and distribution

Linux Ubuntu 20.04

### Mobile device

_No response_

### Python version

3.11

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

When the value of size is close to the maximum value for the dtype, an integer overflow error will occur in following multiplication calculations.

### Standalone code to reproduce the issue

```shell
import tensorflow as tf

splits = tf.constant([0, 3, 5, 9], dtype=tf.int64)
values = tf.constant(1, shape=[3,3], dtype=tf.int64)
size = tf.constant(6522107765268123892, dtype=tf.int64)
weights = tf.constant(1, shape=[3,3], dtype=tf.float32)
counts = tf.raw_ops.RaggedBincount(splits=splits, values=values, size=size, weights=weights)
```


### Relevant log output

```shell
Status: INVALID_ARGUMENT: Encountered overflow when multiplying 3 with 6522107765268123892, result: -1
Aborted (core dumped)
```