sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: ui
Issue: [bug]: Data Table Sorting Highlight
Labels: bug

### Describe the bug

The data table sorting highlight does not go to line 29, when it should be. This has caused me issues when following the (excellent) data table guide.

### Affected component/components

Data Table

### How to reproduce

1. Go to [data table sorting](https://ui.shadcn.com/docs/components/data-table#sorting)
2. Navigate to the 29th line of the first step.

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Mac, Arc
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: deno
Issue: request: option to specify target system in `deno install`
Labels: feat,install

Split from https://github.com/denoland/deno/issues/26180#issuecomment-2433670599.

Currently, `deno install` only downloads packages for the current system. This is good, as we would be wasting space (and bandwidth) downloading resources for systems that aren't in use. For instance, this way `esbuild` only pulls the binary for the system you're running, instead of 25 binaries to cover every possible system.

If you're cross-compiling for `deno compile`, however, then it would be nice to be able to `deno install` the packages for the target system.

To support that, we could add a `--target` option to `deno install`, mirroring `deno compile`. This would allow you to set the target system to cache packages for.

The only caveat I can think of is that it might interact weirdly with postinstall scripts.
Repository: node
Issue: console.group and console.groupCollapsed should write to stderr
Labels: wontfix,console

### Version

all

### Platform

```text
all
```


### Subsystem

console

### What steps will reproduce the bug?

Given the program `console-group.js`
```js
console.group('group');
console.groupCollapsed('group collapsed');
```
run
```sh
node console-group.js 2>/dev/null
```


### How often does it reproduce? Is there a required condition?

consistently, all versions

### What is the expected behavior? Why is that the expected behavior?

The above command should produce no output. This prevents a diagnostic from inadvertently interleaving text in parsable stdout.

One could argue the same should apply to `console.log` and `console.info` and that all machine readable program output should be written to `process.stdout` explicitly, but that ship has sailed.

### What do you see instead?

Send group labels to stderr.

### Additional information

_No response_
Repository: vscode
Issue: Add line number interval setting
Labels: feature-request

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
As described in #37120, I would like to request to add a line number interval setting.

User alexdima suggested that there was too little interest in the feature by looking at a number of vote on another feature which is the base feature ( that sticks the line number interval at 10: #36981). I believe this most probably understates the number of silent users that might find this hard-coded 10 unadjusted to their workspace preferences, but have better things to do than report the feature to change it.
Repository: flutter
Issue: [web] Remove Clipboard API fallback
Labels: engine,platform-web,P2,c: tech-debt,team-web,triaged-web

The web engine has some logic to be able to copy-paste content from a Flutter app, which is using a now outdated/deprecated API ([`document.execCommand`](https://developer.mozilla.org/en-US/docs/Web/API/Document/execCommand)) as a [fallback](https://github.com/flutter/engine/blob/0b56cb8de79e28c4bb58e98129011ca7e684e12e/lib/web_ui/lib/src/engine/clipboard.dart#L225-L233) for browsers that didn't implement the standard API.

We only use the following methods from the standard Clipboard API:

* [writeText](https://developer.mozilla.org/en-US/docs/Web/API/Clipboard/writeText), to put content into the users' clipboard (widely available, since Safari 13.4 (~March 2020))
* [readText](https://developer.mozilla.org/en-US/docs/Web/API/Clipboard/readText), to read content from the users' clipboard (widely available, since Firefox 125 (~April 2024))

It seems that *soon* we'll be able to remove the `execCommand` fallback, and all the scaffolding to make it work.

See `ExecCommand*` strategy classes here: 

* https://github.com/flutter/engine/blob/0b56cb8de79e28c4bb58e98129011ca7e684e12e/lib/web_ui/lib/src/engine/clipboard.dart

(PS: We should also remove the `execCommand` definition from the engine's `dom.dart`!)

---

Closes: https://github.com/flutter/flutter/issues/48581
Repository: langchain
Issue: DallEAPIWrapper not support base_url setting which supported by OpenAI sdk.
Labels: 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

OpenAI sdk support base_url:
```
client = OpenAI(base_url=URL)

response = client.images.generate(
```

but DallEAPIWrapper not support base_url.


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

_No response_

### Description

OpenAI sdk support base_url:
```
client = OpenAI(base_url=URL)

response = client.images.generate(
```

but DallEAPIWrapper not support base_url.

### System Info

System Information
------------------
> OS:  Darwin
> OS Version:  Darwin Kernel Version 24.0.0: Tue Sep 24 23:35:10 PDT 2024; root:xnu-11215.1.12~1/RELEASE_ARM64_T6031
> Python Version:  3.12.2 | packaged by conda-forge | (main, Feb 16 2024, 20:54:21) [Clang 16.0.6 ]

Package Information
-------------------
> langchain_core: 0.3.12
> langchain: 0.3.4
> langchain_community: 0.3.3
> langsmith: 0.1.129
> langchain_anthropic: 0.2.3
> langchain_huggingface: 0.1.0
> langchain_ollama: 0.2.0
> langchain_openai: 0.2.3
> langchain_text_splitters: 0.3.0
> langgraph: 0.2.39

Optional packages not installed
-------------------------------
> langserve

Other Dependencies
------------------
> aiohttp: 3.10.10
> anthropic: 0.36.2
> async-timeout: 4.0.3
> dataclasses-json: 0.6.7
> defusedxml: 0.7.1
> httpx: 0.27.2
> huggingface-hub: 0.25.2
> jsonpatch: 1.33
> langgraph-checkpoint: 2.0.1
> langgraph-sdk: 0.1.33
> numpy: 1.26.4
> ollama: 0.3.3
> openai: 1.52.1
> orjson: 3.10.7
> packaging: 24.1
> pydantic: 2.9.2
> pydantic-settings: 2.6.0
> PyYAML: 6.0.2
> requests: 2.32.3
> sentence-transformers: 3.2.1
> SQLAlchemy: 2.0.36
> tenacity: 8.5.0
> tiktoken: 0.8.0
> tokenizers: 0.20.1
> transformers: 4.45.2
> typing-extensions: 4.12.2
Repository: excalidraw
Issue: Setting the default save path in the settings
Labels: enhancement

Setting the default save path in the settings.
Or selecting the path when saving and remembering it for future saves.
The current version saves only to the default Download folder mixed with other files.
Repository: rust
Issue: Higher-ranked trait bounds in function signature incorrectly require bounds on the impl
Labels: A-trait-system,A-associated-items,C-bug,T-types,fixed-by-next-solver,A-higher-ranked

### Description:

When using higher-ranked trait bounds (HRTBs) in a method signature, the compiler throws an error suggesting that the bounds should be moved to the impl block, even though the function-specific bound should be sufficient.

### Expected behavior:

The function-specific bound should be enough, and the implementation should compile without moving the bound to the impl block.

### Actual behavior:

The compiler throws an error, requiring the bound to be placed on the impl block instead of just the method, even though the method-specific bound should work.

### Example code

```
impl <T:Base>Base for Wrapper<T>{
	type E=T::E;
}
impl <T:Trait<U>,U:Base>Trait<U>for Wrapper<T>{
	fn requires_ref_add_and_assign(&self,u:&U) where for<'a>U::E:AddAssign<<&'a T::E as Add<&'a U::E>>::Output>,for<'a>&'a T::E:Add<&'a U::E>{

	}
}
struct Wrapper<T:Base>(T);
trait Base{
	type E;
}
trait Trait<U:Base>:Base{
	fn requires_ref_add_and_assign(&self,u:&U) where for<'a>U::E:AddAssign<<&'a Self::E as Add<&'a U::E>>::Output>,for<'a>&'a Self::E:Add<&'a U::E>;
}
use std::ops::{Add,AddAssign};
```

### Compiler output

```
error[E0277]: cannot add `&'a <U as Base>::E` to `&'a <T as Base>::E`
  --> src/main.rs:12:2
   |
12 |     fn requires_add(&self,u:&U) where for<'a>U::E:AddAssign<<&'a T::E as Add<&'a U::E>>::Output>,for<'a>&'a T::E:Add<&'a U::E>{
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ no implementation for `&'a <T as Base>::E + &'a <U as Base>::E`
   |
   = help: the trait `for<'a> Add<&'a <U as Base>::E>` is not implemented for `&'a <T as Base>::E`
help: consider introducing a `where` clause, but there might be an alternative better way to express this requirement
   |
11 | impl <T:Trait<U>,U:Base>Trait<U>for Wrapper<T> where for<'a> &'a <T as Base>::E: Add<&'a <U as Base>::E>{
   |                                                +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
```

### Workaround:

Moving the bounds to the impl block works, but function-specific bounds should work without requiring this. Since I can't do that in my actual use case, I've made alternative operation traits. 

### Meta

`rustc --version --verbose`:
```
rustc 1.80.1 (3f5fd8dd4 2024-08-06) (Arch Linux rust 1:1.80.1-1)
binary: rustc
commit-hash: 3f5fd8dd41153bc5fdca9427e9e05be2c767ba23
commit-date: 2024-08-06
host: x86_64-unknown-linux-gnu
release: 1.80.1
LLVM version: 18.1.8
```

</p>
</details>
Repository: tauri
Issue: [feat] IOS/Android SafeArea control
Labels: type: feature request

### Describe the problem

Hello everyone, I've encountered a problem while developing an iOS app. An annoying white titlebar appeared at the top of the screen and on both left and right on landscapre mode. 

![зображення](https://github.com/user-attachments/assets/a7b13912-c328-49ff-94eb-bd3abad53042)

Most likely, the issue is related to this: https://developer.apple.com/documentation/swiftui/view/ignoressafearea(_:edges:)

If that's the case, it might be useful to implement a feature in Tauri that allows control over this parameter.

### Describe the solution you'd like

Now swiftUI offers a function to disable it, it would be nice to have something similar in Tauri.

```swift
struct ContentView: View {
    var body: some View {
        NavigationView {
            ZStack {
                LinearGradient(
                    colors: [.red, .yellow],
                    startPoint: .topLeading,
                    endPoint: .bottomTrailing
                )
                .ignoresSafeArea()
                .navigationTitle("Hello World")
            }
        }
    }
}
```
<div align="center">
  
| Before `.ignoresSafeArea()` | After `.ignoresSafeArea()` |
|-----------------------------|----------------------------|
| <img width="182" alt="Before" src="https://github.com/user-attachments/assets/9939dd43-9f8b-4b91-ac8c-83531930adb0"> | <img width="177" alt="After" src="https://github.com/user-attachments/assets/3fd00c60-e124-4e5e-b9fb-cee51d5ee475"> |

</div>
Repository: go
Issue: runtime:cpu2: TestGdbAutotmpTypes failures
Labels: help wanted,NeedsInvestigation,compiler/runtime

```
#!watchflakes
default <- pkg == "runtime:cpu2" && test == "TestGdbAutotmpTypes"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8733263226355225873)):

    === RUN   TestGdbAutotmpTypes
    === PAUSE TestGdbAutotmpTypes
    === CONT  TestGdbAutotmpTypes
        runtime-gdb_test.go:79: gdb version 15.0


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: pytorch
Issue: Support nn.Module arguments for the function to torch.compiler.allow_in_graph
Labels: triaged,oncall: pt2,module: dynamo

### 🚀 The feature, motivation and pitch

It is very common that a nn.Module is passed as an argument to a function, such as the forward hooks registered to a module.
There are cases that the code of such function is not traceable by Dynamo but the graph is possible be captured correctly by AOT dispatcher. So we would like to decorate the function as torch.compiler.allow_in_graph.

But this is not allowed by the current design of allow_in_graph because it requires the inputs to fn must be Proxy-able types in the FX graph. Valid types include: Tensor/int/bool/float/None/List[Tensor?]/List[int?]/List[float?] Tuple[Tensor?, …]/Tuple[int?, …]/Tuple[float?, …]/torch.dtype/torch.device

nn.Moudle is not one of them. which makes the function is not possible to work as expected with allow_in_graph.
Decorated such function with allow_in_graph causes more graph breaks than avoiding them.

Below is an example showing such a case:

```
import torch

class MyModule(torch.nn.Module):
  def __init__(self):
      super().__init__()
 
  def forward(self, x):
      return x.mul(5.0)
 
def my_function(module, x):
  x = x.mul(3.0)
  print("Simulating something dynamo is not able to trace into.")
  return module(x)
 
torch.compiler.allow_in_graph(my_function)
 
def fn(module, x):
    x = torch.add(x, 1.0)
    x = my_function(module, x)
    x = torch.add(x, 2.0)
    return x
 
fn = torch.compile(fn)
module = MyModule()
input = torch.ones(2, requires_grad = True)
output = fn(module, input)
output.sum().backward()
```

If we can enhance to allow nn.Module as the argument of the fn to allow_in_graph, it will greatly widen the use cases supported by allow_in_graph.


### Alternatives

_No response_

### Additional context

_No response_

cc @ezyang @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @amjames @rec
Repository: kubernetes
Issue: How to balance distribution of existing pods without restarting them
Labels: sig/scheduling,kind/support,lifecycle/stale,needs-triage

I now have 10 pods, but I thought I didn't plan them well at the beginning, which resulted in five of them being scheduled to one node. These pods are running wss services, so they do not want to be restarted. So is there any way to distribute these pods evenly without restarting the operation?
Repository: vscode
Issue: Allow relative paths in `typescript.tsserver.nodePath`
Labels: feature-request,typescript

- VS Code Version: `1.94.2`
- OS Version: MacOS

Steps to Reproduce:

1. Update workspace settings JSON `typescript.tsserver.nodePath` to point at a relative path to the workspace root (e.g. `./my-node-script.sh`)
2. Notice that the script isn't used for invoking tsserver (typescript plugin falls back to using VSCode's inbuilt node install) 

The problem occurs because `asAbsoluteWorkspacePath()` expects that the path to the node path is prefixed with the workspace name.

I'd expect this property to behave the same as `typescript.tsdk` which **doesn't** require the workspace name to prefixed to the relative path passed to it.

https://github.com/microsoft/vscode/blob/fe997185b5e6db94693ed6ef5456cfa4e8211edf/extensions/typescript-language-features/src/utils/relativePathResolver.ts#L9-L20
Repository: TypeScript
Issue: TypeScript skips type-checking despite deleted file in referenced project
Labels: Bug

### Acknowledgement

- [x] I acknowledge that issues using this template may be closed without further explanation at the maintainer's discretion.

### Comment

We have encountered an unusual case in our project references setup. Below is a description of the current configuration. I believe there might be a gap in our setup or configuration that is causing this issue.

# Setup
- We have two projects: 'bar' and 'foo'
- 'foo' references 'bar'
- 'foo/src/index2.ts' consumes a function from "bar/clean" (The entry point is created using TypeScript paths at the repo root tsconfig)
- 'tsconfig.project-references.json' at the repo root is our solution file, containing links to the projects
- Base tsconfig

```
{
  "compilerOptions": {
    "baseUrl": "./",
    "outDir": "out-tsc/frontend/base",
    "incremental": true,
    "composite": true,
    "target": "ES2020",
    "lib": ["ES2022", "DOM"],
    "jsx": "react",
    "jsxFactory": "React.createElement",
    "jsxFragmentFactory": "React.Fragment",
    "types": [],
    "module": "ESNext",
    "moduleResolution": "Node10",
    "resolveJsonModule": true,
    "importHelpers": true,
    "isolatedModules": false,
    "allowSyntheticDefaultImports": true,
    "allowImportingTsExtensions": true,
    "esModuleInterop": true,
    "forceConsistentCasingInFileNames": true,
    "strict": true,
    "noFallthroughCasesInSwitch": true,
    "skipLibCheck": true,
    "experimentalDecorators": false,
    "verbatimModuleSyntax": true,
    "emitDeclarationOnly": true,
    "paths": {
      "bar/clean": ["packages/bar/src/clean.ts"]
    }
  }
}
```



# Steps to reproduce the issue
1. Run TypeScript build with project references. This should create a 'tsDist' folder at the repo root with emitted declarations:
    ```yarn tsc -b tsconfig.project-references.json -v```

2. Delete the file 'packages/bar/src/clean.ts'. This file is consumed by 'packages/foo/src/index2.ts'. Note that we have paths defined for 'bar/clean' in 'tsconfig.json':
     ```rm packages/bar/src/clean.ts```

3. Run TypeScript build with project references again. This should update the 'tsDist' folder at the repo root with emitted declarations. However, it doesn't throw any error, even though 'packages/foo/src/index2.ts' is consuming a non-existent file:
     ```yarn tsc -b tsconfig.project-references.json -v```

Repository for reproduction - https://github.com/sudesh-atlassian/project-references-debug-1.git
Tested with typescript version - v5.4.2, v5.5.2 and v5.6.2

# Queries
- Is this expected behaviour, where typecheck would not typecheck when we have a cache and a file is deleted
- Is there a known way to mitigate this issue
Repository: ui
Issue: [bug]: Cannot install sidebar
Labels: bug

### Describe the bug

![image](https://github.com/user-attachments/assets/d70d5173-a174-414b-a0c0-1c5e97ec9113)


### Affected component/components

Sidebar

### How to reproduce

npx shadcn@latest add sidebar

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Windows
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: ui
Issue: [bug]: Custom utils path inside `components.json` is being ignored
Labels: bug

### Describe the bug

Here's my `components.json` file:

```
{
  "$schema": "https://ui.shadcn.com/schema.json",
  "style": "new-york",
  "rsc": true,
  "tsx": true,
  "tailwind": {
    "config": "tailwind.config.ts",
    "css": "src/styles/globals.css",
    "baseColor": "gray",
    "cssVariables": true,
    "prefix": ""
  },
  "aliases": {
    "components": "~/shared/components",
    "utils": "~/shared/lib",
    "ui": "~/shared/ui-kit",
    "lib": "~/shared/lib",
    "hooks": "~/shared/hooks"
  }
}
```

However, when adding component `cn` is always being imported from `~/lib/utils` even though I explicitly specified it from `~/shared/lib`.

### Affected component/components

Every

### How to reproduce

1. Modify your `components.json` to match mine.
2. Try to add a component, for example `npx shadcn@latest add sidebar`

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Node@20.18.0, React@19.0.0-rc-69d4b800-20241021, NextJS@15.0.1
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: three.js
Issue: BatchedMesh: Reorganization discussion
Labels: Suggestion

### Description

Over the last few releases BatchedMesh has had a number of features added to support optimization, resizing, instancing, etc which has made the class very powerful and flexible. But there have been concerns about complexity and surface API, as well as requests for more features including point & line rendering (#29018), and multi-material support (#27930), etc. I'm happy to rework some of the API of the class but I'll request some more details on what exactly the concerns are and what the more tangible impact / problem is so we can discuss solutions.

cc @mrdoob @Mugen87 

### Solution(s)

- In the short term for this release we can comment the recently-added `optimize`, `setGeometrySize`, `setGeometryCount` functions to avoid future breaking changes if these are going to be moved.

- Introduce some kind of subclassing or flags for more complex rendering or other render types (like lines, points).

- One solution I would like to discuss is moving geometry management to a `BatchedBufferGeometry` class so that the logic complexity for the addition and removal of sub-geomeries would be encapsulated there. The `BatchedMesh` class could continue to pass-through the function calls to the batched mesh. Ultimately the goal being to separate some of the logic out from an otherwise monolithic file. This could also allow for more easily sharing geometry between multiple BatchedMeshes in the case that different shader are needed (#29018).

A class could be structured like so:

```js
class BatchedBufferGeometry {

  constructor( indexCount, vertexCount );

  addGeometry( ... );
  setGeometryAt( ... );
  deleteGeometry( ... );
  
  getBoundingBoxAt( ... );
  getBoundingSphereAt( ... );
  getGeometryRangeAt( ... );
  
  setGeometrySize( ... );
  optimize();
  
}
```

BatchedMesh would otherwise still be responsible for managing instances.

### Alternatives

Leave it as-is - other suggestions.

### Additional context

_No response_
Repository: PowerToys
Issue: Allow Awake to be turned on/off with a keyboard shortcut
Labels: Idea-Enhancement,Needs-Triage,Product-Awake

### Description of the new feature / enhancement

Title says it all.

### Scenario when this would be used?

So many options in PowerToys can be turned on/off with a keyboard shortcut. Whyc not Awake? I use it often, and it would make it a lot more practical.

### Supporting information

_No response_
Repository: godot
Issue: Triple quoted strings cannot be compared to typical strings with the Expression class
Labels: bug,topic:core

### Tested versions

- Reproducible in v4.3.stable.artix_linux

### System information

Godot v4.3.stable unknown - Artix Linux 

### Issue description


In the editor, if you compare a double quoted string to a triple double quoted string, they are equivalent.

If you use the Expression class to compare them, they are not equivalent.

I'm guessing it shouldn't matter whether it's a double, single, triple double or triple single quoted string. They should all be the same if the contents mean the same thing.



### Steps to reproduce


      func evaluate():
	      if "x" == """x""":
		      print("sane")
	      else:
		      print("insane")
		      
	      var xp = Expression.new()
	      var err = xp.parse('"x" == """x"""', [])
	      if err != OK:
		      push_error("failed to parse")
	      var res = xp.execute([])
	      if xp.has_execute_failed():
		      push_error(xp.get_error_text())
	      print('Does expression.execute() think they are the same?')
	      print(res)

Prints:

    sane
    Does expression.execute() think they are the same?
    false

Should print:

    sane
    Does expression.execute() think they are the same?
    true

For any combination of quote types.

### Minimal reproduction project (MRP)

[godot-quote-bug.zip](https://github.com/user-attachments/files/17501407/godot-quote-bug.zip)