sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: ollama
Issue: Support for jinaai/jina-embeddings-v3 embedding model
Labels: model request

jina-embeddings-v3 is a multilingual multi-task text embedding model designed for a variety of NLP applications. Based on the [Jina-XLM-RoBERTa architecture](https://huggingface.co/jinaai/xlm-roberta-flash-implementation), this model supports Rotary Position Embeddings to handle long input sequences up to 8192 tokens. Additionally, it features 5 LoRA adapters to generate task-specific embeddings efficiently.

Key Features:

- Extended Sequence Length: Supports up to 8192 tokens with RoPE.
- Task-Specific Embedding: Customize embeddings through the task argument with the following options:
        retrieval.query: Used for query embeddings in asymmetric retrieval tasks
        retrieval.passage: Used for passage embeddings in asymmetric retrieval tasks
        separation: Used for embeddings in clustering and re-ranking applications
        classification: Used for embeddings in classification tasks
        text-matching: Used for embeddings in tasks that quantify similarity between two texts, such as STS or symmetric retrieval tasks
- Matryoshka Embeddings: Supports flexible embedding sizes (32, 64, 128, 256, 512, 768, 1024), allowing for truncating embeddings to fit your application.
Repository: vscode
Issue: Long chat attachment filenames cause chat input to overflow
Labels: bug,panel-chat


Type: <b>Bug</b>

1. Attach a file with a very long name to chat

**Bug**
The widget expands so that you can't see the submit buttons anymore:

![Image](https://github.com/user-attachments/assets/0e441451-d69b-4f2b-9bef-6dad0105fc14)





VS Code version: Code - Insiders 1.94.0-insider (Universal) (1926933184de3f77ac7176e9fc302c54bd9634b0, 2024-09-23T05:12:01.964Z)
OS version: Darwin arm64 23.6.0
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Apple M2 Max (12 x 2400)|
|GPU Status|2d_canvas: unavailable_software<br>canvas_oop_rasterization: disabled_off<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: disabled_software<br>multiple_raster_threads: enabled_on<br>opengl: disabled_off<br>rasterization: disabled_software<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: disabled_software<br>video_encode: disabled_software<br>webgl: unavailable_software<br>webgl2: unavailable_software<br>webgpu: unavailable_software<br>webnn: disabled_off|
|Load (avg)|4, 4, 4|
|Memory (System)|64.00GB (1.13GB free)|
|Process Argv|--crash-reporter-id 0fffb5da-9cd7-46fd-9e7f-a1564e8c5fda|
|Screen Reader|no|
|VM|0%|
</details><details>
<summary>A/B Experiments</summary>

```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
vsaa593cf:30376535
py29gd2263:31024238
c4g48928:30535728
a9j8j154:30646983
962ge761:30841072
pythongtdpath:30726887
welcomedialog:30812478
pythonnoceb:30776497
asynctok:30898717
dsvsc014:30777825
dsvsc015:30821418
pythonmypyd1:30859725
h48ei257:31000450
pythontbext0:30879054
accentitlementst:30870582
dsvsc016:30879898
dsvsc017:30880771
dsvsc018:30880772
cppperfnew:30980852
pythonait:30973460
724cj586:31013169
a69g1124:31018687
dvdeprecation:31040973
dwnewjupytercf:31046870
impr_priority:31057980
nativerepl1:31134653
refactort:31084545
pythonrstrctxt:31093868
flighttreat:31119334
wkspc-onlycs-t:31132770
nativeloc1:31118317
wkspc-ranged-t:31125599
jh802675:31132134
e80f6927:31120813
ei213698:31121563
i21gd607:31141543
notype1:31143044
b50ed353:31138333
showbadge:31139796
f8igb616:31140137

```

</details>

<!-- generated by issue reporter -->
Repository: go
Issue: proposal: testing/fstest: add MapFS.CopyFrom(fs.FS)
Labels: Proposal

### Proposal Details

Since it was concluded that `fs.FS` is necessarily read-only, the only alternative is for every writable filesystem to implement its own form of [`os.CopyFS`](https://pkg.go.dev/os#CopyFS). This proposal is about doing so for [`MapFS`](https://pkg.go.dev/testing/fstest#MapFS).

For details, see:
* https://github.com/golang/go/issues/45757#issuecomment-1640530305
Repository: godot
Issue: GDScript test suite fails with MinGW-LLVM build 
Labels: bug,platform:windows,needs testing,topic:tests

### Tested versions

v4.4.dev.custom_build [42a330e6e]

### System information

Godot v4.4.dev (42a330e6e) - Windows 10.0.22621 - Multi-window, 2 monitors - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3060 Ti (NVIDIA; 32.0.15.6109) - AMD Ryzen 7 3700X 8-Core Processor (16 threads)

### Issue description

Toolchain used: https://github.com/mstorsjo/llvm-mingw/releases (both 20240917 with LLVM 19.1.0 final and llvm-mingw 20240619 with LLVM 18.1.8)

Output:
```
[doctest] doctest version is "2.4.11"
[doctest] run with "--help" for options
Could not load project settings.
ERROR: Could not open specified test directory.
   at: (modules\gdscript\tests\gdscript_test_runner.cpp:334)
===============================================================================
./modules/gdscript/tests/gdscript_test_runner_suite.h:43:
TEST SUITE: [Modules][GDScript]
TEST CASE:  Script compilation and runtime

modules\gdscript\tests\gdscript_test_runner.cpp:190: FATAL ERROR: An error occurred while making the tests.

./modules/gdscript/tests/gdscript_test_runner_suite.h:49: FATAL ERROR: REQUIRE( fail_count == 0 ) is NOT correct!
  values: REQUIRE( -1 == 0 )
  logged: Make sure `*.out` files have expected results.
          All GDScript tests should pass.

ERROR: Failed to create file "res://.editorconfig".
   at: EditorPaths (editor\editor_paths.cpp:271)
ERROR: Failed to get attributes for: res://.editorconfig
   at: (drivers\windows\file_access_windows.cpp:473)
Could not load project settings.
===============================================================================
./modules/gdscript/tests/test_completion.h:223:
TEST SUITE: [Modules][GDScript][Completion]
TEST CASE:  [Editor] Check suggestion list

./modules/gdscript/tests/test_completion.h:87: FATAL ERROR: Invalid test directory.

WARNING: Property not found: gui/theme/lcd_subpixel_layout
     at: get_setting_with_override (core\config\project_settings.cpp:375)
===============================================================================
./modules/gdscript/tests/test_lsp.h:391:
TEST SUITE: [Modules][GDScript][LSP]
TEST CASE:  [workspace][resolve_symbol]

./modules/gdscript/tests/test_lsp.h:90: FATAL ERROR: REQUIRE( err == OK ) is NOT correct!
  values: REQUIRE( 31 == 0 )
  logged: Could not open specified root directory


================================================================
CrashHandlerException: Program crashed with signal 11
Engine version: Godot Engine v4.4.dev.custom_build (de106b9cf3557cfc3dcccad5e62d46d845e32730)
Dumping the backtrace. Please include this when reporting the bug to the project developer.
[1] _gnu_exception_handler (../crt/crt_handler.c:0)
[2] GDScriptTests::initialize(String const&) (./modules/gdscript/tests/test_lsp.h:91)
-- END OF BACKTRACE --
================================================================
```

### Steps to reproduce

Build Godot using MinGW-LLVM (`use_mingw=yes` and `use_llvm=yes`) with tests enabled.
Run it with `--test`.

### Minimal reproduction project (MRP)

-
Repository: ollama
Issue: https://ollama.com/install.sh creates contrib.list which just creates tons of warnings
Labels: bug,linux,install

### What is the issue?

After running `https://ollama.com/install.sh` I now have a `/etc/apt/sources.list.d/contrib.list` which I never asked for and every `apt-get update` command now makes tons of warnings:

```
W: Target Packages (contrib/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:4 and /etc/apt/sources.list.d/contrib.list:4
W: Target Packages (contrib/binary-i386/Packages) is configured multiple times in /etc/apt/sources.list:4 and /etc/apt/sources.list.d/contrib.list:4
W: Target Packages (contrib/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:4 and /etc/apt/sources.list.d/contrib.list:4
W: Target Translations (contrib/i18n/Translation-en_IE) is configured multiple times in /etc/apt/sources.list:4 and /etc/apt/sources.list.d/contrib.list:4
(etc. for a couple 200 lines in my case)
```

Of course, I'm going to fix the issue by removing `/etc/apt/sources.list.d/contrib.list`, but I believe it shouldn't be created in the first place. And if it has to be, please cleanup after your script by removing it yourself. A 2024 version of "Be kind, rewind" in some sort ;-)


### OS

Linux

### GPU

Nvidia

### CPU

Intel

### Ollama version

0.3.11
Repository: pytorch
Issue: Setting a `complex` tensor to `linalg.norm()` returns a `float` tensor
Labels: triaged,module: linear algebra

### 🐛 Describe the bug

Setting an `int` tensor to [linalg.norm()](https://pytorch.org/docs/stable/generated/torch.linalg.norm.html) gets the error message as shown below:

```python
import torch
from torch import linalg

my_tensor = torch.tensor([8, -3, 0, 1])

linalg.norm(input=my_tensor) # Error
```

> RuntimeError: linalg.vector_norm: Expected a floating point or complex tensor as input. Got Long

But, setting a `complex` tensor to `linalg.norm()` returns a `float` tensor as shown below:

```python
import torch
from torch import linalg

my_tensor = torch.tensor([8.+0.j, -3.+0.j, 0.+0.j, 1.+0.j])

linalg.norm(input=my_tensor)
# tensor(8.6023)

linalg.norm(input=my_tensor).dtype
# torch.float32
```

So, I set `dtype=torch.complex64` to `linalg.norm()` but it still returns a `float` tensor as shown below: 

```python
import torch
from torch import linalg

my_tensor = torch.tensor([8.+0.j, -3.+0.j, 0.+0.j, 1.+0.j])
                           # ↓ ↓ ↓ ↓ ↓ ↓ ↓ ↓ ↓ ↓ ↓
linalg.norm(input=my_tensor, dtype=torch.complex64)
# tensor(8.6023)

linalg.norm(input=my_tensor, dtype=torch.complex64).dtype
# torch.float32
```

### Versions

```python
import torch

torch.__version__ # '2.3.0'
```

cc @jianyuh @nikitaved @pearu @mruberry @walterddr @xwang233 @Lezcano
Repository: pytorch
Issue: `2` and `-2` for `ord` argument of `linalg.norm()` should be explained more clearly
Labels: module: docs,triaged,module: linear algebra

### 📚 The doc issue

[The doc](https://pytorch.org/docs/stable/generated/torch.linalg.norm.html) of `linalg.norm()` explains the supported norms for `ord` argument but `2` and `-2` are not explained clearly just saying `largest singular value` and `smallest singular value` respectively as shown below:

|`ord`|norm for matrix|norm for vector|
|-|-|-|
|...|...|...|
|`2`|largest singular value|as below|
|`-2`|smallest singular value|as below|
|...|...|...|

### Suggest a potential alternative/fix

So, the words `SVD(Singular Value Decomposition)` should be added to them as shown  below:

|`ord`|norm for matrix|norm for vector|
|-|-|-|
|...|...|...|
|`2`|The largest singular value of SVD(Singular Value Decomposition)|as below|
|`-2`|The smallest singular value of SVD|as below|
|...|...|...|

cc @svekars @brycebortree @sekyondaMeta @jianyuh @nikitaved @pearu @mruberry @walterddr @xwang233 @Lezcano
Repository: go
Issue: cmd/go: doc: doesn't show embedded struct's methods
Labels: help wanted,NeedsInvestigation,GoCommand

### Proposal Details

Hi!
I was recently using a new GO module in my project.
There was code like this:
```go
type (
   A struct {}
   B struct { *A }
)

func (*A) Foo() {}
```
Tybe B however was a large struct with many methods and exported fields.
I had a code example that used method `Foo` and I just wanted to know more about i.
I used `go doc B.Foo` but it said `doc: no method or field B.Foo in package`.

I suppose, that because call like this is 100% possible `&B{}.Foo()`, above `go doc` call should return documentation for `Foo`
Repository: flutter
Issue: [video_player] Add support for transparency
Labels: c: new feature,a: video,p: video_player,team-ecosystem,P3,triaged-ecosystem

It looks like https://pub.dev/packages/video_player doesn't document any support for [alpha channels](https://pixelbakery.com/recipes/video-image-formats), but it would be nice if it could accurately render videos with transparency.
Repository: transformers
Issue: Add support for OmDet-Turbo multi-gpu inference with DataParallel.
Labels: New model,Distributed Training / Models,Feature request

### Feature request

OmDet-Turbo will be added to Transformers soon, however it won't support using DataParallel for inference using multi-gpu, at least initially. 

### Motivation

If there is a large demand to support multi-gpu inference with DataParallel.

### Your contribution

A PR will be created if there is demand for it.
Repository: flutter
Issue: [go_router] improve readability of go_router prior to guard implementation
Labels: c: new feature,package,c: proposal,P3,p: go_router,team-go_router,triaged-go_router

### Use case

After having a look into [the guard proposal](http://flutter.dev/go/go-router-redirect) and what it'd take to implement that; I believe it would be beneficial to improve this package readability prior to implementation in the following aspects:

  1. It is hard to know if an `Uri uri` or `String path` or `String loc` parameter is in fact a pattern or simply an already "compiled" path. You may have to check the wider context.
  2. There are some function nesting going on, sometimes 3 level deep, which is hard to read in the redirects
  3. The logic for redirection is mainly in configuration.dart, but is still a bit spread in other files

### Proposal


1. Create a new `RoutePattern` class that would also serve as a wrapper for functions in `path_utils` but also indicate that an parameter is in fact a route pattern.
2. Concentrate the redirection logic in a redirection.dart and flatten the function nesting part.

I believe the guard proposal, would be easier to implement after those changes.
Repository: go
Issue: x/build/cmd/gomote: don't duplicate logic present in golangbuild in the repro subcommand
Labels: Builders,NeedsInvestigation

Soon, `gomote repro` is going to assume some logic in `golangbuild` as part of its test command output, specifically for the no-network builders. This is unfortunate, since we're duplicating this subtle logic in multiple places.

Let's strive to avoid that in the future. In particular, test execution in `golangbuild` has some complexity around test execution. The two biggest ones are disabling the network on some builders and copying nested submodules out of context to test them (#34352). It would make sense to turn `golangbuild` into its own reproducer, like we do for the environment. This could work but needs thought.

For now, this issue tracks this particular consequence of the complexity of test execution seeping into other parts of the codebase: duplicating the no-network logic for printing the test command in the `gomote repro` command.
Repository: flutter
Issue: Add `AnimationTheme` to specify default curve(s) and duration(s)
Labels: framework,a: animation,c: proposal,P3,team-framework,triaged-framework,f: theming

### Use case

There are a ton of super useful [implicitly animated widgets](https://api.flutter.dev/flutter/widgets/ImplicitlyAnimatedWidget-class.html). They require an explicit duration argument and have a static default argument for curve (`Curves.linear`).

The most obvious way to handle these arguments across your app it to create globals and/or create your own inherited widget to hold them. This works okay, but it's annoying to have to specify the relevant curve(s) and duration(s) in every relevant place. It's even more annoying if you:
1. Use different durations and/or curves for different scenarios
2. Want to dynamically override the animation duration and/or curve according to user settings or situation (ie tuning a game to feel faster and snappier when a user is on a streak)
3. Are on a large team with specific animation design guidelines and don't want to rely on developers remembering to pipe the correct values into the relevant widgets

This is an especially good candidate for including into the framework itself instead of relying on the community to build packages/roll their own solutions because the core value add (having sane defaults and optional arguments on all relevant built-ins) can only be achieved by changing the built in widgets.

### Proposal

1. Create an `AnimationTheme` inherited widget and  `AnimationThemeData` class that hold a default `Curve` and `Duration`
2. Add an `AnimationTheme.of(context)` static method that retrieves the animation theme and listens to any changes in the theme
2. Add `AnimationThemeData` to `ThemeData` and include default values
3. Have all implicitly animated widgets inherit default values (with chained inheritance resolution if `inherit=true`)  from the nearest `AnimationTheme`/`Theme`
4. Make the `duration` and `curve` arguments optional and nullable with no default values and use them as overrides for the theme values when non-null

Open questions:
1. Should there be other arguments such as `curveFast`, `durationFast` etc equivalent to `bodySmall`, `bodyMedium`....? Devs could then opt-into alternate theme-held animations
2. Are there other widgets that should reference the theme held values? Maybe navigator and it's default transitions? What about `AnimationController`?
3. Should we lerp curves and durations in some clever way (like some theme colors etc do) when their theme values change, or should we defer to the individual widgets to handle changes as they see fit?

On all of the above I feel the best approach is to launch an MVP and then see what feature requests devs make as all these extra features are easy to add later if needed but hard to roll back if we find they're not.
Repository: go
Issue: x/website: go.dev tends not to show up on Google search results, but tip.golang.org does
Labels: NeedsInvestigation,website

### Go version

n/a

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

```shell
n/a
```


### What did you do?

I performed Google searches for various documents that I know are hosted on go.dev. Example search queries:

* `golang doc comments`
* `golang 1.23 release notes`

### What did you see happen?

The copy of the document on tip.golang.org was the first Google search result each time.

Here are the two examples:

![screen_20240923142359](https://github.com/user-attachments/assets/3e1c3e2e-e860-4cd9-a11a-f3b8a48ab440)

![screen_20240923142413](https://github.com/user-attachments/assets/571490db-22e7-4817-aeda-030ef133dc6f)

(I noticed this on my personal Google account, but I took those two screenshots from a Chrome incognito window.)

### What did you expect to see?

I expect the canonical version of these documents to be the first search result, or at least near the top.

* `golang doc comments`:
  - https://tip.golang.org/doc/comment is the first result
  - https://go.dev/doc/comment isn't anywhere in the first two pages of search results
* `golang 1.23 release notes`:
  - https://tip.golang.org/doc/go1.23 is the first result
  - https://go.dev/doc/go1.23 isn't anywhere in the first two pages of search results
  - Weirdly, the second search result *is* a go.dev URL, the "Go 1.23 is released" blog post at https://go.dev/blog/go1.23.

I guess for most projects I probably wouldn't file an SEO ticket, but you folks are mostly paid by Google, so I figure you ought to be able to sort it out :)
Repository: godot
Issue: Color wrapper for alpha values does not work
Labels: topic:core

### Tested versions

Reproducible in 4.1.1 and 4.3

### System information

Godot v4.3.stable - Windows 10.0.22631 - GLES3 (Compatibility) - NVIDIA GeForce RTX 4070 Ti (NVIDIA; 32.0.15.6109) - AMD Ryzen 9 7950X 16-Core Processor (32 Threads)

### Issue description

On the docs for Color, there are wrappers for RGBA to use 0-255 instead of 0-1 values.
https://docs.godotengine.org/en/stable/classes/class_color.html#class-color-property-a

However, the wrapper for alpha (a) value does not work.
The docs should explain this or the engine should give a warning if values outside the expected range are used.
(Alternatively--the wrapper should behave as expected.)

Instead of using the wrapper, Color8 can also be used to strictly specify the 0-255 range.


### Steps to reproduce

Open the MRP below.
Run the root scene and observe the color behavior.
The lines are generated from left to right, from i=0 to i=num_lines.

We expect the first two lines to have the same color, but they do not:
line.default_color = Color(1, 1, 1, 51.0/255.0)
line.default_color = Color(255, 255, 255, 51)

The third and fourth lines show the expected behavior, demonstrated using Color8 (both lines should be the same color.)
line.default_color = Color(1, 1, 1, 51.0/255.0)
line.default_color = Color8(255, 255, 255, 51)



### Minimal reproduction project (MRP)

[color_test.zip](https://github.com/user-attachments/files/17104957/color_test.zip)
Repository: next.js
Issue: Using a client-side promise on initial render hangs server stream
Labels: bug,Lazy Loading

### Link to the code that reproduces this issue

https://github.com/mordechaim/promise-stream

### To Reproduce

1. Start the application with `npm run dev`
2. Click "hard navigation" link


### Current vs. Expected behavior

I use `use()` to resolve the promise in a client component. If the page is a full page load, the suspended component never "wakes up", the browser's loading indicator keeps spinning and the initial response body never completes.

When building the application with `next build` it hangs as well, with the following error message:

```
> next build

  ▲ Next.js 15.0.0-canary.163

   Creating an optimized production build ...
 ✓ Compiled successfully
 ✓ Linting and checking validity of types    
 ✓ Collecting page data    
   Generating static pages (5/6)  [=   ]Failed to build /suspend/page: /suspend (attempt 1 of 3) because it took more than 60 seconds. Retrying again shortly.
```

The behavior is not present if any of those is true:
- The promise is created on the server and passed to the client in unresolved state
- The promise resolves before the initial render completes
- The page is a soft navigation, namely, the promise wasn't pre-rendered on the server

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Home
  Available memory (MB): 32674
  Available CPU cores: 8
Binaries:
  Node: 20.5.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 15.0.0-canary.163 // Latest available version is detected (15.0.0-canary.163).
  eslint-config-next: N/A
  react: 19.0.0-rc-5d19e1c8-20240923
  react-dom: 19.0.0-rc-5d19e1c8-20240923
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


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

Lazy Loading

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

next dev (local), next build (local)

### Additional context

_No response_
Repository: pytorch
Issue: [torch.library] add convenience API for autocast
Labels: triaged,module: amp (automated mixed precision),module: library,oncall: pt2,module: pt2-dispatcher

internal x-post: https://fb.workplace.com/groups/1405155842844877/permalink/9142331259127258/

Probably add some torch.library.register_autocast API with some convenience options ("upcast to float32", "downcast to float16")

cc @mcarilli @ptrblck @leslie-fang-intel @jgong5 @anjali411 @ezyang @chauhang @penguinwu @bdhirsh