sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: tensorflow
Issue: Update Python in Docker images to 3.11.x and ditch `3.11.0rc1`
Labels: stat:awaiting tensorflower,type:bug,type:build/install,TF 2.18

### Issue type

Build/Install

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

Yes

### Source

binary

### TensorFlow version

2.18

### Custom code

No

### OS platform and distribution

Docker

### Mobile device

_No response_

### Python version

_No response_

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

The Python version of the docker images is outdated and should be updated

### Standalone code to reproduce the issue

```shell
docker run -it tensorflow/tensorflow python
```


### Relevant log output

```shell
Python 3.11.0rc1 (main, Aug 12 2022, 10:02:14) [GCC 11.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>
```
Repository: godot
Issue: Enum does not update in resource on change it needs restart to update
Labels: bug,topic:gdscript,topic:editor

### Tested versions

Reproducible in:
4.4Dev-3
4.4Dev-4
4.4Dev-5
4.4Dev-6

### System information

Linux Manjaro, Nvidia Geforce GTX 850, CPU: intel i7

### Issue description

when in resource you place a enum as typed variable you may choose the enums that are written like:

```gdscript
enum example{
    one,
    two,
    three,
}
```

all works well
but if you add "four" you won't see it in the resources
you need to restart the godot and wala there it is

so each time you add an enums or change names you need to restart the godot to take effect

### Steps to reproduce

1. create node with variable (array) that contains resources
2. create resource and attach it
3. add enum variable in resource
4. add enum variable
5. and try to set it in node at first step -> it's array (any one) -> it's enum variable

it's not there

6. restart godot

it's there.

### Minimal reproduction project (MRP)

N/A
Repository: kubernetes
Issue: Audit log file mode
Labels: kind/feature,needs-triage,wg/structured-logging

### What would you like to be added?

I want to be able to configure access rights to the audit logs file. Now the rights are written right in the code, and this is 600

https://github.com/kubernetes/kubernetes/blob/master/vendor/gopkg.in/natefinch/lumberjack.v2/lumberjack.go

### Why is this needed?

Complete with the rotation of the audit logs file and the fact that the kube api server (usually) runs from under the "root" of the user, only root can read the audit log file (file permissions are 0600). This makes it difficult for an unprivileged process to deliver logs to external systems.
Repository: PowerToys
Issue: Black Screen Happens on opening PowerToys setting
Labels: Issue-Bug,Product-Settings,Needs-Triage

### Microsoft PowerToys version

0.86.0

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

Settings

### Steps to reproduce

