sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: tensorflow
Issue: AttributeError: 'tensorflow.python.framework.ops.EagerTensor' object has no attribute '__dlpack__'
Labels: stat:awaiting tensorflower,type:feature,type:others,TF 2.13

### Issue type

Feature Request

### Have you reproduced the bug with TensorFlow Nightly?

No

### Source

source

### TensorFlow version

tf 2.12.0

### Custom code

Yes

### OS platform and distribution

google colab

### Mobile device

_No response_

### Python version

3.10.12

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

it looks like tensorflow tesnors doesn't support `__dlpack__` and `__dlpack_device__` dunders. Not sure, If it's already something down the road map. If not, can we add these dunders to tf tensors to conform array_api_standrads?

### Standalone code to reproduce the issue

```shell
import tensorflow as tf
tensor = tf.constant([1,3,2])
tensor.__dlpack__()
```


### Relevant log output

```shell
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
[<ipython-input-3-016b1ec8a3b2>](https://localhost:8080/#) in <cell line: 1>()
----> 1 tensor.__dlpack__()

[/usr/local/lib/python3.10/dist-packages/tensorflow/python/framework/ops.py](https://localhost:8080/#) in __getattr__(self, name)
    441         np_config.enable_numpy_behavior()
    442       """)
--> 443     self.__getattribute__(name)
    444 
    445   @staticmethod

AttributeError: 'tensorflow.python.framework.ops.EagerTensor' object has no attribute '__dlpack__'
```
Repository: next.js
Issue: Link component does not automatically keep the same language when switching pages in app directory
Labels: bug,Runtime

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: darwin
      Arch: x64
      Version: Darwin Kernel Version 22.5.0: Thu Jun  8 22:22:22 PDT 2023; root:xnu-8796.121.3~7/RELEASE_X86_64
    Binaries:
      Node: 16.14.0
      npm: 8.3.1
      Yarn: 1.22.19
      pnpm: N/A
    Relevant Packages:
      next: 13.4.20-canary.15
      eslint-config-next: 13.4.19
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.2.2
    Next.js Config:
      output: N/A
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

Internationalization (i18n), Middleware / Edge (API routes, runtime)

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/leosollereder/nextI18n

### To Reproduce

To reproduce the bug, you need to follow the official documentation on i18n in the app router:

https://nextjs.org/docs/app/building-your-application/routing/internationalization

### Describe the Bug

The code uses two different languages, "en" and "de", with "de" being the defaultLanguage. 
When switching the language to english, and then using a <Link> component to another page, in the above case "/testsite", it leads me to the "/de/testsite" page, instead of keeping the english version.
Is this the expected/desired behaviour, and do I manually need to add the language to each href in the <Link> components for this to work?

### Expected Behavior

The expected behaviour would be, that upon enabling localization, the language stays the same, even when switching pages, without having to manually add it at the beginning of a href of a <Link>.

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: rust
Issue: Compiler hang when using enum with recursive generic types in From trait implementation
Labels: T-compiler,C-bug,I-hang

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

I encountered a compiler hang when using an enum with recursive generic types in the implementation of the From trait. Below is the code that triggers the issue:
```rust
enum Equation<X, Y> {
   //code
}

impl<X, Y> Default for Equation<X, Y>
where
    X: Default,
{
   //code
}

impl<X, Y, T> From<T> for Equation<Equation<X, Y>, Equation<X, Y>>
where
    T: ToString,
    Equation<X, Y>: From<T>,
    X: Default,
{
    //code
}

```

When attempting to compile this code, the compiler enters an infinite loop and hangs indefinitely. I believe the issue lies in the recursive nature of the generic types used in the From trait implementation.

I would appreciate it if you could investigate this issue and provide guidance💡 on how to resolve it. If there are any workarounds or alternative approaches to achieve the desired behavior, please let me know.😃

I first find this issue on nightly. It is worth mentioning that the provided code snippet causes a hang issue on  the latest stable too.

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```

rustc 1.74.0-nightly (2f5df8a94 2023-08-31)
binary: rustc
commit-hash: 2f5df8a94bb3c5fae4e3fcbfc8ef20f1f976cb19
commit-date: 2023-08-31
host: x86_64-unknown-linux-gnu
release: 1.74.0-nightly
LLVM version: 17.0.0
```
what's more, to get more information,I also tried '-Z -time-passes':
```sh
$rustc -Z time-passes hang_bug.rs 
time:   0.001; rss:   37MB ->   38MB (   +1MB)  setup_global_ctxt
time:   0.003; rss:   38MB ->   53MB (  +15MB)  expand_crate
time:   0.003; rss:   38MB ->   53MB (  +15MB)  macro_expand_crate
error[E0601]: `main` function not found in crate `hang_bug`
  --> hang_bug.rs:22:2
   |
22 | }
   |  ^ consider adding a `main` function to `hang_bug.rs`

time:   0.004; rss:   53MB ->   61MB (   +8MB)  looking_for_entry_point
time:   0.004; rss:   53MB ->   61MB (   +8MB)  misc_checking_1
time:   0.000; rss:   61MB ->   63MB (   +3MB)  type_collecting
^C

```
If you have any suggestions on obtaining more information that can help trace the cause of the hang, I would greatly appreciate it.😉
<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary>Backtrace</summary>
<p>

```
no output
```

</p>
</details>
Repository: godot
Issue: Custom class nodes break when changing inheritance
Labels: discussion,topic:gdscript,topic:editor

### Godot version

v4.1.1.stable.official [bd6af8e0e]

### System information

Windows 10

### Issue description

