sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: Support macOS Sequoia Writing tools text input feature
Labels: a: text input,framework,engine,platform-mac,c: proposal,P2,team-text-input,triaged-text-input

Add support for the macOS Sequoia text editing context menu "Writing Tools"

![Screenshot 2024-06-20 at 4 54 37 PM](https://github.com/flutter/flutter/assets/682784/94e2fe67-90d8-48df-95e2-dd18db057d47)
![Screenshot 2024-06-20 at 4 55 09 PM](https://github.com/flutter/flutter/assets/682784/e88e5021-a5da-4eda-ae7e-6bf7d87b493d)
![Screenshot 2024-06-20 at 5 35 50 PM](https://github.com/flutter/flutter/assets/682784/f52d137a-3a2d-432d-976c-d31098b9835b)
![Screenshot 2024-06-20 at 5 35 35 PM](https://github.com/flutter/flutter/assets/682784/c869f23f-9206-4a33-a07e-4c09a160610e)

```swift
class CustomTextView: NSView, NSServicesMenuRequestor {
    override func validRequestor(forSendType sendType: NSPasteboard.PasteboardType?, 
                                 returnType: NSPasteboard.PasteboardType?) -> Any? {
        if sendType == .string || sendType == .rtf {
            return self
        }
        return super.validRequestor(forSendType: sendType, returnType: returnType)
    }
    
    nonisolated func writeSelection(to pboard: NSPasteboard,
                                    types: [NSPasteboard.PasteboardType]) -> Bool {
        // Write plain text and/or rich text to pasteboard
        return true
    }

    // Implement readSelection(from pboard: NSPasteboard)
       as well for editable view
}
```

https://developer.apple.com/videos/play/wwdc2024/10168/?time=543

iOS issue at https://github.com/flutter/flutter/issues/150452
WebKit issue at https://github.com/flutter/flutter/issues/150965
Repository: rust
Issue: Document the `run_make_support` library
Labels: T-compiler,A-docs,A-contributor-roadblock,A-run-make

The support library has some sparse doc comments via `./x doc src/tools/run-make-support`, but it really needs some better high-level docs to help test writers (otherwise the support library is very hard to discover). There also needs to be crosslinks from rustc-dev-guide back to these docs.

---

<https://rust-lang.zulipchat.com/#narrow/stream/421156-gsoc/topic/Project.3A.20Rewriting.20Makefile.20Tests.20Using.20Rust/near/443513926> reproduced here for convenience:

I'm thinking that I should add some docs for the support library, for stuff like:

- Assumptions (e.g. paths relative to the working directory of the test being run)
- Key API design: the `Command` wrapper and `CompletedProcess` etc.
- Synposis of common `Command` and `CompletedProcess` APIs
- Guidance for adding new command wrappers, adding new dependencies, when to uplift things from tests to the support library etc.
- Recommendations: error reporting
- Reminder to augment and update the changelog
Repository: ui
Issue: [bug]: Bottom padding issue Tabs flex wrap scenario
Labels: bug

### Describe the bug

```
<div className="grid auto-rows-max items-start gap-4 md:gap-8 lg:col-span-2">
        <Tabs defaultValue="All">
          <TabsList className="flex flex-wrap pb-32">
            <TabsTrigger value="All">All</TabsTrigger>
            {itemsCollection.map((item) => (
              <TabsTrigger value={item.name as string}>{item.name}</TabsTrigger>
            ))}
          </TabsList>
          {genres.map((item) => (
            <TabsContent value={item.name as string}>
             /* content */
            </TabsContent>
          ))}
        </Tabs>
      </div>
```
in the above example, `pb-32` is hardcoded because if there is a large tab collection, it breaks into two or more rows, then the background color & padding doesnt extend. If the viewport is resized to `md` & lower, it is more clear that the Tab component padding doesnt grow/shrink. TabsTrigger clips into below components 



### Affected component/components

Tabs, TabsContent, TabsList, TabsTrigger

### How to reproduce

1. this may just be a client component issue
2. add `flex flex-wrap` to TabList
3. observe TabContent overlap in position with TabList

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Mac 14.4, Chrome (latest)
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: godot
Issue: Runtime TileData modifications are reset after TileMapLayer _rendering_update
Labels: discussion,documentation,topic:2d

### Tested versions

- Reproducible in v4.3.beta1.official [a4f2ea91a]

### System information

Godot v4.3.beta1 - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1660 SUPER (NVIDIA; 31.0.15.2802) - AMD Ryzen 5 5600X 6-Core Processor (12 Threads)

### Issue description

If I modify the `z_index` of tiles in a `TileMapLayer` in `_tile_data_runtime_update`, that z_index modification is gone if the TileMapLayer re-renders. 

I noticed it in my floor system, because I `hide()` the floor when it shouldn't be visible, and `show()` it again when it is. Upon being shown again, the tiles I applied a z_index modification to get reverted back to the initial state from their original `TileData`.

![1Ln1Y9o 1](https://github.com/godotengine/godot/assets/15309863/232f3ead-075a-426e-83e2-22bab4b1f276)

## Expectation

I would expect that if I modify a z_index (or any other property of a cell), the change would remain cached and not reset unless I explicitly set it to some other value or reset it.

## Notable Mention

It's also maybe important/related to mention that if you try to `get_cell_tile_data(coords)` on a cell you've modified in runtime, you still get the original `TileData`, and you have no way to access the modifications you made unless you explicitly save them in some other data structure.

I understand that maybe `get_cell_tile_data` is *supposed* to get the original `TileData` object, but there could be a way added to get the cached runtime tiledata with changes too. This may be a candidate for a different report though.

### Steps to reproduce

1. In `_use_tile_data_runtime_update` of a TileMapLayer, specify some coords that require an update.
2. In `_tile_data_runtime_update`, for those coordinates, apply a `z_index` update (In my case, I add +10 z_index).
3. `hide()` that `TileMapLayer`, then `show()` it again. Your `z_index` change will be reset to its initial value.

### Minimal reproduction project (MRP)

[mrp_tiledatabug.zip](https://github.com/user-attachments/files/15892847/mrp_tiledatabug.zip)
Repository: flutter
Issue: [Flutter GPU] Allow specifying the mip level/slice for color attachments.
Labels: c: proposal,P2,team-engine,triaged-engine,flutter-gpu

- Support needs to be added to Impeller's HAL for this.
- Allow specifying a specific `ColorAttachment.mipLevel` (default 0) and `ColorAttachment.slice` (default 0).
- Throw a Dart exception if `!(0 < mipLevel < mipLevelCount)` or if `slice` is is out of range for the given `TextureType` (i.e. `TextureType.cube` has 6 slices, whereas `TextureType.2d` has 1).
Repository: flutter
Issue: Expose low level IME interactions
Labels: a: text input,c: proposal,P2,team-text-input,triaged-text-input

### Use case

Currently, it's very hard for Flutter developers to make changes to Flutter's text input experience without losing access to Flutter's entire text input stack. Specifically, if I want to [example]

This problem arises because in each of Flutter's platform embedders, Flutter abstracts differences in the platforms' text input APIs and communicates with the framework using common platform channel methods ([text_input.dart](https://github.com/flutter/flutter/blob/b44c67e2e8/packages/flutter/lib/src/services/text_input.dart)). For Flutter app developers, there is no access to the platform's unique nuances if they aren't covered in the common platform channel methods. It's not possible to access them by writing a plugin without rewriting all the rest of Flutter's text input code as well.

### Proposal

Instead of abstracting platform differences in the engine, the platform channel calls could mirror the native platform APIs. Any abstraction could be done in the framework, on top of these verbatim platform channel methods. Then, Flutter app developers could potentially access these calls themselves while still using Flutter's existing text editing stack.

### Open questions

 * Would it be possible to do this with FFI, or even FFIgen?
 * Flutter suffers from a distributed system problem in that the framework and engine both maintain a copy of the current text input state, both sides can make changes to this, and it must be synced between them asynchronously. Does this new approach make this problem worse or better?

Creating this issue in collaboration with @matthew-carroll from a discussion in https://github.com/flutter/flutter/issues/150068.
Repository: godot
Issue: Hue Variation not applied in CPUParticles2D if hue variation curve is unset
Labels: bug,topic:2d,topic:particles

### Tested versions

4.2.2

### System information

win10 godot 4.2.2

### Issue description

If you create a new CPUParticles2D, set otherwise valid values, but leave the curve at its default empty/unset value, there is no hue variation (in godot 4.2.2).  Encountered while helping people on the godot forum, when we tracked down the issue, I was told this is not the expected behavior and asked to file a bug report.  Looks like problem exists in lin 940 of cpu_particles_2d.cpp, it checks if the curve parameters are valid, and since they're not, the output value is 0.0.  Output value should default to 1.0, scaled by the min/max settings.

### Steps to reproduce

create a new empty 2d scene.  Add a new CPUParticles2D node to it.  Set a minimum variation to 0, and a maximum to 1, but leave the curve at its default empty/unset value.  There is no hue variation.

### Minimal reproduction project (MRP)

[nothanks.txt](https://github.com/user-attachments/files/15893240/nothanks.txt)
Repository: flutter
Issue: [impeller] the blur can discard fidelity from an overflow with the correct scale + sigma
Labels: P2,e: impeller,team-engine,triaged-engine

Certain combinations of scale + sigma can cause the shader to overflow now that we are scaling the sigma based on the entity's transform.

I played around with this a bit and just increasing the sigma from zero to 1000 won't cause a crash.  A scale is required.

The following patch will make it never possible.  It seems like it isn't throwing much away in the case that hits this.  The way that this should work is that `GaussianBlurFilterContents::CalculateScale` should accommodate for large sigmas with a counteracting downscale.  There is a certain range of input that is falling through the cracks though.

```diff
diff --git a/impeller/entity/contents/filters/gaussian_blur_filter_contents.cc b/impeller/entity/contents/filters/gaussian_blur_filter_contents.cc
index 035109e519..96c585b3fe 100644
--- a/impeller/entity/contents/filters/gaussian_blur_filter_contents.cc
+++ b/impeller/entity/contents/filters/gaussian_blur_filter_contents.cc
@@ -653,6 +660,13 @@ GaussianBlurPipeline::FragmentShader::KernelSamples GenerateBlurInfo(
     x_offset = 1;
   }
 
+  // This is a safe-guard to make sure we don't overflow the fragment shader.
+  // The kernel size is multiplied by 2 since we'll use the lerp hack on the
+  // result.
+  if (result.sample_count > (2 * (kMaxKernelSize - 1))) {
+    result.sample_count = 2 * (kMaxKernelSize - 1);
+  }
+
```

## reproduction steps
1) run the `EntityTest.GaussianBlurFilter`
1) set the x scale to 3.0
1) set the sigma to combined
1) start increasing the sigma
1) notice that around 300 sigma, there will be a crash
Repository: vscode
Issue: Normalize let/const exports in vscode.d.ts
Labels: api,debt,api-finalization

Some properties in extension API like https://github.com/microsoft/vscode/blob/0dfcf2c82934ef40ed584d3d6a1764f0c0d78069/src/vscode-dts/vscode.d.ts#L10349 are exported with `let` because they can change, but this also implies that extensions can set them. That isn't allowed, only vscode can change them. Some similar properties already use `const`. We should normalize these to `const` everywhere to avoid confusion.

`readonly` communicates the intent a little better, but this is a namespace, not properties on an interface. But I think it's clear from the name and behavior that these properties will change.
Repository: PowerToys
Issue: PowerRename : allow column width size change (right pane)
Labels: Needs-Triage

### Description of the new feature / enhancement

The right pane contains 2 columns, the first one with the original file name and next to it the new (renamed) file name.
If the file name is very long, only part of it is displayed on left column. It would be useful to be able to move (using the mouse) the vertical separation left or right so you can see the full file name of the left column by moving it to the right, or the full renamed file name by moving it to the right.

### Scenario when this would be used?

When the file name is very long and you have to use a regexp to remove some part at the end of the file name because in that case you're blind, or you'll have to resize the full window, and even a large screen is used (mine is 3840px width and long file names need the PowerRename window to use almost all of the screen width.

### Supporting information

Some sites are known to download files with very long names like : 

1. book names which includes the title, authors list, date, editor, ISBM etc. (dot pdf).
2. classical music tracks names (01 - Johann Sebastian Bach - Brandenburg Concerto No. 3 In G Major BWV 1048 - Concerto No 1 - etc. (dot mp3)
Repository: godot
Issue: [ProgressBar] inconsistent Step behavior
Labels: discussion,documentation,topic:gui

### Tested versions

v4.2.2.stable.mono.official [15073afe3]

### System information

Godot v4.2.2.stable.mono - Windows 10.0.22631 - GLES3 (Compatibility) - NVIDIA GeForce RTX 4090 (NVIDIA; 32.0.15.5585) - 12th Gen Intel(R) Core(TM) i5-12600K (16 Threads)

### Issue description

When using the default `Step` of `0.01`, ProgressBar **_will_** **_not_** increase(`+=`) `Value` by a value lower than or equal to `0.005` via script.  It **_will_** however increase value by `0.006` and above.

If the logic is that ProgressBar won't accept values lower than it's step, it's inconsistent that it accepts `0.006+` but not `0.005-`.

Setting `Step` to `0.009` makes it accept both values.
It seems to me like a rounding error somewhere in Value's `Set` method.

I think it should either accept both or none.
The current behaviour's inconsistency is very confusing and it took me hours to figure out why a specific Bar wasn't working.

### Steps to reproduce

1. Create a Progress bar.
2. Attach new Script.
3. In _Process increase the Progress Bar's value by 0.005 per tick.
4. Nothing happens.
5. Increase value to 0.006.
7. Now it works. 

### Minimal reproduction project (MRP)

[ProgressBarPrecision.zip](https://github.com/user-attachments/files/15893561/ProgressBarPrecision.zip)
Repository: pytorch
Issue: Expand Tag Set: views & reductions
Labels: module: internals,good first issue,triaged

### 🚀 The feature, motivation and pitch

`pointwise` tag has found use in multiple places. It would also be useful to have `reduction` and `view` tags. Especially the latter is often re-created adhoc.

cc @ezyang @bhosmer @smessmer @ljk53 @bdhirsh @SherlockNoMad

### Alternatives

_No response_

### Additional context

_No response_
Repository: electron
Issue: [Bug]: Extreme globalShortcut flakiness on Kubuntu 24.04 Wayland
Labels: platform/linux,bug :beetle:,has-repro-gist,component/globalShortcut,wayland,31-x-y

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a bug report that matches the one I want to file, without success.

### Electron Version

31.0.1

### What operating system are you using?

Ubuntu

### Operating System Version

Kubuntu 24.04

### What arch are you using?

x64

### Last Known Working Electron version

30.1.x

### Expected Behavior

globalShortcut works from all applications

### Actual Behavior

globalShortcut is ignored in some application (eg Sublime Text) despite not having any interfering local shortcut in that application.

### Testcase Gist URL

_No response_

### Additional Information

It works fine if the focused application is Chrome, Android Studio, or the Android Emulator

It fails if I focus Sublime Text, Firefox, Dolphin, or no applications.

Specifically testing using `Ctrl+Shift+Z` and `Ctrl+Shift+X`

This seems to have been reported years ago and simply rejected as a `wontfix`? #15863 That would make all our years of development a waste if that's really not going to be fixed.
Repository: next.js
Issue: Cannot create app router localized sitemap
Labels: bug,Metadata,linear: next

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/elastic-wave-5d4hkj?workspaceId=b7d16bab-058a-4b6f-b4f8-cb3182273009

### To Reproduce

1. Create a new Next.js app with `npx create-next-app@latest` (accept all the default settings)
2. Create a new `app/sitemap.ts` file
3. Copy and paste the example from: https://nextjs.org/docs/app/api-reference/file-conventions/metadata/sitemap#generating-a-sitemap-using-code-js-ts. This will work when you visit `localhost:3000/sitemap.xml`
4. Now, copy and paste the localized example: https://nextjs.org/docs/app/api-reference/file-conventions/metadata/sitemap#generate-a-localized-sitemap. This will not work. Remove all the alternates, and it works again.

### Current vs. Expected behavior

We would expect to see a sitemap with localized alternates when we visit `localhost:3000/sitemap.xml`. Instead, visiting this route results in a plain text result, with a `Uncaught TypeError: Cannot read properties of null (reading 'childNodes')` error in the browser console.

![CleanShot 2024-06-18 at 21 40 33](https://github.com/vercel/next.js/assets/8345645/0c68d2b0-2a2a-4fdd-a365-30aa536ddc9e)


### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
  Available memory (MB): 4102
  Available CPU cores: 2
Binaries:
  Node: 20.9.0
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: 8.10.2
Relevant Packages:
  next: 15.0.0-canary.37 // Latest available version is detected (15.0.0-canary.37).
  eslint-config-next: N/A
  react: 19.0.0-rc-6f23540c7d-20240528
  react-dom: 19.0.0-rc-6f23540c7d-20240528
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Metadata

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

This issue is a duplicate of: https://github.com/vercel/next.js/issues/65817
Repository: pytorch
Issue: Extract some public APIs from torch::cuda::initModule(module) to torch::initModule()
Labels: triaged,module: amp (automated mixed precision)

### 🚀 The feature, motivation and pitch

Currently there are some APIs in torch::cuda::initModule(module) that are device-independent, such as the following:
(https://github.com/pytorch/pytorch/blob/304c9345726e68c9bbd0ea370b3c056db6964c4b/torch/csrc/cuda/Module.cpp#L1173)
```
static void registerCudaPluggableAllocator(PyObject* module) {
  auto m = py::handle(module).cast<py::module>();  
  //  ...
  m.def("_set_cached_tensors_enabled", [](bool enabled) {
    at::caching::set_cached_tensors_enabled(enabled);
  });

  m.def("_add_cached_tensor", [](const at::Tensor& t) {
    at::caching::add_cached_tensor(t);
  });

  m.def("_remove_cached_tensor", [](const at::Tensor& t) {
    at::caching::remove_cached_tensor(t);
  });

  m.def("_is_cached_tensor", [](const at::Tensor& t) {
    return at::caching::is_cached_tensor(t);
  });
  // ...
}
```


### Alternatives

Can we extract these APIs so that they can be used by all devices?

### Additional context

_No response_

cc @mcarilli @ptrblck @leslie-fang-intel @jgong5
Repository: go
Issue: proposal: archive/tar: add iterator form of (&Reader).Next()
Labels: Proposal

### Proposal Details

In Go 1.23, we can use range-over-func a.k.a iterator and developers propose to apply for the package into some packages.

For instance, the following issues are easy to know what kind of content are proposed.
https://github.com/golang/go/issues/61897
https://github.com/golang/go/issues/64341

This proposal is similar with above it.
I think it's good to apply for archive/tar, too.

```
func (tr *Reader) NextIter() iter.Seq2[*Header, error] {
	return func(yield func(*Header, error) bool) {
		hdr, err := tr.Next()
		if err == io.EOF {
			return
		}
		if !yield(hdr, err) {
			return
		}
	}
}
```

Thanks.
Repository: PowerToys
Issue: Peek support for ipynb(jupyter notebook)
Labels: Help Wanted,Product-Peek

### Description of the new feature / enhancement

Peek should support more file format, such as ipynb(jupyter notebook)

### Scenario when this would be used?

Peek does not support many file format, it shoudn't be.

### Supporting information

_No response_
Repository: next.js
Issue: Calling router.refresh() reset scroll to top for previous page
Labels: bug,Navigation

### Link to the code that reproduces this issue

https://github.com/markoradojcic/scroll-bug

### To Reproduce

1. Scroll list and click one of items
2. Click on button that calls router.refresh()
3. Go back to previous page


https://github.com/vercel/next.js/assets/16863336/e6618bfd-b180-44a6-806e-f6c48ea164e2



### Current vs. Expected behavior

Current behavior: scroll position resets to top
Expected behavior: preserve scroll position on previous page


### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.4.0: Wed Feb 21 21:44:43 PST 2024; root:xnu-10063.101.15~2/RELEASE_ARM64_T6000
  Available memory (MB): 16384
  Available CPU cores: 8
Binaries:
  Node: 21.5.0
  npm: 10.2.4
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.2.4 // Latest available version is detected (14.2.4).
  eslint-config-next: 14.2.4
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.4.5
Next.js Config:
  output: N/A
```


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

Navigation

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

next dev (local), next build (local), next start (local)

### Additional context

_No response_
Repository: ui
Issue: [bug]: Application error: a client-side exception has occurred (see the browser console for more information).
Labels: bug

### Describe the bug

When i click on the Combobox component in the form its getting client side error

### Affected component/components

Combobox

### How to reproduce

Go to 'https://ui.shadcn.com/docs/components/combobox#form'

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Brave browser
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues