sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: x/tools/go/packages: missing TypesInfo when NeedTypesInfo was set while NeedSyntax & NeedTypes were not
Labels: NeedsDecision,Tools

### Go version

go1.22.7 darwin/arm64

### Output of `go env` in your module/workspace:

```shell
GO111MODULE='on'
GOARCH='arm64'
GOBIN=''
GOCACHE='/Users/xrxtzz/Library/Caches/go-build'
GOENV='/Users/xrxtzz/Library/Application Support/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='arm64'
GOHOSTOS='darwin'
GOINSECURE=''
GOMODCACHE='/Users/xrxtzz/go/pkg/mod'
GONOPROXY='`*.everphoto.cn,git.smartisan.com'
GONOSUMDB='`*.everphoto.cn,git.smartisan.com'
GOOS='darwin'
GOPATH='/Users/xrxtzz/go'
GOPRIVATE='`*.everphoto.cn,git.smartisan.com'
GOPROXY='https://goproxy.cn,direct'
GOROOT='/opt/homebrew/Cellar/go@1.22/1.22.7/libexec'
GOSUMDB='sum.golang.google.cn'
GOTMPDIR=''
GOTOOLCHAIN='local'
GOTOOLDIR='/opt/homebrew/Cellar/go@1.22/1.22.7/libexec/pkg/tool/darwin_arm64'
GOVCS=''
GOVERSION='go1.22.7'
GCCGO='gccgo'
AR='ar'
CC='cc'
CXX='c++'
CGO_ENABLED='1'
GOMOD='/Users/xrxtzz/Documents/code/code_analysis/irfronts/go/go.mod'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -ffile-prefix-map=/var/folders/lk/nhh_2w2n2sv2kdzk75mfbrcr0000gp/T/go-build3609621157=/tmp/go-build -gno-record-gcc-switches -fno-common'
```


### What did you do?

The `NeedTypesInfo` option indicates that `packages.Load` would add `TypesInfo` field to result packages. But it turns out that when `NeedTypesInfo` was used separately from `NeedSyntax` or `NeedTypes`, the `TypesInfo` fields would simply be `nil`.


```go
package main

import (
	"fmt"

	"golang.org/x/tools/go/packages"
)

func main() {
	packs, _ := loadProgramPackageWithTypesInfo("strings")
	fmt.Println(packs[0].TypesInfo)
}

func loadProgramPackageWithTypesInfo(pattern string) ([]*packages.Package, error) {
	cfg := packages.Config{
		Mode: packages.NeedName | packages.NeedFiles | packages.NeedCompiledGoFiles |
			packages.NeedImports | packages.NeedTypesInfo | packages.NeedTypesSizes,
	}
	return packages.Load(&cfg, pattern)
}
```

### What did you see happen?

When `NeedTypesInfo` was used separately from `NeedSyntax` or `NeedTypes`, in LoadMode of packages.Load, the `TypesInfo` fields would simply be `nil`.

### What did you expect to see?

The `TypesInfo` were produced properly.
Repository: react
Issue: [DevTools Bug]: Phantom re-renders on sibling <label> components
Labels: Type: Bug,Status: Unconfirmed,Component: Developer Tools

### Website or app

https://stackblitz.com/edit/react-devtools-bug?file=src%2FApp.jsx

### Repro steps

1. Start profiler
2. Input into "Component with state"
3. Both of "ComponentWithState" and "AnotherReactComponent" were re-rendered will be shown in the report but why?

![image](https://github.com/user-attachments/assets/a62f5168-b986-4ec1-8d99-a8731f7a21ff)


### How often does this bug happen?

Every time

### DevTools package (automated)

_No response_

### DevTools version (automated)

_No response_

### Error message (automated)

_No response_

### Error call stack (automated)

_No response_

### Error component stack (automated)

_No response_

### GitHub query string (automated)

_No response_
Repository: transformers
Issue: GGUF support for BERT architecture
Labels: Feature request

### Feature request

I want to add the ability to use GGUF BERT models in transformers.
Currently the library does not support this architecture. When I try to load it, I get an error TypeError: Architecture 'bert' is not supported.
I have done most of the mapping, with some fields I am having difficulty.
Can anybody help me and provide comments on this feature?
### Motivation

I ran into a problem that I can't use gguf models in RASA(rasa uses standard from_pretrained). So I decided to make BERT support

### Your contribution

That's my extended ggml.py file
```python
GGUF_TENSOR_MAPPING = {
    "bert": {
        "context_length": "max_position_embeddings",
        "block_count": "num_hidden_layers",
        "feed_forward_length": "intermediate_size",
        "embedding_length": "hidden_size",
        "attention.head_cgguf>=0.10.0ount": "num_attention_heads",
        "attention.layer_norm_rms_epsilon": "rms_norm_eps",
        # "attention.causal": "",
        # "pooling_type": "",
        "vocab_size": "vocab_size",
    }
}
 
GGUF_CONFIG_MAPPING = {
    "bert": {
        "context_length": "max_position_embeddings",
        "block_count": "num_hidden_layers",
        "feed_forward_length": "intermediate_size",
        "embedding_length": "hidden_size",
        "attention.head_cgguf>=0.10.0ount": "num_attention_heads",
        "attention.layer_norm_rms_epsilon": "rms_norm_eps",
        # "attention.causal": "",
        # "pooling_type": "",
        "vocab_size": "vocab_size",
    }
}
 
GGUF_TOKENIZER_MAPPING = {
    "tokenizer": {
        # "ggml.token_type_count": "",
        # "ggml.pre": "",
        "ggml.model": "tokenizer_type",
        "ggml.tokens": "all_special_tokens",
        "ggml.token_type": "all_special_ids",
        "ggml.unknown_token_id": "unk_token_id",
        "ggml.seperator_token_id": "sep_token_id",
        "ggml.padding_token_id": "pad_token_id",
        "ggml.cls_token_id": "cls_token_id",
        "ggml.mask_token_id": "mask_token_id",
    },
    "tokenizer_config": {       
        "ggml.unknown_token_id": "unk_token_id",
        "ggml.seperator_token_id": "sep_token_id",
        "ggml.padding_token_id": "pad_token_id",
        "ggml.cls_token_id": "cls_token_id",
        "ggml.mask_token_id": "mask_token_id",
    },
}
```
Repository: neovim
Issue: vim.version.parse: more granular "strict" options
Labels: enhancement,lua

### Problem

I would like to be able to parse versions, such as `1.0.0`, `v1.0.0`, `1.0`, `v1`, which is possible with the default `strict = false` behaviour, but not with `strict = true`.

But I would like it to fail on something that is clearly not a version, such as a git commit sha.

Currently, this is the behaviour:

```
:lua =vim.version.parse("d818fd0624205b34e14888358037fb6f5dc51234")
{
  major = 818,
  minor = 0,
  patch = 0,
  <metatable> = {
    __eq = <function 1>,
    __index = <function 2>,
    __le = <function 3>,
    __lt = <function 4>,
    __newindex = <function 5>,
    __tostring = <function 6>
  }
}
```

### Expected behavior

I'm not sure if there's a good solution to this, but perhaps some options that allow you to fine-tune the strictness would work.

For example,

```lua
---@class vim.version.parse.Opts
---
--- No coercion attempt if `true`...
---@field strict? boolean | vim.version.parse.StrictnessConfig