1. Double click to open PowerToys setting on system tray (or left-click on system tray for quick setting)
2. Black screen happens
![Image](https://github.com/user-attachments/assets/f5c31348-6c31-4c9b-b040-941a2a1da951)

Log attached
- [PowerToysReport_2024-12-09-23-39-53.zip](https://github.com/user-attachments/files/18063119/PowerToysReport_2024-12-09-23-39-53.zip)


### ✔️ Expected Behavior

- open setting window

### ❌ Actual Behavior

- Black Screen is shown

### Other Software

Windows 11 23H2 (22631.4541)
Repository: node
Issue: Test concurrency causes the Test Runner to report a wrong isTTY value
Labels: question

another one for the test runner:

### Description

Using `child_process` for test parallisation also sets `process.stdout.isTTY` to `undefined`.


The following returns `undefined` when it's run with `node --test`:

```bash
# node --test example.test.js
console.log(process.stdout.isTTY)
# undefined
```

when it's run with plain node, it's `true`:

```bash
# node example.test.js
console.log(process.stdout.isTTY)
# true
```

I had a very faint memory of a similar issue described by someone else, 
very similar to this and IIRC about the `child_process`.

So, I run the same with `--experimental-test-isolation=none` and there it is: it returns `true` which confirms my suspicions.

```bash
# node --test --experimental-test-isolation=none example.test.js
console.log(process.stdout.isTTY)
# true
```


Although you can work around it, it's very problematic for the following reasons:


- It's inconsistent with [POLA](https://en.wikipedia.org/wiki/Principle_of_least_astonishment) 
- It' inconsistent with it's *own* API because it reports one way with one flag, and another without. 
- It leaks implementation details

How the tests are run is an *implementation detail* that shouldn't be leaking like that.  
I'm sure there are some valid reasons for it but this feels plain wrong.

Thoughts?


**Note:** I only *suspect* these 2 issues are related.
Repository: go
Issue: proposal: os: add ReparsePointTag
Labels: OS-Windows,Proposal

### Proposal Details

Windows applications might need to know the [reparse point tag](https://learn.microsoft.com/en-us/windows/win32/fileio/reparse-point-tags) of a given `os.FileInfo`. Although the  Windows implementation of `os.FileInfo` knows the reparse point tag, there is no way to get that information using the public `os` API. This means that applications are forced to partially reimplement `os.Lstat` by opening the file and calling `GetFileInformationByHandleEx`.

I propose to add the following helper function to the `os` package:

```go
// ReparsePointTag returns the the reparse point tag associated with fi.
//
// ReparsePointTag only applies to results returned by this package's [LStat].
// fi must be associated with a reparse point.
// Otherwise, ReparsePointTag returns false.
func ReparsePointTag(fi FileInfo) (uint32, bool)
```

The `ReparsePointTag` implementation could be made more `os`-agnostic by also defining an interface that external `os.FileInfo` implementations could implement to get the reparse point tag. This might be an overkill for now, as reparse points are not a broadly-addopted concept outside NTFS file systems.

`ReparsePointTag` would only be useful on Windows for now, although it could potentially be implemented on other OSes supporting NTFS drivers.

@golang/windows
Repository: go
Issue: x/tools/cmd/goimports,gopls: avoid deprecated symbols and/or packages
Labels: gopls,gopls/imports

Skimming the codebase, it look like we don't consider API deprecation in goimports. That is surprising.

We should avoid deprecated symbols and packages as import candidates.

Edit: context is golang/go#70717, where a user imported x/exp/maps by accident. (Though, will note that x/exp/maps is not currently deprecated).

CC @pjweinb
Repository: go
Issue: proposal: go/types: add Select function
Labels: Proposal

**Background:** The type checker has two different APIs for the same concept, namely information about a selection of a field or method:
- `Info.Selections` and `MethodSet` both use the record type `Selection`;
- `LookupFieldOrMethod` returns a triple, (obj, indices, indirect).

There is no way to construct a `Selection` from the result of `LookupFieldOrMethod`. Especially when operating in parallel on the method sets of two types, it is a perennial nuisance that these corresponding items have different forms.

**Proposal:** We propose a function, `Select`, to bridge this gap.

```go
package types

// Select selects the field or method whose ID is Id(pkg, name), on a value of type recv.
// See LookupFieldOrMethod for more detail.
func Select(recv Type, addressable bool, pkg *Package, name string) (Selection, bool) {
	obj, index, indirect := LookupFieldOrMethod(recv, addressable, pkg, name string)
	var kind SelectionKind 
	switch obj {
	case *types.Func:
		kind = MethodVal
	case *types.Var:
		kind = FieldVal
	}
	return Selection{kind, recv, obj, index, indirect}, obj != nil
}
```

Related:
- https://github.com/golang/go/issues/10091: Closed because it was a rename; this issue proposes an addition.
- https://github.com/golang/go/issues/12881: superseded by this issue. Also, we have never observed a need for NewSelection other than the one above.

@findleyr @griesemer @timothy-king
Repository: next.js
Issue: Webpack failing to use correct node loader in yarn workspace
Labels: bug,Webpack

### Link to the code that reproduces this issue

https://github.com/snspinn/yarn-workspace-nextjs

### To Reproduce

Note: The following step will need rust installed:

1. Clone `https://github.com/snspinn/yarn-workspace-nextjs`
2. Run `yarn install` at top level
3. Build napi-rs package:
   - `cd libraries/server-package`
   - `yarn install && yarn build`
4. Build next app:
   - `cd ../../app/my-app`
   - `yarn install && yarn next build`

### Current vs. Expected behavior

I would expect it to just load the module. It works when using the `file:` protocol. However, this is a less than ideal workaround as it has other knock on affects (https://github.com/yarnpkg/berry/issues/6550, https://github.com/yarnpkg/berry/issues/3972).
Current behavior is that the build fails with a Module parse/loader error. 


```
➤ YN0000: · Yarn 4.5.3
➤ YN0000: ┌ Resolution step
➤ YN0000: └ Completed
➤ YN0000: ┌ Fetch step
➤ YN0000: └ Completed in 0s 526ms
➤ YN0000: ┌ Link step
➤ YN0031: │ One or more node_modules have been detected and will be removed. This operation may take some time.
➤ YN0000: │ ESM support for PnP uses the experimental loader API and is therefore experimental
➤ YN0000: └ Completed
➤ YN0000: · Done with warnings in 0s 888ms
   ▲ Next.js 15.0.4

   Creating an optimized production build ...
Failed to compile.

../../libraries/server-package/server-package.linux-x64-gnu.node
Module parse failed: Unexpected character '' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)

Import trace for requested module:
../../libraries/server-package/server-package.linux-x64-gnu.node
../../libraries/server-package/index.js
./src/app/api/server-package/route.ts


> Build failed because of webpack errors
```

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #49~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Nov  6 17:42:15 UTC 2
  Available memory (MB): 31960
  Available CPU cores: 8
Binaries:
  Node: 20.14.0
  npm: 9.9.3
  Yarn: 4.5.3
  pnpm: N/A
Relevant Packages:
  next: 15.0.4
  eslint-config-next: N/A
  react: 19.0.0
  react-dom: 19.0.0
  typescript: N/A
Next.js Config:
  output: standalone
```


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

Developer Experience, Webpack

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

next dev (local), next build (local)

### Additional context

Had been getting this error since v14 therefore have not tested with any canary releases. Was waiting to see if `serverComponentsExternalPackages` becoming stable would solve it.
Repository: react-native
Issue: Auto Completion is not working for Phone Number
Labels: Needs: Repro,Newer Patch Available,Needs: Attention

### Description

 have a text Input inside a form to ask the user to register. the issue is the keyboard suggestions to fill the phone number is not showing for unknown reasons.

Does anyone have this issue before and how it can be solved?

P.S: I tried to play with the Keyboard type and with autoComplete type and with textContentType, but nothing work


<InputComponent
                    key={'phoneNumber'}
                    label={'phone number'}                    onChangeText={handleChange('phoneNumber')}
                    value={values.phoneNumber}
                    onBlur={handleBlur('phoneNumber')}
                  // 
                    autoComplete={'tel'}
                    blurOnSubmit={false}
 
                    autoCapitalize={'none'}
                    keyboardType={'number-pad'}
                    textContentType="telephoneNumber"                  
                />

![image](https://github.com/user-attachments/assets/e92131d9-9b15-4b6e-9e0e-0f728649a1ef)




### Steps to reproduce

- Just using a Text Input in React Native, doesn't auto suggestion completion

usually in other app u find your phone number suggested and show the suggestions keyboard

### React Native Version

0.74.1

### Affected Platforms

Runtime - iOS

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

```text
..
```


### Stacktrace or Logs

```text
..
```


### Reproducer

..

### Screenshots and Videos

![image](https://github.com/user-attachments/assets/f68169d3-6e7a-471e-84a7-c43b55f05153)
Repository: flutter
Issue: Firebase tests are retried when the failure is that no tests were run
Labels: platform-android,team-infra,P2,triaged-infra

While investigating a failing pull request I discovered that our recipe code retries firebase failures when no tests are identified by firebase. This bug tracks identifying if those results have a signature or result that we can detect and not retrying those failures. The reason firebase gives a failure is that we are being billed for something that in theory is not giving us results. Retrying can't fix the issue. 

https://ci.chromium.org/ui/p/flutter/builders/try/Linux_android%20android_device_tests_shard_1%20master/12743/overview

<img width="565" alt="Screenshot 2024-12-09 at 10 09 09 AM" src="https://github.com/user-attachments/assets/6427524f-1e4d-4866-9617-bafcd5cdf357">

https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8729261023562739057/+/u/Run_package_tests/Firebase_Test_Lab/stdout

```
More details are available at [ https://console.firebase.google.com/project/flutter-infra-staging/testlab/histories/bh.2128561b4a3def3d/matrices/4897799301081527082 ].
┌─────────┬────────────────────────┬────────────────────┐
│ OUTCOME │    TEST_AXIS_VALUE     │    TEST_DETAILS    │
├─────────┼────────────────────────┼────────────────────┤
│ Failed  │ panther-33-en-portrait │ Test failed to run │
└─────────┴────────────────────────┴────────────────────┘
Test failure for example/integration_test/shared_preferences_test.dart after 2 attempts
```
Repository: pytorch
Issue: Support int step for nonfused optimizer implementations
Labels: module: optimizer,low priority,triaged,actionable

### 🚀 The feature, motivation and pitch

An actionable (though lower priority) followup from the discussion here https://github.com/pytorch/pytorch/issues/127197.

While it may be nice to have support for this, a very easy workaround is to use float for step.

### Alternatives

_No response_

### Additional context

_No response_

cc @vincentqb @jbschlosser @albanD @crcrpar
Repository: pytorch
Issue: Add a linter for Docker images which are not included in docker-builds.yml
Labels: module: ci,triaged,needs design

This is a common miss when adding a new Docker image to not add it into docker-builds.yml.  For example, https://github.com/pytorch/pytorch/pull/140733 added `pytorch-linux-focal-cuda12.4-cudnn9-py3.13-gcc9-inductor-benchmarks` for 3.13, but didn't add it into docker-builds.yml.  Its build worked because the `calculate-docker-image` would try to build the image itself and that would continue for a long time till someone notice the higher build time.

Having a linter would make sure that the new Docker image is built and pushed to ECR correctly instead of being rebuilt in all related CI jobs.

cc @seemethere @malfet @pytorch/pytorch-dev-infra
Repository: neovim
Issue: vim.fn.system not working in a windows Git bash/zsh environment
Labels: bug,platform:windows

### Problem

Usage of vim.fn.system will error with '/usr/bin/bash: /s: No such file or directory'
Also, simple `:!ls` does not work.

Ultimately, neovim runs `$SHELL /s /c cmdline`. As SHELL is bash/zsh, the error occurs.

Resolve this by apply '/s /c' options only to a white-list of known windows shells.

### Steps to reproduce

install neovim with winget
install official git for windows, which provides a bash environment
run neovim in this bash environment

### Expected behavior

vim.fn.system('ls') and `:!ls` should work.

### Nvim version (nvim -v)

0.10.2

### Vim (not Nvim) behaves the same?

No. vim `:!ls` works

### Operating system/version

Windows 11

### Terminal name/version

Wezterm

### $TERM environment variable

not relevent

### Installation

winget neovim
Repository: rust
Issue: min_generic_const_args: Braced paths should forbid infer vars
Labels: T-compiler,A-const-generics,F-min_generic_const_args

We should ensure that `Foo<{ BAR }>`   is treated the same as `Foo<BAR>` when ` BAR` has generic parameters (i.e. it should error in both cases).
Repository: vscode
Issue: (Web, Safari) Copying and pasting line with colon and no leading space results in URL encoding of pasted text
Labels: bug,help wanted,editor-clipboard,ios-ipados

<!-- ⚠️⚠️ 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: Web
- OS Version: iPadOS 18.1 (Safari)

VSCode Web on iPadOS/Safari appears to be erroneously encoding certain copied text as a URL.

So copying this string of text from a VSCode Web file:
`foo: bar`

And pasting it into another VSCode web file will result in:
`foo:%20bar`

This is only the case if there isn’t a space before the colon anywhere on the line. So,
` foo: bar` and `foo bar: baz` both copy and paste normally.

This also only happens within VSCode web. So, copying `foo: bar` from an external app and pasting it into VSCode Web or copying `foo: bar` from VSCode web into another app both work fine.

I have not been able to reproduce this on VSCode Web on Mac or Windows. 


Steps to Reproduce:

1. On iPadOS on Safari, open a new file on VSCode Web (or Github Codespaces)
2. Write text `foo: bar`
3. Copy to clipboard, where the first character of selection is NOT whitespace
4. Paste into same file.

https://github.com/user-attachments/assets/0dca81bb-fee2-4623-9ed4-0441ff70231e
Repository: rust
Issue: Unhelpful diagnostic on `=` to `:` typo mentioning return type notation
Labels: A-diagnostics,T-compiler,D-confusing

### Code

```Rust
let x: Vec::new();
```

### Current output

```
error: return type notation arguments must be elided with `..`
 --> src/main.rs:2:20
  |
2 |     let x: Vec::new();
  |                    ^^ help: add `..`: `(..)`

error: return type notation not allowed in this position yet
 --> src/main.rs:2:12
  |
2 |     let x: Vec::new();
  |            ^^^^^^^^^^
```


### Rationale and extra context

This is a mistake where `:` was used instead of `=`. Instead of telling the user that it talks about rtn.

### Rust Version

```Shell
stable and latest nightly.
rustc 1.85.0-nightly (a2545fd6f 2024-11-28)
```

### Anything else?

@rustbot label +D-invalid-suggestion
Repository: langchain
Issue: langchain 0.3.10 does not support langsmith >=0.2.0
Labels: investigate

### Checked other resources

- [X] I added a very descriptive title to this issue.
- [X] I searched the LangChain documentation with the integrated search.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I am sure that this is a bug in LangChain rather than my code.
- [X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

### Example Code

The latest versions of langchain and langsmith and not compatible. I am needing to use langsmith version `0.1.147`

```
langchain>=0.3.10
langsmith==0.2.1
```

### Error Message and Stack Trace (if applicable)

The conflict is caused by:
    The user requested langsmith==0.2.1
    langchain 0.3.10 depends on langsmith<0.2.0 and >=0.1.17
    The user requested langsmith==0.2.1
    langchain 0.3.10 depends on langsmith<0.2.0 and >=0.1.17

### Description

I am trying to use langchain version `0.3.10` with langsmith `0.2.1` but langchain requires langsmith to be version 0.2.0 or below

### System Info

System Information
------------------
> OS:  Windows
> OS Version:  10.0.22631
> Python Version:  3.13.1 (tags/v3.13.1:0671451, Dec  3 2024, 19:06:28) [MSC v.1942 64 bit (AMD64)]

Package Information
-------------------
> langchain_core: 0.3.22
> langchain: 0.3.10
> langsmith: 0.1.147
> langchain_anthropic: 0.3.0
> langchain_google_genai: 2.0.6
> langchain_openai: 0.2.11
> langchain_text_splitters: 0.3.2
> langchain_weaviate: 0.1.0.dev1

Optional packages not installed
-------------------------------
> langserve

Other Dependencies
------------------
> aiohttp: 3.11.9
> anthropic: 0.40.0
> async-timeout: Installed. No version info available.
> defusedxml: 0.7.1
> filetype: 1.2.0
> google-generativeai: 0.8.3
> httpx: 0.27.0
> jsonpatch: 1.33
> langsmith-pyo3: Installed. No version info available.
> numpy: 1.26.4
> openai: 1.57.1
> orjson: 3.10.12
> packaging: 24.2
> pydantic: 2.10.3
> PyYAML: 6.0.2
> requests: 2.32.3
> requests-toolbelt: 1.0.0
> simsimd: 6.2.1
> SQLAlchemy: 2.0.36
> tenacity: 9.0.0
> tiktoken: 0.8.0
> typing-extensions: 4.12.2
> weaviate-client: 4.9.6
Repository: flutter
Issue: enable ASAN for impeller_unittests and impeller_golden_tests on macos ci
Labels: P2,e: impeller,team-engine,triaged-engine

Spawned from https://github.com/flutter/engine/pull/57015

There is a `--asan` flag in GN.  If you set it it will compile the binaries with the correct flags.  The impeller targets will fail to compile though because `flatc` will fail to execute.  Clang on macos links a runtime library ( `libclang_rt.asan_osx_dynamic.dylib` ) that isn't available to dyld without some sort of change.  I'm not sure what mechanisms GN has to run otool to edit the linkage.