sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Input history & options for tasks with input prompt (`promptString`)
Labels: feature-request,tasks

<!-- ⚠️⚠️ 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. -->
It would be very useful if task inputs could remember previously entered values, and suggest them with autofill/fuzzy matching (just like `pickString`, or when selecting a task). Or at the very least, pre-fill the last entered value as a default value (already in the box), maybe via something like `"default": ${previousValue}`; that alone would go a long way (and hopefully it would be a quick win).

Right now, we're just presented with an empty input box, and it can take time + brain power to figure out exactly what to type in the box, or to constantly re-type the same thing over & over (every single time the task needs to be re-run on the same input, as in the case of an "edit & re-run" workflow).
![image](https://user-images.githubusercontent.com/66686238/235753079-12e3fc92-da61-4900-970a-0e15059a8c47.png)

This is specifically for inputs that are too numerous or dynamic to fit/maintain in a selection (`pickString`), or too difficult to get from a `command` (not even sure where to start for this).

#180633 could also be included in this feature by allowing users to also configure possible/suggested `options` for `promptString` as well. That way, `pickString` could be reserved for when the list of options is static & finite, or when the labels & values are different.

`promptString` could even support the `command` configuration, allowing users to select from the combination all three  (or enter a custom value): input history, hard-coded `options`, and the result of a `command`.

Notes:
- Obviously, we don't want the input history to be recorded when `"password": true`.
- I don't think this feature could be considered to break backward compatibility, but if so, it could be enabled via a new configuration (something like `"inputHistory": true`). It could even be a new type entirely (something like `fuzzyPrompt`).
- Right now, our workaround is to copy-paste the input from somewhere (or type it in from scratch each time), or to run these operations in a terminal manually, which allows for autocomplete (but is obviously not desirable compared to running them as tasks in VS Code).
- #64358 would also provide some better workarounds for this. For example, default values could come from environment variables (which could be populated by any process).
Repository: storybook
Issue: [Feature Request]: Allow auto docs defaultName name to be per story
Labels: feature request,addon: docs

### Is your feature request related to a problem? Please describe

Is there any way to change the autodoc default name for each story group ?



![image](https://user-images.githubusercontent.com/114412495/235758037-cbb46878-34fd-441e-b2a0-6add16f5759c.png)


### Describe the solution you'd like

For example 
> Button 
> > Button Docs

> Link
> > Link Docs 


### Describe alternatives you've considered

_No response_

### Are you able to assist to bring the feature to reality?

yes, I can

### Additional context

_No response_
Repository: flutter
Issue: [webview_flutter_wkwebview] `-[WKPreferences javaScriptEnabled]` is deprecated in iOS 14
Labels: platform-ios,p: webview,package,P2,team-ios,triaged-ios

`webview_flutter_wkwebview` is using an API that was deprecated in iOS 14.  Use an `@availability` check to use the non-deprecated property, and fall back to the old one on < 14.

```objc
  [[self preferencesForIdentifier:identifier] setJavaScriptEnabled:enabled.boolValue];
```
https://github.com/flutter/packages/blob/c90dd9834ebfd3d9b06f5f99dae1dd7652de6053/packages/webview_flutter/webview_flutter_wkwebview/ios/Classes/FWFPreferencesHostApi.m#L44

Deprecation says `Use WKWebpagePreferences.allowsContentJavaScript to disable content JavaScript on a per-navigation basis`.  I don't think `WKWebpagePreferences` is currently created in the plugin.

```
FWFPreferencesHostApi.m:44:47: error: 'setJavaScriptEnabled:' is deprecated: first deprecated in iOS 14.0 - Use WKWebpagePreferences.allowsContentJavaScript to disable content JavaScript on a per-navigation basis [-Werror,-Wdeprecated-declarations]
  [[self preferencesForIdentifier:identifier] setJavaScriptEnabled:enabled.boolValue];
                                              ^
In module 'WebKit' imported from FWFPreferencesHostApi.h:6:
WKPreferences.h:92:28: note: property 'javaScriptEnabled' is declared deprecated here
@property (nonatomic) BOOL javaScriptEnabled API_DEPRECATED("Use WKWebpagePreferences.allowsContentJavaScript to disable content JavaScript on a per-navigation basis", macos(10.10, 11.0), ios(8.0, 14.0));
```

You can see this by running:
```sh
$ dart run script/tool/bin/flutter_plugin_tools.dart xcode-analyze "--ios-min-version=14.0" --ios
```

```yaml
    args: ["xcode-analyze", "--ios", "--ios-min-version=14.0"]
```
https://github.com/flutter/packages/blob/c90dd9834ebfd3d9b06f5f99dae1dd7652de6053/.ci/targets/ios_platform_tests.yaml#L15
Repository: next.js
Issue: [NEXT-1177] require.context does not work with client components
Labels: linear: next

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.4.0: Mon Mar  6 20:59:28 PST 2023; root:xnu-8796.101.5~3/RELEASE_ARM64_T6000
    Binaries:
      Node: 18.16.0
      npm: 9.5.1
      Yarn: N/A
      pnpm: 7.25.0
    Relevant packages:
      next: 13.3.2-canary.11
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

App directory (appDir: true)

### Link to the code that reproduces this issue

https://codesandbox.io/p/sandbox/require-context-next-js-client-component-bug-orqmoc?selection=%5B%7B%22endColumn%22%3A3%2C%22endLineNumber%22%3A5%2C%22startColumn%22%3A3%2C%22startLineNumber%22%3A5%7D%5D&file=%2Fapp%2Fdocs%2Ffeatures.mdx

### To Reproduce

Use [require.context](https://webpack.js.org/guides/dependency-management/#requirecontext) to grab a glob of files and return them in a Server Component:

```tsx
const mdxContext = require.context("./docs", true, /\.mdx$/);
const mdxComponents = mdxContext
  .keys()
  .filter((fileName) => !fileName.startsWith("app")) // filter duplicates
  .map((fileName) => mdxContext(fileName).default);

/** Add your relevant code here for the issue to reproduce */
export default function Home() {
  return mdxComponents.map((Component) => <Component />);
}
```

Everything should render fine until adding a Client Component by uncommenting the `Counter` component in `app/docs/features.mdx` which then should trigger the following error:

`Error: Cannot read properties of null (reading 'useState')`

### Describe the Bug

Rendering Client Components when using `require.context` throws an error.

### Expected Behavior

Using `require.context` should allow rendering Client Components. Alternatively, a first-class globbing mechanism could replace the need for this. This could be similar to Vite's globbing implementation attached to [import.meta.glob](https://vitejs.dev/guide/features.html#glob-import).

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_

<sub>[NEXT-1177](https://linear.app/vercel/issue/NEXT-1177/requirecontext-does-not-work-with-client-components)</sub>
Repository: storybook
Issue: [Bug]: storysource code not formatted
Labels: bug,help wanted,addon: storysource,sev:S3

### Describe the bug

When using v7 with react+vite, the storysource code is much more reliable than it was in v6! However, one issue I've noticed is that when using story function format, the code is _not formatted_ in a readable manner.

<img width="421" alt="" src="https://github.com/storybookjs/storybook/assets/9084735/c5d06fcf-4111-42e5-8039-136f0cb41c4e">

It would be nice if there was a way to run something like `prettier` on the code snippet (at build time) or just preserve original source formatting.

### To Reproduce

7.1.0-alpha.11: https://stackblitz.com/edit/github-vusgyh?file=src%2Fstories%2FButton.stories.tsx

7.1.0-alpha.27: https://stackblitz.com/edit/github-vusgyh-pixhqk?file=src%2Fstories%2FButton.stories.tsx

7.1.0-beta.0: https://stackblitz.com/edit/github-vusgyh-mcgr2x?file=src%2Fstories%2FButton.stories.tsx

### System

N/A. See stackblitz

### Additional context

_No response_
Repository: storybook
Issue: [Bug]: Storybook 7 addons in subdirectories cannot be added without manually adding file extension
Labels: bug,api: addons

### Describe the bug

Trying to run storybook dev or build:

```
@storybook/cli v7.0.7

WARN Could not resolve addon "@my-scope/my-package/subdirectory/register", skipping. Is it installed?
```

My storybook config:
```
{
  framework: {
    name: '@storybook/react-vite',
    options: {},
  },
  addons: ["@my-scope/my-package/subdirectory/register"]
}
```

If I add the js file extension to the following, it works fine:

```
{
  framework: {
    name: '@storybook/react-vite',
    options: {},
  },
  addons: ["@my-scope/my-package/subdirectory/register.js"]
}
```

It seems to also work fine for storybook addons that point their `"main"` field to the addon.

### To Reproduce

_No response_

### System

_No response_

### Additional context

_No response_
Repository: PowerToys
Issue: Fancy zone + triple monitor + create new desktop with task view = incorrect layout
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.69.1

### Installation method

PowerToys auto-update

### Running as admin

No

### Area(s) with issue?

FancyZones

### Steps to reproduce

Looks like if you have a triple monitor setup, and create a new desktop with windows 10 task view, the new desktop that's created doesn't duplicate the fancy view layout properly. At least, the setup was incorrect when I did this. On my two side monitors, I have 3 rows and the center I have nothing. After creating a new desktop, one of the side monitors was "nothing" and the center monitor was 3 rows.

### ✔️ Expected Behavior

My two side monitors were set to three rows. The center was nothing.

### ❌ Actual Behavior

The center was three rows. One side monitor was three rows. The other side monitor was nothing.

### Other Software

_No response_
Repository: flutter
Issue: iOS PlatformViewsController needs to be more resilient when creating the same view multiple times.
Labels: platform-ios,engine,a: platform-views,P2,team-ios,triaged-ios

**Background**

PlatformViews are created asynchronizely through method channel via a [onCreate](https://github.com/flutter/engine/blob/main/shell/platform/darwin/ios/framework/Source/FlutterPlatformViews.mm#L194) message.  

OnCreate essentially constructs a UIView and put it in to the root_view_ map with an id. If the same id is "created" again, the root_view_[$id] is replaced with a newly constructed UIView.

Skip forward to how the root_views are ordered and added to the view tree, the logics are in [BringLayersIntoView](https://github.com/flutter/engine/blob/main/shell/platform/darwin/ios/framework/Source/FlutterPlatformViews.mm#L790-L796). We rely on the fact that [UIView addSubview] reorders the view to the top most if the subview is already in the view tree. See: https://github.com/flutter/engine/blob/main/shell/platform/darwin/ios/framework/Source/FlutterPlatformViews.mm#L786-L796. So it doesn't matter if the view is in the view tree, [UIView addSubvIew] takes care adding the view and putting the views at the correct order.

**Bug**

This causes a potential race condition. Consider the below situation:

root_view_[0] is viewA. And viewA is currently in the view tree, or in another word, a subview of flutter view.
OnCreate is called with id 0, viewB is created, root_view_[0] is changed from viewA to viewB. 
During the same frame, `BringLayersIntoView` is going to get the view from root_view_[0], which is now viewB. Because the view representing id 0 was viewA, viewB is not in the view tree, `[UIView addSubview]` will add viewB to the view tree. And now we have both viewA and viewB representing id 0 in the view tree. The correct behavior is to only have viewB in this situation.
Repository: rust
Issue: Unhelpful error with braces after type in parameters
Labels: A-diagnostics,A-parser,T-compiler

### Code

```Rust
fn uwu<T>(x: T{}) {}
```


### Current output

```Shell
error: expected parameter name, found `{`
 --> src/lib.rs:1:15
  |
1 | fn uwu<T>(x: T{}) {}
  |               ^ expected parameter name

error: expected one of `!`, `(`, `)`, `+`, `,`, `::`, or `<`, found `{`
 --> src/lib.rs:1:15
  |
1 | fn uwu<T>(x: T{}) {}
  |               ^
  |               |
  |               expected one of 7 possible tokens
  |               help: missing `,`
```


### Desired output

_No response_

### Rationale and extra context

_No response_

### Other cases

_No response_

### Anything else?

_No response_
Repository: rust
Issue: Bad error when using a const generic wrong
Labels: A-diagnostics,A-const-generics,D-confusing

The following code:

```rust
fn uwu<const N: usize>() {
    let _ = [0; N{}];
}
```

produces the error

```
error: generic parameters may not be used in const operations
 --> src/lib.rs:2:17
  |
2 |     let _ = [0; N{}];
  |                 ^ cannot perform const operation using `N`
  |
  = help: const parameters may only be used as standalone arguments, i.e. `N`
  ```
  
  however, when enabling `feature(generic_const_exprs)`, the error changes to
  
  ```
  error[[E0574]](https://doc.rust-lang.org/nightly/error_codes/E0574.html): expected struct, variant or union type, found const parameter `N`
 --> src/lib.rs:4:17
  |
4 |     let _ = [0; N{}];
  |                 ^ not a struct, variant or union type
  ```
  
The error on stable should change to be the same as the error with `generic_const_exprs` enabled.

On stable, it's probably more likely that the user doesn't want the generic to be const, or wants to remove the `{}` than them trying to actually do anything with `generic_const_exprs`.
Repository: deno
Issue: Deno KV browser implementation
Labels: ext/kv

I want to write code that can be reused between clients and servers. As Deno KV does not implement a standard Web API available in web browsers, I think it would be great to publish a module for kind of polyfilling Deno KV in browsers but backed by IndexedDB. This way apps can be built to store and sync data using a consistent API, etc.
Repository: godot
Issue: Updating rotation and position of AnimatableBody2D in code only updates using the last instruction when sync to physics is enabled
Labels: bug,topic:core,confirmed,topic:physics

### Godot version

4.0.2.stable, 4.1.dev1

### System information

Windows 10

### Issue description

In an attempt to create a moving and rotating platform that syncs to physics, I created an AnimatableBody2D and updated the code to manipulate my object rather than use an animation.

The code I'm using is this:
```
func _physics_process(delta):
	global_rotation_degrees += delta*10
	global_position.x += delta*10
```

What I expect:
A clockwise rotating object that goes from left to right.

What I get:
Only the last instructions updates the object, in this case, the position.

Doing this on the parent class (StaticBody2D) OR disabling the sync to physics makes it work, but you lose the sync to physics.

I might be doing this wrong, but couldn't find info around it, so sorry if this is a non-issue.

### Steps to reproduce

- Create AnimatableBody2D node
- Add a sub node for visibility (Sprite2D with Godot logo)
- Add script to AnimatableBody2D with
'''
func _physics_process(delta):
	global_rotation_degrees += delta*10
	global_position.x += delta*10
'''
- Object will only translate to the right instead of translating and rotating

### Minimal reproduction project

N/A
Repository: flutter
Issue: On iOS running an app logs `[SceneConfiguration] Info.plist contained no UIScene configuration dictionary (looking for configuration named "(no name)")`
Labels: platform-ios,tool,P2,team-ios,triaged-ios

Running on iOS 16.2 and higher logs:
```
Runner[406:6604] [SceneConfiguration] Info.plist contained no UIScene configuration dictionary (looking for configuration named "(no name)")
```

See in CI as well: https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8782173984577042033/+/u/run_microbenchmarks_ios/test_stdout

This forum thread https://developer.apple.com/forums/thread/721912 suggests it wants a `UIApplicationSceneManifest` addition to the Info.plist.  That creates a `UISceneConfigurations` dictionary that seems safe to leave blank? But it also adds a `UIApplicationSupportsMultipleScenes` property and I don't know (doubt) if it's totally safe to default set that to YES...

Whatever the right thing to add here we can include in the `flutter create` template.  I don't know if it's safe/desirable to migrate.
Repository: flutter
Issue: Simplify the names drone names after engine v2 migration is complete
Labels: team-infra,P3,triaged-infra,:hourglass_flowing_sand:

There are multiple copies of drone which makes it very difficult to maintain. All the environment specific drones should be removed in favor of drones without an environment.
Repository: flutter
Issue: [camerax] ☂️ Clean up wrapped native classes
Labels: c: new feature,platform-android,p: camera,package,P3,c: tech-debt,team-android,triaged-android

As the `android_camera_camerax` plugin has been under development, there have a number of tasks that have not blocked PRs but are important technical debt to pay down. This umbrella issue covers those tasks that apply to refactoring wrapped native classes:

- [ ] Refactor logic in constructors/`create` methods to helper methods or to callers of those methods.
- [ ] Remove any redundant documentation added or left by the autogenerator.
- [ ] [Dart-specific] Make Dart Host API implementations private.
- [ ] There are currently two ways to create files to save recordings to; condense to one.
- [ ] [Native-specific] Move checks for objects being managed by an `InstanceManager` to the Flutter API implementations themselves versus where instances of those implementations are used.
- [ ] Use command pattern to use handlers to create objects of each type that is represented by a `LiveDataSupportedType` (see [original comment](https://github.com/flutter/packages/pull/3878#discussion_r1184179333)).
Repository: flutter
Issue: [camerax] ☂️ Clean up Dart Tests
Labels: c: new feature,platform-android,p: camera,package,P3,c: tech-debt,team-android,triaged-android

As the `android_camera_camerax` plugin has been under development, there have a number of tasks that have not blocked PRs but are important technical debt to pay down. This umbrella issue covers those tasks that apply to cleaning up tests in this plugin:

- [ ] Consider implementing a `setUp()` method for the [plugin Dart test ](https://github.com/flutter/packages/blob/main/packages/camera/camera_android_camerax/test/android_camera_camerax_test.dart) since several of the same setup steps are involved.
- [x] #138633
- [ ] Condense test mock files that contain same mocks, namely mocks for `TestInstanceManagerHostApi`.
- [ ] Reduce assertion calls in tests that loop over various types ([example](https://github.com/flutter/packages/pull/3878/files#r1184165664))
- [ ] Add test for behavior of using weak references of plugin implementation in callback methods to avoid memory leaks (see [discussion](https://github.com/flutter/packages/pull/3878/files#r1184291971)).
- [ ] Reduce parameters that are not necessary to be visible for testing (now that I've added a proxy, some of these can be private).
Repository: flutter
Issue: Android_embedding_bundle is out of date and difficult to update.
Labels: platform-android,engine,P2,team-android,triaged-android

The script seems to not work without altering some paths.

I tried to update it and roll the androidx.window dependency and it ran into a conflicting name. I tried a few things locally to resolve that (which, in frustration, forgot to preserve) - none of which really seemed to work in the end. I'm abandoning this because I don't actually need to roll the dependency for what I'm doing right now, but roughly speaking:

- `generate.sh` should be updated to point to `//third_party/gradle` instead of whatever gradle is installed locally.
- Some of the path references in `build.gradle` and `configure.gradle` don't seem to be right anymore.
- The `copy` task in `build.gradle` needs to have some way of handling when multiple AARs have the same name.
- I can't seem to figure out where the `com.google.android.play.core` is coming from anymore. I suspect the script no longer fetches it and we just haven't updated it in so long that it doesn't matter anymore.
Repository: vscode
Issue: Expose ability to replace an existing Output along with the metadata
Labels: debt,notebook-output,notebook-api

Assume we have 3 outputs in a Notebook cell
And we'd like to replace the second output, the API that is available today is 
```typescript
/**
 * Replace all output items of existing cell output.
 *
 * @param items Output items that replace the items of existing output.
 * @param output Output object that already exists.
 * @return A thenable that resolves when the operation finished.
 */
replaceOutputItems(items: NotebookCellOutputItem | readonly NotebookCellOutputItem[], output: NotebookCellOutput): Thenable<void>;
```

However if there's no way to update the metadata of the second output, 
the above API only provides the ability to replace the items inside that output.

The other API that could be used is `replaceOutput`
```typescript
/**
 * Replace the output of the cell that is executing or of another cell that is affected by this execution.
 *
 * @param out Output that replaces the current output.
 * @param cell Cell for which output is cleared. Defaults to the {@link NotebookCellExecution.cell cell} of
 * this execution.
 * @return A thenable that resolves when the operation finished.
 */
replaceOutput(out: NotebookCellOutput | readonly NotebookCellOutput[], cell?: NotebookCell): Thenable<void>;
```

However this cannot be used, as the Jupyter extension now needs to keep track of all 3 outputs.
The outputs are added very quickly and its possible the previous outputs have not yet been added into the cell, thus the only API that works today is `replaceOutputItems`

Proposal, extend `replaceOutput` to support replacing an existing output, similar to `replaceOutputItems`
This is an overload of the existing `replaceOutput`
```typescript
/**
* Replace all output items of existing cell output.
*
* @param newOutupt Output items that replace the existing output.
* @param output Output object that already exists.
* @return A thenable that resolves when the operation finished.
*/
replaceOutput(newOutput: NotebookCellOutput, output: NotebookCellOutput): Thenable<void>;
```
Repository: excalidraw
Issue: excalidraw.com does not display anything on Safari for macOS
Labels: safari

Hello,

I encountered an issue while attempting to access excalidraw.com using Safari. The website only displays a white page, with no content visible. However, the site functions correctly on Google Chrome.

System specifications:

macOS Ventura 13.3.1 (arm64)
Safari Version 16.4
Lockdown Mode: On

Could you please provide guidance on how to resolve this issue?

Thank you for your help.
Repository: create-react-app
Issue: Error compiling my first-react-app
Labels: needs triage


![react problem](https://user-images.githubusercontent.com/109921600/235821181-cfba23e3-6172-4f12-8180-e6b5d544964a.PNG)