---@class vim.version.parse.StrictnessConfig
---
---Allow prefixes, such as `v` or `tmux-`.
---@field prefix? boolean | string[]
---
---
---Allow suffixes, such as `-rc1`.
---@field suffix? boolean | string[]
---
---1 allows `1`, 2 allows `1.0`, ...
---@field min_component_count? integer
---
---@field max_component_count? integer
```
Repository: deno
Issue: deno cli helper feature for providing least privilege access to scripts
Labels: permissions,suggestion

When I run a script using deno in the command line for the first time, I get useful prompts to allow or deny access to environment, os, or the network. 

After I run the command successfully first time, I would like deno to provide me with the exact command that has all the privileges I have given with a least-privilege approach to run next time.

For example:

1. Run first time and interactively give permissions
![Screenshot 2024-10-18 at 09 55 10](https://github.com/user-attachments/assets/0178b0b1-f537-4c2c-b3c7-d3fc4ee43264)

2. At the end, deno would suggest the least-privilege command to run the next time. e.g:

Run this using the following command next time:
`deno --allow-env --allow-read=~/.aws/config,~/.aws/credentials --allow-net=example.com:80 run npm:aws-cdk synthesize`
Repository: pytorch
Issue: TeLU activation function
Labels: module: nn,triaged

### 🚀 The feature, motivation and pitch

I want to develop and add TeLU activation function to the PyTorch. Please go through the following paper on why TeLU is useful and potentially useful compared to GeLU.

https://arxiv.org/pdf/2402.02790

https://ieeexplore.ieee.org/document/9301084

### Alternatives

It is a new potential activation function addition

### Additional context

_No response_

cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki
Repository: deno
Issue: `deno run -A npm:create-next-app -e hello-world` does not work
Labels: bug,upstream,node compat

Version: Deno 2.0.2
Error:
```
TypeError: Invalid URL: 'hello-world'
    at getSerialization (ext:deno_url/00_url.js:98:11)
    at new URL (ext:deno_url/00_url.js:405:27)
    at createApp (file:///Users/arnauorriols/Library/Caches/deno/npm/registry.npmjs.org/create-next-app/14.2.15/dist/index.js:30034:29)
    at run (file:///Users/arnauorriols/Library/Caches/deno/npm/registry.npmjs.org/create-next-app/14.2.15/dist/index.js:30528:27)
    at eventLoopTick (ext:core/01_core.js:175:7)
```
Repository: ui
Issue: [bug]: Facing installation issue while installing shadcn in nextjs project in MacOs
Labels: bug

### Describe the bug

I am trying to install shadcn in nextjs project but it is giving an error

npm error A complete log of this run can be found in: /Users/chetanbhoasle/.npm/_logs/2024-10-18T11_24_44_051Z-debug-0.log
chetanbhoasle@chetans-MacBook-Air manager-lead % sudo npx shadcn@latest init        

node:internal/modules/cjs/loader:1140
  const err = new Error(message);
              ^

Error: Cannot find module '@babel/types'
Require stack:
- /Users/chetanbhoasle/.npm/_npx/d66c5096c7023bfb/node_modules/@babel/helper-member-expression-to-functions/lib/index.js
- /Users/chetanbhoasle/.npm/_npx/d66c5096c7023bfb/node_modules/@babel/helper-replace-supers/lib/index.js
- /Users/chetanbhoasle/.npm/_npx/d66c5096c7023bfb/node_modules/@babel/helper-create-class-features-plugin/lib/decorators.js
- /Users/chetanbhoasle/.npm/_npx/d66c5096c7023bfb/node_modules/@babel/helper-create-class-features-plugin/lib/index.js
- /Users/chetanbhoasle/.npm/_npx/d66c5096c7023bfb/node_modules/@babel/plugin-transform-typescript/lib/index.js
    at Module._resolveFilename (node:internal/modules/cjs/loader:1140:15)
    at Module._load (node:internal/modules/cjs/loader:981:27)
    at Module.require (node:internal/modules/cjs/loader:1231:19)
    at require (node:internal/modules/helpers:177:18)
    at Object.<anonymous> (/Users/chetanbhoasle/.npm/_npx/d66c5096c7023bfb/node_modules/@babel/helper-member-expression-to-functions/lib/index.js:5:10)
    at Module._compile (node:internal/modules/cjs/loader:1364:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1422:10)
    at Module.load (node:internal/modules/cjs/loader:1203:32)
    at Module._load (node:internal/modules/cjs/loader:1019:12)
    at Module.require (node:internal/modules/cjs/loader:1231:19) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/Users/chetanbhoasle/.npm/_npx/d66c5096c7023bfb/node_modules/@babel/helper-member-expression-to-functions/lib/index.js',
    '/Users/chetanbhoasle/.npm/_npx/d66c5096c7023bfb/node_modules/@babel/helper-replace-supers/lib/index.js',
    '/Users/chetanbhoasle/.npm/_npx/d66c5096c7023bfb/node_modules/@babel/helper-create-class-features-plugin/lib/decorators.js',
    '/Users/chetanbhoasle/.npm/_npx/d66c5096c7023bfb/node_modules/@babel/helper-create-class-features-plugin/lib/index.js',
    '/Users/chetanbhoasle/.npm/_npx/d66c5096c7023bfb/node_modules/@babel/plugin-transform-typescript/lib/index.js'
  ]
}

Node.js v18.20.4


### Affected component/components

application

### How to reproduce

create a new next js project
install shadcn


### Codesandbox/StackBlitz link

bug

### Logs

_No response_

### System Info

```bash
Mac Os M1 8GB 256SSD
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: godot
Issue: Parser error when using a class_name on a ResourceFormatSaver / ResourceFormatLoader if the class references an autoload
Labels: bug,topic:editor,topic:plugin,needs testing

### Tested versions

Reproducible in:
- 4.2.2 stable
- 4.3 stable
- master (04692d83cb8f61002f18ea1d954df8c558ee84f7)

### System information

Tested on Linux & Windows - any renderer

### Issue description

When making a `ResourceFormatSaver` or `ResourceFormatLoader`, the documentation says they need a `class_name` to be registered as valid loaders / savers. 

If any of these scripts or their dependencies references an autoload, when launching the project, this error appears: `Parser Error: Identifier not found: Autoload`

Removing the class_name removes this error.

The only workaround is to manually call `ResourceSaver.add_resource_format_saver(saver)` at runtime after all the autoloads are parsed and loaded.

If this cannot be fixed for technical reasons, it would be great if the error message referenced the root of the issue, because nothing in the stack trace leads back to the format savers.

### Steps to reproduce

- Create a custom class that calls an Autoload at any point (in its script, or in any of its dependencies)
- Create a `ResourceFormatSaver` (or loader) referencing that custom class
- Add a `class_name` to the ResourceFormatSaver
- Start the project

### Minimal reproduction project (MRP)

[MRP resource saver](https://github.com/user-attachments/files/17434661/mrp_resource_saver.zip)
Repository: rust
Issue: projecting to assoc type of supertrait that is implemented differently for trait object goes wrong
Labels: A-associated-items,I-unsound,C-bug,requires-nightly,T-types,A-trait-objects

<!--
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 tried this code: [playground](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=06b34ccd6cabc944d63ff50b2fdcc472)

```rust
#![feature(ptr_metadata)]

use std::ptr::Pointee;

trait Trait: Pointee {
    fn meta(&self) -> Self::Metadata;
}

impl Trait for () {
    fn meta(&self) {}
}

fn main() {
    let d: &dyn Trait<Metadata = ()> = &();
    let m = d.meta();
    dbg!(m);
}
```

I expected to see this happen: The type of `m` is `()` (or `Trait` is dyn incompatible).

Instead, this happened: The type of `m` is `DynMetadata<dyn Trait<Metadata = ()>>`.

Presumably this affects all traits with `#[rustc_deny_explicit_impl(implement_via_object = false)]` and associated types.

Miri does report UB for this code:

```
error: Undefined Behavior: calling a function with return type () passing return place of type std::ptr::DynMetadata<dyn Trait<Metadata = ()>>
  --> src/main.rs:15:13
   |
15 |     let m = d.meta();
   |             ^^^^^^^^ calling a function with return type () passing return place of type std::ptr::DynMetadata<dyn Trait<Metadata = ()>>
   |
   = help: this indicates a bug in the program: it performed an invalid operation, and caused Undefined Behavior
   = help: see https://doc.rust-lang.org/nightly/reference/behavior-considered-undefined.html for further information
   = help: this means these two types are not *guaranteed* to be ABI-compatible across all targets
   = help: if you think this code should be accepted anyway, please report an issue with Miri
   = note: BACKTRACE:
   = note: inside `main` at src/main.rs:15:13: 15:21
```

### 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.
-->

playground nightly
```
Build using the Nightly version: 1.84.0-nightly

(2024-10-17 3ed6e3cc69857129c1d3)
```

@rustbot label A-trait-objects A-associated-items T-types I-unsound requires-nightly -needs-triage 

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"compiler-errors"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: rust
Issue: Volatile reads and writes on aarch64 sometimes generate instructions not suitable for MMIO in protected VMs
Labels: A-LLVM,A-codegen,T-compiler,C-bug,S-has-mcve,O-AArch64

`core::ptr::write_volatile` and `core::ptr::read_volatile` are documented as being intended to act on I/O memory, i.e. for MMIO. These are indeed widely used by many crates providing drivers for MMIO devices across the ecosystem.

When running in a virtual machine, MMIO must be emulated by the hypervisor. This is done (on aarch64 at least) by having the MMIO region unmapped in the stage 2 page table, which results in a data abort to the hypervisor when the VM attempts to read or write the MMIO region. The hypervisor then decodes the exception syndrome register (`esr_el2`) and uses the fault address register (`far_el2`) to determine which MMIO address is being accessed and perform the appropriate operation in response.

Unfortunately, rustc sometimes compiles `core::ptr::write_volatile` on aarch64 to something like `str w9, [x0], #4`. We've seen this happen particularly since Rust 1.78, but it may be possible with earlier Rust versions too. The problem with this is that this post-addressing mode is performing register writeback (in this case, incrementing `x0` by 4), and so [doesn't set the exception syndrome register](https://developer.arm.com/documentation/ddi0595/2020-12/AArch64-Registers/ESR-EL1--Exception-Syndrome-Register--EL1-?lang=en#fieldset_0-24_0_15-24_24). This prevents the hypervisor from emulating the MMIO access, as it has no way of decoding the instruction syndrome or finding the faulting address.

In an unprotected VM (e.g. regular KVM), it is possible for the VMM to work around this by reading the guest VM's memory to find the relevant instruction, decoding the instruction manually, and finding the MMIO address that way. This has a performance overhead and adds extra complexity. In the case of a protected VM where the host doesn't have access to the guest VM's memory (e.g. protected KVM), this is not possible as the VMM is not able to read the guest VM's memory and so cannot do instruction decoding. There is thus no way to emulate these attempted MMIO accesses in a protected VM on aarch64.

The net result of this is that instructions which perform register writeback (e.g. post-increment addressing modes) are not suitable for MMIO in aarch64 VMs. This is arguably a flaw in the aarch64 architecture, but as that's not feasible to fix at this point it must be fixed in the compiler instead. rustc should therefore avoid generating such instructions for `volatile_read` and `volatile_write` calls.

The only alternative I can see to fixing this in rustc is for every crate which performs MMIO to use inline assembly rather than `volatile_read` / `volatile_write`, but that is not a very feasible or scalable solution.
Repository: PowerToys
Issue: Mini window overlayed on ALL APPLICATIONS
Labels: Issue-Bug,Area-Runner,Needs-Repro

### Microsoft PowerToys version

0.85.1

### Installation method

WinGet

### Running as admin

Yes

### Area(s) with issue?

General

### Steps to reproduce

When you start PowerToys a small but annoying window appears in the top left corner, no matter how many times you reopen the app.
no matter what the application is, it overlays on top of any application [PowerToysReport_2024-10-18-07-22-43.zip](https://github.com/user-attachments/files/17436116/PowerToysReport_2024-10-18-07-22-43.zip)

attached image
![Image](https://github.com/user-attachments/assets/3da39c5f-0b8f-4e36-8cdd-b0f9e917b83c)


### ✔️ Expected Behavior

This is how it looks once i closed the application
![Image](https://github.com/user-attachments/assets/44354cef-95e0-4441-a1fc-5385ff385b71)


### ❌ Actual Behavior

it overlays on top of any application 
![Image](https://github.com/user-attachments/assets/42a977f5-7b22-4cdc-b556-37e0b518cf14)


### Other Software

every software installed on my computer has this windows overlayed
Repository: langchain
Issue: Parsing a dictionary of lists problem
Labels: 🤖:bug,stale

### 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

I want to get "a" as a key in ppp , but code (using Dict) below fails:

 ```
 import os
  from pydantic import BaseModel, Field
  from langchain_openai import ChatOpenAI

  model = ChatOpenAI(model="gpt-4o-mini-2024-07-18", temperature=0.0)

  class A(BaseModel):
    a_1: str
    a_2: str
    r: str

  class B(BaseModel):
    b_1: str
    b_2: str
    r: str
  
  class C(BaseModel):
    ccc:List[A]
    ppp: Dict[str, List[B]]


  structured_llm = model.with_structured_output(C)

  response = structured_llm.invoke(prompt)
```




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

ValidationError: 1 validation error for C
ppp
  Field required [type=missing, input_value={'ccc': [{'a_1': 'Price',...tant to Battery Life'}]}, input_type=dict]
    For further information visit https://errors.pydantic.dev/2.9/v/missing


### Description

I have a code that works:

  import os
  from pydantic import BaseModel, Field
  from langchain_openai import ChatOpenAI

  model = ChatOpenAI(model="gpt-4o-mini-2024-07-18", temperature=0.0)

  class A(BaseModel):
    a_1: str
    a_2: str
    r: str

  class B(BaseModel):
    a: str
    b_1: str
    b_2: str
    r: str
  
  class C(BaseModel):
    ccc:List[A]
    ppp: List[B]

  structured_llm = model.with_structured_output(C)

  response = structured_llm.invoke(prompt)


### System Info

System Information
------------------
> OS:  Linux
> OS Version:  #1 SMP PREEMPT_DYNAMIC Thu Jun 27 21:05:47 UTC 2024
> Python Version:  3.10.12 (main, Sep 11 2024, 15:47:36) [GCC 11.4.0]

Package Information
-------------------
> langchain_core: 0.2.41
> langchain: 0.2.16
> langchain_community: 0.2.17
> langsmith: 0.1.136
> langchain_openai: 0.1.21
> langchain_text_splitters: 0.2.4

Optional packages not installed
-------------------------------
> langgraph
> langserve

Other Dependencies
------------------
> aiohttp: 3.10.10
> async-timeout: 4.0.3
> dataclasses-json: 0.6.7
> httpx: 0.27.2
> jsonpatch: 1.33
> numpy: 1.26.4
> openai: 1.52.0
> orjson: 3.10.7
> packaging: 24.1
> pydantic: 2.9.2
> PyYAML: 6.0.2
> requests: 2.32.3
> requests-toolbelt: 1.0.0
> SQLAlchemy: 2.0.35
> tenacity: 8.5.0
> tiktoken: 0.8.0
> typing-extensions: 4.12.2