I have created a custom class (let's call it CustomNode2D)  inheriting Node2D and subsequently created a ton of scenes with that node type. Afterwards i modified the class to inherit Area2D. This leads to the helpful error message 'Script inherits from native type 'Area2D', so it can't be assigned to an object of type 'Node2D'

This can be fixed by opening the scene and "changing" the node type to CustomNode2D. This feels unnecessary, because when hovering the node it correctly shows its Type as CustomNode2D. Perhaps there should be a way to update all scenes with nodes based on a modified class to avoid having to manually click through all these scenes.

### Steps to reproduce

- Create class inheriting Node2D

```
#CustomNode2D.gd
class_name CustomNode2D
extends Node2D
```

- Create scene with root node based on CustomNode2D
- Modify CustomNode2D to inherit another class
```
#CustomNode2D.gd
class_name CustomNode2D
extends Area2D
```
- Run previously created scene 

### Minimal reproduction project

[New Game Project.zip](https://github.com/godotengine/godot/files/12497612/New.Game.Project.zip)
Repository: storybook
Issue: [Bug]: Documents are not very friendly to vue3's tsx rendering, such as slots and events
Labels: bug,needs triage

### Describe the bug

I want it to look like this：
```html
<template>
  <Button text="Button" @click="action('click')">
    Content
  </Button>
</template>
```
but it actually renders like this:
![image](https://github.com/storybookjs/storybook/assets/43991889/e77f392c-ecaf-4e40-ab26-25c7b212a433)

My demo address：https://github.com/MrXwq/vite-vue3-storybook

### To Reproduce

_No response_

### System

```bash
Environment Info:

  System:
    OS: macOS 12.3
    CPU: (8) arm64 Apple M1 Pro
  Binaries:
    Node: 18.15.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 7.24.2 - ~/node_modules/.bin/npm
  Browsers:
    Chrome: 116.0.5845.140
    Safari: 15.4
  npmPackages:
    @storybook/addon-actions: ^7.4.0 => 7.4.0 
    @storybook/addon-essentials: ^7.4.0 => 7.4.0 
    @storybook/addon-interactions: ^7.4.0 => 7.4.0 
    @storybook/addon-links: ^7.4.0 => 7.4.0 
    @storybook/blocks: ^7.4.0 => 7.4.0 
    @storybook/testing-library: ^0.2.0 => 0.2.0 
    @storybook/vue3: ^7.4.0 => 7.4.0 
    @storybook/vue3-vite: ^7.4.0 => 7.4.0
```


### Additional context

_No response_
Repository: rust
Issue: Highlight default enum variant in rustdoc output
Labels: T-rustdoc,C-feature-request

### Problem

Since Rust has introduced `#[default]`, can we hightlight it in the doc?
Like this one:
```
#[derive(Default)]
enum Status {
    #[default]
    Active,
    Inactive,
}
```

For other type of default definition of enums, it can be hard! For example, the following code, can be hard:
```
#[derive(...)]
enum Status {
    Active,
    Inactive,
}

impl Default for Status {
    fn default() -> Self {
        serde::from_str("active").unwrap()
    }
}
```

or:
```
#[derive(...)]
enum Status {
    Active,
    Inactive,
}

impl Default for Status {
    fn default() -> Self {
        if env!("ENV") == "prod" {
            Self::Inactive
        } else {
            Self::Active
        }
    }
}
```
We can ignore these cases.

### Proposed Solution

_No response_

### Notes

_No response_
Repository: storybook
Issue: Editor - tinymce is not defined 
Labels: bug,needs triage

### Describe the bug

![Screenshot 2023-09-01 at 7 11 01 PM](https://github.com/storybookjs/storybook/assets/140604795/3599d4cf-2bad-4022-97ea-ac3424e42eae)

I have tried creating stories for the Editor in tinymce. Even after importing all the files get the above error. Is there any solution to rectify this?

### To Reproduce

_No response_

### System

```bash
at ./node_modules/tinymce/models/dom/model.js (http://localhost:6006/vendors-node_modules_tinymce_models_dom_model_js.iframe.bundle.js:8048:3)
    at options.factory (http://localhost:6006/runtime~main.iframe.bundle.js:687:31)
    at __webpack_require__ (http://localhost:6006/runtime~main.iframe.bundle.js:28:33)
    at fn (http://localhost:6006/runtime~main.iframe.bundle.js:344:21)
    at ./src/compoments/common/AtsEditor/AtsEditor.stories.js (http://localhost:6006/compoments-common-AtsEditor-AtsEditor-stories.iframe.bundle.js:17:82)
    at options.factory (http://localhost:6006/runtime~main.iframe.bundle.js:687:31)
    at __webpack_require__ (http://localhost:6006/runtime~main.iframe.bundle.js:28:33)
    at fn (http://localhost:6006/runtime~main.iframe.bundle.js:344:21)
    at http://localhost:6006/main.iframe.bundle.js:3478:10
```


### Additional context

_No response_
Repository: angular
Issue: Allow locale number formatting to be applied without grouping
Labels: area: common

### Which @angular/* package(s) are relevant/related to the feature request?

@angular/common

### Description

`formatNumber` allows locale formatting which also will group digits with a group separator character, according to the locale.

e.g. 1234 becomes 1,234

However in some circumstances locale formatting may be desirable, to use the correct currency symbol or to use the correct decimal point character - without also grouping the digits.

e.g. calling 
```typescript
import { formatNumber  } from '@angular/common';
...

const value = 1234.5;
const formattedValue = formatNumber(value, 'de-DE', '1.2');

console.log(formattedValue); // this will be 1.234,50 but there is no way to make it 1234,50
```

### Proposed solution

`Intl.NumberFormat` exposes a `useGrouping` option, see https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/NumberFormat/NumberFormat#usegrouping.

This could use a similar solution, e.g. expose a flag higher up as an argument to `formatNumber` to allow grouping to be optionally applied.

### Alternatives considered



Several users have written, or have been advised to write, their own custom logic to strip out the commas afterwards. This seems counter productive and possibly bad advice:

https://itecnote.com/tecnote/angular-removing-comma-from-number-pipe-in-angular2/
https://stackoverflow.com/questions/47992859/removing-comma-from-number-pipe-in-angular2
https://stackoverflow.com/questions/56544851/can-angulars-decimal-pipe-display-4-integer-digits-without-a-comma
https://stackoverflow.com/questions/64132585/how-to-remove-1000-factor-commas-from-currency-pipe-in-angular
Repository: go
Issue: x/pkgsite: remove .gz test files
Labels: pkgsite

Remove, and avoid checking in .gz test files (e.g. tests/screentest/testdata/vulndb-v1/index/db.json.gz), which aren't easy to review.
Repository: flutter
Issue: Block incompatible Xcode version updates to CI
Labels: tool,t: xcode,team-infra,P3,triaged-infra

The Xcode version we use currently in CI is 14.3.1. Xcode 14.3.1 requires macOS 13+. Basically all of our CI bots, though, are on macOS 12.6.

Surprisingly, most everything works despite the incompatibility. However some things, such as opening Xcode, don't work and cause issues.

To mitigate this, we should add presubmit tests or a recipe step that check if the Xcode version is compatible with the macOS version to warn us before upgrading the Xcode version.
Repository: PowerToys
Issue: Run a PowerPoint slideshow in a zone as if on a second monitor
Labels: Needs-Triage

### Description of the new feature / enhancement

Please have PowerPoint be able to view a zone as a display for a slide show to run within. PowerPoint takes control of the entire screen when running a slide show using a single monitor setup, but with the proposed feature, it would run only within a predefined zone. This would enable a user to edit a PowerPoint presentation while simultaneously displaying the running slideshow. 

### Scenario when this would be used?

When collaborating on a slide presentation with clients and colleagues while screen sharing, showing the running slideshow is often helpful when making edits to the file. When using a single monitor setup, one has to stop the slideshow view to make an edit and then restart the presentation to see the changes made. With this proposed enhancement, a designer/presenter could change the file "offscreen/unseen" to the viewers while maintaining the slideshow running.

### Supporting information

_No response_
Repository: angular
Issue: Weird behavior of i18n-tagged strings with SSR
Labels: area: i18n,area: server

### Which @angular/* package(s) are the source of the bug?

localize

### Is this a regression?

Yes

### Description

I have an SSR app that uses `loadTranslations` to avoid building dist files for each locale. More specifically, I [bootstrap the language](https://github.com/aleesaan/angular-i18n-ssr/blob/main/src/app/services/language.service.ts) based on [the request's cookies or headers](https://github.com/aleesaan/angular-i18n-ssr/blob/main/src/app/services/transfer-state.server.service.ts).  
This works well with strings marked with `$localize`, they're always in the correct language ✨ However, for strings marked with `i18n` attributes, the server seems to generate the response once, and then use it for every response thereafter 😢   

So if I run the server, then request the app in French, I will get the first response in French, and then the app bootstraps in the browser, and everything is still in French, great! 🚀 
But! When I then switch to English, the first response will still be in French for strings marked with `i18n`! Then the app bootstraps, and everything is in English correctly. 🤔 

You can check this by pulling and running the [reproduction repo I created](https://github.com/aleesaan/angular-i18n-ssr), following the steps I described above and looking at the first response you get from the server. This happens every time you restart the server, it seems to cache the first response it serves (at least for strings marked with `i18n`).

I've been trying to look in the source code but I don't understand this! Do you know how I can fix it? What's the difference between marking a string with `i18n` vs `$localize`?

### Please provide a link to a minimal reproduction of the bug

https://github.com/aleesaan/angular-i18n-ssr

### Please provide the exception or error you saw

_No response_

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 16.2.1
Node: 16.20.1
Package Manager: npm 8.19.4
OS: darwin arm64

Angular: 
... 

Package                      Version
------------------------------------------------------
@angular-devkit/architect    0.1602.1 (cli-only)
@angular-devkit/core         16.2.1 (cli-only)
@angular-devkit/schematics   16.2.1 (cli-only)
@schematics/angular          16.2.1 (cli-only)
```


### Anything else?

_No response_
Repository: go
Issue: proposal: x/mobile: start using OpenGL ES 3 instead of OpenGL ES 2 on Android
Labels: Proposal,mobile

<!--
Our proposal process is documented here:
https://go.dev/s/proposal-process
-->

Now OpenGL ES 3 is not supported by gomobile-build as it was troublesome to detect whether a device supports GL ES 3 or not (https://github.com/golang/mobile/blob/7088062f872dd0678a87e8986c67992e9c8855a5/gl/work.h#L5-L10).

IMO, it is already safe to assume that most devices support GL ES 3, and we don't have to detect it. One reason is that ES 3 is supported by Android 5 (https://developer.android.com/guide/topics/graphics/opengl).

By this change, gomobile implementation will be slightly simpler.

What do you think?

/CC @hyangah @dmitshur @crawshaw
Repository: vscode
Issue: SCM - Add `scmResourceGroupState` context key
Labels: help wanted,feature-request,scm

Commands contributed to the `scm/resourceState/context` can use the `scmResourceState` context key in their when-clauses to test the value of the `contextValue` property of the `SourceControlResourceState`.

There is no equivalent capability for commands contributed to the `scm/resourceGroup/context` menu. It is only possible to test the read-only `id` property of the `SourceControlResourceGroup`, which is done by checking `scmResourceGroup` in when-clauses.

Our SCM provider uses resource groups more dynamically than the Git provider does, and we want to vary the contents of a group's context menu (and inline command buttons) during its life. We cannot change the group's `id` property to achieve this, and we don't want to destroy and recreate a group in order to do so.

This issue is a feature request for the addition of an optional `contextValue` property on `SourceControlResourceGroup`, which would be exposed as a new context key named `scmResourceGroupState`.

If the proposal is accepted I am willing to prepare a PR.
Repository: PowerToys
Issue: [Image Resizer] Customize preset before resize within the Image Resizer popup
Labels: Needs-Triage

### Description of the new feature / enhancement

Having presets is useful, but choosing the Custom preset only recalls your previously used settings. At times, this is great, but it would also be useful if it were possible to select a preset, then click a button to change to the Custom preset but with its values populated from the clicked preset. This would let you quickly perform a custom resize using a preset as its basis.

### Scenario when this would be used?

Changing a preset that is usually set to Fit for its fit mode, to Fill, for example. With more resize options in the future, this feature could become even more relevant.

### Supporting information

_No response_
Repository: node
Issue: Discussion: In an ESM-first mode, how should extensionless entry points be handled?
Labels: module,esm,wasm,wasi

Building off of https://github.com/nodejs/node/pull/49295#issuecomment-1703017541 and https://github.com/nodejs/node/pull/31415, we’re considering a new mode, probably enabled by flag, where all of the current places where Node defaults to CommonJS would instead default to ESM. One of the trickiest questions to answer for defining such a new mode is how extensionless entry points should be handled.

In an early version of the ESM implementation, extensionless entry points followed the same interpretation of `.js` files; if they were in a `"type": "module"` `package.json` scope, they were run as ESM, otherwise they were run as CommonJS. They couldn’t be referenced via `import`; extensionless support was limited to entry points, to handle the CLI tool use case without complicating the resolution algorithm. https://github.com/nodejs/node/pull/31415 removed this ESM extensionless entry point support because there was desire to someday permit extensionless entry points to be not just ESM JavaScript but also Wasm. We haven’t followed up since.

There is a strong desire from users for the ability to write CLI apps or “shell scripts” using ESM, without needing things like symlinks or CommonJS wrappers in order to enable extensionless entry points being interpreted as ESM. I can think of two potential ways to enable such, which we could limit to being enabled by our new flag:

1. Extensionless is just always ESM in a `"type": "module"` scope (or in this new ESM-first mode, outside of a `"type": "commonjs"` scope). There’s simply no ability for extensionless Wasm entry points; Node.js is a JavaScript runtime, after all. This tracks how there’s also currently no support for extensionless native/`.node`-file entry points.

2. Use the [Wasm magic byte](https://github.com/nodejs/node/pull/49295#issuecomment-1702557447) to disambiguate between Wasm and ESM entry. Either always check for magic byte before trying to parse, or check after failure to parse as ESM JavaScript.

Are there other approaches?

I think we need to find some way to enable this use case, either behind this new “ESM by default” flag or in Node generally. It keeps coming up and the pressure from users will only increase as ESM adoption continues. @LiviaMedeiros @nodejs/loaders @nodejs/wasi @nodejs/tsc