sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: bitcoin
Issue: Allow creating and injecting a custom coinbase into a block template
Labels: Feature

### Please describe the feature you'd like to see added.

I would like a command in bitcoin core for creating a raw coinbase transaction and another command for injecting it into a block template.

### Is your feature related to a problem, if so please describe it.

I am working on a project that lets users purchase coinbase utxos directly from miners, who are expected to send their customers these utxos in whatever block they mine next. It is difficult to test my software on regtest because I can't specify what outputs coinbase transactions should create. The console commands "generateblock," "generatetoaddress," and "generatetodescriptor" all automatically create a coinbase transaction that sends the block subsidy plus fees to a single address which you must specify as an argument. They do not, however, let you customize your coinbase transaction.

### Describe the solution you'd like

I would love to use the "createrawtransaction" method to create a coinbase transaction with several outputs where I send most of the subsidy as well as a final output that lets me specify a value of "remainder" or something like that to catch whatever is left over after the initial outputs are created.

With this custom coinbase transaction in hand, I'd love to put it in an array of transactions and pass that array to the "generateblock" command. The latter command would need to "notice" that the first transaction in the array is a coinbase transaction and use it as a replacement for whatever coinbase transaction it was going to create automatically.

### Describe any alternatives you've considered

I could reach out to a miner and ask them to send me whatever software they use to create custom coinbase transactions but I fear their professional setups would be vastly more complex than mine and it just wouldn't work.

### Please leave any additional context

I checked on stack overflow and found [this q-and-a](https://bitcoin.stackexchange.com/questions/97076/how-create-coinbase-transaction-with-createrawtransaction/98334) which says, in part, "It is not possible to create a coinbase transaction using createrawtransaction. ... Miners must use software that can independently create the coinbase transaction. Miners actually prefer doing this because they want to be able to modify the coinbase to use as an extra nonce..." Miners may already have software for independently creating custom coinbase transactions, but as someone who just wants to do it on my local regtest environment, it's frustrating that there are no good methods for this.
Repository: storybook
Issue: [Bug]: vite transformation errors on serve and build after upgrading from version 6 to 7 
Labels: bug,question / support,compatibility with other tools,builder-vite

### Describe the bug

After upgrading (`npx storybook@latest upgrade`) from v6 to v7 
I've started to get the following errors on build:

```
ERROR: The symbol "React" has already been declared
ERROR: The symbol "SvgPencil" has already been declared
ERROR: Multiple exports with the same name "ReactComponent"
```

pointing to an svg file (export { SvgPencil as ReactComponent };)

I'm using vite and in `.storybook/main.js` following plugins are declared 
` plugins: [svgrPlugin(), react()]`
(vite-plugin-svgr, @vitejs/plugin-react)

When running storybook 

![image](https://github.com/storybookjs/storybook/assets/9695142/00947f82-5612-401b-b54e-f23468430ba0)

I'm getting 

```
 [vite] Internal server error: Transform failed with 3 errors
  ERROR: The symbol "inWebWorker" has already been declared
  ERROR: The symbol "prevRefreshReg" has already been declared
   ERROR: The symbol "prevRefreshSig" has already been declared
   Plugin: vite:esbuild
```

I'm using vite latest version (4.4.9) 

Not sure what's causing those issues, and will appreciate any help!

### To Reproduce

_No response_

### System

```bash
Environment Info:

  System:
    OS: macOS 13.3.1
    CPU: (10) arm64 Apple M2 Pro
  Binaries:
    Node: 18.14.0 - ~/.volta/tools/image/node/18.14.0/bin/node
    npm: 9.3.1 - ~/.volta/tools/image/node/18.14.0/bin/npm
  Browsers:
    Chrome: 116.0.5845.187
    Safari: 16.4
  npmPackages:
    @storybook/addon-actions: ^7.4.1 => 7.4.1 
    @storybook/addon-essentials: ^7.4.1 => 7.4.1 
    @storybook/addon-interactions: ^7.4.1 => 7.4.1 
    @storybook/addon-links: ^7.4.1 => 7.4.1 
    @storybook/jest: ^0.2.2 => 0.2.2 
    @storybook/react: ^7.4.1 => 7.4.1 
    @storybook/react-vite: ^7.4.1 => 7.4.1 
    @storybook/test-runner: ^0.13.0 => 0.13.0 
    @storybook/testing-library: ^0.2.0 => 0.2.0
```


### Additional context

_No response_
Repository: storybook
Issue: [Documentation]: Documentation for `argTypes` is not correct
Labels: help wanted,typescript,argtypes

### Describe the problem

The docs say:

<img width="707" alt="image" src="https://github.com/storybookjs/storybook/assets/45210624/339e5381-f5d8-4759-9616-05e64ee43e33">


But the actual type is:

```
interface InputType {
    name?: string;
    description?: string;
    defaultValue?: any;
    type?: SBType | SBScalarType['name'];
    if?: Conditional;
    [key: string]: any;
}
```

I'm willing to work on this if it's indeed wrong.

### Additional context

Edit: Taking another look at this - you can indeed pass `options` and `control` and it does work but it is not documented in the type.
Repository: vscode
Issue: Fractional scaling on X11 is blurry and cuts right borders.
Labels: bug,linux,workbench-os-integration,confirmation-pending

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.82.1
- OS Version: Fedora 38

Steps to Reproduce:

1. Set X11 scaling to 125%
2. Open VSCode

Result: Fonts look a bit blurry, and drop down menus are missing the right and bottom borders.
![Cut Borders](https://github.com/microsoft/vscode/assets/80237215/cae736d6-2ad3-47f2-9a1a-f13ed4a8f1cc)


Workaround: launch vscode with option: `--force-device-scale-factor 1`.
Repository: material-ui
Issue: [Select][material-next] Add Select component
Labels: on hold,component: select,design: material you

Part of https://github.com/mui/material-ui/issues/29345

Material You specs: https://m3.material.io/components/menus/specs

#### Migration Guide checklist

- [x] Copy component files from material (v5) to material-next, including tests, types, and utils: PR: [#39188](https://github.com/mui/material-ui/pull/39188)
- [ ] Migrate component to Typescript
- [ ] Remove deprecated components and componentsProps props, leaving only slots and slotProps
- [ ] Drop support for ThemeProvider in favor of CssVarsProvider
- [ ] Refactor component to use Base UI’s `useSelect`: WIP [#39591](https://github.com/mui/material-ui/issues/39591)
- [ ] Implement Material You design specs
- [ ] Add component playground to v5 docs
- [ ] Refactor styles to use component CSS Variables

#### Other features & related tasks

- Introduce a new `Option` component based on `@mui/base/useOption`
- Introduce a new (internal) `Menu` based on `@mui/base/useMenu` for the Select's listbox
- `native` prop for native `select` isn't provided by Base yet
- FormControl integration https://github.com/mui/material-ui/issues/38411
- Replace Input dependencies with `material-next` Input components when those are done: https://github.com/mui/material-ui/issues/38374
- `useSelect` uses `useControlledReducer` internally, the warning when switching between controlled/uncontrolled needs to be added back ([this comment)](https://github.com/mui/material-ui/pull/38723#issuecomment-1703184280)
- Support for `Divider` https://github.com/mui/material-ui/issues/39007
- Option grouping - v5 uses `ListSubheader`, should v6 replace it with a `OptionGroup` component? (This would be a breaking change, and also not in the MD3 spec)
- New `SelectField` component https://github.com/mui/material-ui/issues/21782
- Avoid native `label` with non-native `Select` https://github.com/mui/material-ui/issues/38869#issuecomment-1792184844
Repository: flutter
Issue: [image_picker] picking methods future is not completed if closing native model quickly on iOS devices
Labels: platform-ios,p: image_picker,package,has reproducible steps,P2,team-ios,triaged-ios,found in release: 3.13,found in release: 3.14

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Steps to reproduce

1. Open the gallery with `pickMultipleMedia`.
2. Close the native modal very quickly

### Expected results

The future ends normally.

### Actual results

The future never ends.

### Code sample

<details><summary>Code sample</summary>

```dart
import 'package:flutter/material.dart';
import 'package:image_picker/image_picker.dart';

void main() {
  runApp(const MainApp());
}

class MainApp extends StatelessWidget {
  const MainApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        body: Center(
          child: OutlinedButton(
            onPressed: () async {
              debugPrint('Gallery opened');
              await ImagePicker().pickMultipleMedia();
              debugPrint('Gallery closed');
            },
            child: const Text('Open gallery'),
          ),
        ),
      ),
    );
  }
}

```

</details>


### Screenshots or Video

<details>
<summary>Screenshots / Video demonstration</summary>

https://github.com/flutter/flutter/assets/26067909/454a2489-3e4e-4e48-8de0-34f8412dbb2d

</details>


### Logs

<details><summary>Logs</summary>

```console
[Paste your logs here]
```

</details>


### Flutter Doctor output

<details><summary>Doctor output</summary>

```console
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.13.1, on macOS 13.0.1 22A400 darwin-arm64, locale fr-FR)
[✓] Android toolchain - develop for Android devices (Android SDK version 32.1.0-rc1)
[✓] Xcode - develop for iOS and macOS (Xcode 14.3.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2021.1)
[✓] VS Code (version 1.82.1)
[✓] Connected device (2 available)
[✓] Network resources

• No issues found!
```

</details>
Repository: ant-design
Issue: 页签类型的Card提供render props
Labels: Inactive,unconfirmed

### What problem does this feature solve?

现在的api使用起来不方便，希望提供chidren render props或者单独提供一个配置项

### What does the proposed API look like?

```
<Card tabList={[{...},{...},{...}]}>
  {
    (item, index) => {
      return <>{index}</>
    }
  }
</Card>
```

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: vscode
Issue: Occurrences Highlight obscurely affected by Editor Search options
Labels: editor-find,under-discussion

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.81.1, 1.82.1, **1.91.0** 
- OS Version: macOS Ventura 13.5.2 (22G91)

**Steps to Reproduce:**

1. Make sure `Occurrences Highlight` is enabled
2. Open an editor and type the following words, eg. space separated: `Abc abcd abc`
3. Open the search panel (Ctrl or Cmd + f) and make sure that the Match Case and Match Whole Words options are disabled
4. Close the search panel (Esc)
5. Click into or select the whole first word `Abc`
6. All three occurrences of _"abc"_ will be highlighted regardless of position or case
7. Repeat with the options being enabled one-by-on, while also having the search panel closed afterwards
8. Occurrences will be highlighted according to the options, **hidden from the user**

**Expected behaviour:**

`Occurrences Highlight` should either be allowed to be independently configured **OR** the current configuration should be transparent to the user.

**Actual behaviour:**

While coding, and potentially looking for occurrences, the user might miss an important piece because the highlight is potentially affected by whatever the last intentionally set search options were. **The user might not be aware of the current configuration.**

Note: This is not a "functional bug", but rather a "UX bug".
Repository: godot
Issue: Using Window.unresizable to make a resizable game window unresizable increases the window size by 11 pixels
Labels: bug,platform:windows,topic:porting

### Godot version

4.1.1.stable, 4.2.dev4

### System information

Godot v4.1.1.stable - Windows 10.0.19043 - Vulkan (Mobile) - integrated AMD Radeon(TM) Graphics (Advanced Micro Devices, Inc.; 30.0.13014.8) - AMD Ryzen 7 5700U with Radeon Graphics (16 Threads)

### Issue description

When using `Window.unresizable` to make a resizable game window unresizable, the window size increases by 11 pixels in each direction. This happens when the game window is set as resizable in the project settings, and then set to unresizable in a script; setting it as unresizable in the project settings does not immediately cause this problem.

This happens in the Forward+, Mobile, and Compability renderers.

### Steps to reproduce

1. In project settings, set `display/window/size/resizable` to `true`
2. In a script, set the current window to unresizable (e.g. with `get_window().unresizable = true`)
3. The window gets bigger

---

The attached example project uses two ColorRects, one hiding the other, to make the effect more obvious. Setting `unresizable` to true should show the magenta rect peeking out on the bottom and right edges.

```
var unresizable:bool = false
```  
![2023-09-14 03_33_03](https://github.com/godotengine/godot/assets/35484302/cc2e53f1-2b48-4454-a2c6-fec6439e4c3c)

```
var unresizable:bool = true
```  
![2023-09-14 03_32_41](https://github.com/godotengine/godot/assets/35484302/a66ac27d-4b95-4ae9-9eb7-0f7af01e155c)


### Minimal reproduction project

[Resize Border.zip](https://github.com/godotengine/godot/files/12607623/Resize.Border.zip)
Repository: tauri
Issue: [feat] Need a function to disable moving windows
Labels: type: feature request

### Describe the problem

Like electron movavle.

https://www.electronjs.org/docs/latest/api/browser-window#winsetmovablemovable-macos-windows

### Describe the solution you'd like

Ability to control whether windows can be moved.

### Alternatives considered

_No response_

### Additional context

_No response_
Repository: flutter
Issue: Password bar in the keyboard is flashing when using `TextField` with `AutofillHints.password` on iOS 17
Labels: a: text input,platform-ios,e: OS-version specific,has reproducible steps,P2,found in release: 3.13,found in release: 3.14,team-text-input

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Steps to reproduce

1. Use an iOS 17 device
2. Add a `TextField` with `AutofillHints.password`
3. Start typing

### Expected results

No flashing.

### Actual results

The password bar of the keyboard flashes but sometimes also the `TextField` (see video).

### Code sample

```dart
import 'package:flutter/material.dart';

void main() {
  runApp(
    const MaterialApp(
      home: Scaffold(
        body: Center(
          child: TextField(
            autofillHints: [AutofillHints.password],
          ),
        ),
      ),
    ),
  );
}
```

https://github.com/nilsreichardt/flutter-ios17-textfield-bug

### Screenshots or Video

https://github.com/flutter/flutter/assets/24459435/4f872d72-93ae-459c-ab7b-b0f71798505e



### Logs

<details><summary>Logs</summary>

```console
2023-09-14 13:44:46.470430+0200 Runner[1447:88815] Metal API Validation Enabled
2023-09-14 13:44:46.567930+0200 Runner[1447:88815] [VERBOSE-2:FlutterDarwinContextMetalImpeller.mm(42)] Using the Impeller rendering backend.
2023-09-14 13:44:46.680337+0200 Runner[1447:89203] flutter: The Dart VM service is listening on http://127.0.0.1:62669/HKQ_5uMac8k=/
```

</details>


### Flutter Doctor output

<details><summary>Doctor output</summary>

```console
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.13.4, on macOS 13.5.2 22G91 darwin-arm64 (Rosetta), locale en-DE)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
[✓] Xcode - develop for iOS and macOS (Xcode 14.3.1)
[✓] Chrome - develop for the web
[!] Android Studio (version unknown)
    ✗ Unable to determine Android Studio version.
    ✗ Unable to find bundled Java version.
[✓] Android Studio (version 2022.3)
[✓] IntelliJ IDEA Community Edition (version 2023.1)
[✓] IntelliJ IDEA Ultimate Edition (version 2022.2.3)
[✓] IntelliJ IDEA Ultimate Edition (version 2022.2.3)
[✓] VS Code (version 1.82.1)
[✓] VS Code (version 1.82.0-insider)
[✓] Connected device (2 available)
[✓] Network resources
```

</details>

### Additional context

* Used iPhone 13 with iOS 17.0
* Appears with Flutter v3.13.4 (latest stable version) and Flutter v3.14.0-14.0.pre.290 (latest master version)
Repository: deno
Issue: feat: easier way to destroy child processes
Labels: public API,suggestion,runtime

After a debugging session regarding leaking resources in tests it turned out that [a test case in the Fresh repository](https://github.com/denoland/fresh/blob/e59472e35a040880318936e8a2c03c2bf1b04783/tests/main_test.ts#L866-L868) wasn't properly waiting for child processes to be killed.

The current way to do it should look like this:

```js
const childProcess = new Deno.Command(...).spawn();

// Send kill signal
childProcess.kill("SIGTERM");
// Wait until it's shut down finished. This is often forgotten
await childProcess.status;
```

This lead us to wonder if we could provide an easier API for that. Especially, in a test suite it's not relevant how the child process is killed. You just want this thing to be destroyed. Some random ideas:

```ts
// New method
await childProcess.killAndWait();

// Make kill() return Promise, doesn't work with every signal though so meh
await childProcess.kill("SIGTERM")

// Add necessary symbols to support "using"
using childProcess = new Deno.Command(...).spawn();
```
Repository: vscode
Issue: Cannot read properties of undefined (reading 'compileAG')
Labels: bug,error-telemetry,tokenization

```javascript
TypeError: Cannot read properties of undefined (reading 'compileAG')
at l in vscode-file://vscode-app//node_modules.asar/vscode-textmate/release/main.js:1:24135
at <anonymous> in vscode-file://vscode-app//node_modules.asar/vscode-textmate/release/main.js:1:20316
at <anonymous> in vscode-file://vscode-app//node_modules.asar/vscode-textmate/release/main.js:1:20852
at y in vscode-file://vscode-app//node_modules.asar/vscode-textmate/release/main.js:1:21653
at Object.c [as _tokenizeString] in vscode-file://vscode-app//node_modules.asar/vscode-textmate/release/main.js:1:20047
at m._tokenize in vscode-file://vscode-app//node_modules.asar/vscode-textmate/release/main.js:1:7377
at m.tokenizeLine2 in vscode-file://vscode-app//node_modules.asar/vscode-textmate/release/main.js:1:6513
at m.tokenizeEncoded in src/vs/workbench/services/textMate/browser/tokenizationSupport/textMateTokenizationSupport.ts:54:40
at T.tokenizeEncoded in src/vs/workbench/services/textMate/browser/tokenizationSupport/tokenizationSupportWithLineLimit.ts:42:23
at f in src/vs/editor/common/model/textModelTokens.ts:427:28
at safeTokenize in src/vs/editor/common/model/textModelTokens.ts:69:14
at a.forceTokenization in src/vs/editor/common/model/tokenizationTextModelPart.ts:566:20
at u.forceTokenization in src/vs/editor/common/model/tokenizationTextModelPart.ts:142:22
at C.f in src/vs/editor/contrib/indentation/browser/indentation.ts:634:22
at C.trigger in src/vs/editor/contrib/indentation/browser/indentation.ts:527:13
at o.value in src/vs/editor/contrib/indentation/browser/indentation.ts:493:9
at Y.w in src/vs/base/common/event.ts:1107:13
at Y.fire in src/vs/base/common/event.ts:1138:9
at Y.fire in src/vs/editor/browser/widget/codeEditorWidget.ts:1976:9
at H.Nb in src/vs/editor/browser/widget/codeEditorWidget.ts:1159:21
at H.trigger in src/vs/editor/browser/widget/codeEditorWidget.ts:1085:10
at p.C in src/vs/editor/contrib/dropOrPasteInto/browser/copyPasteController.ts:472:16
at async in src/vs/editor/contrib/dropOrPasteInto/browser/copyPasteController.ts:277:6
```
[Go to Errors Site](https://errors.code.visualstudio.com/card?ch=8b617bd08fd9e3fc94d14adb8d358b56e3f72314&bH=7fdb9944-9e1f-41d5-2839-1272b5c82ab1)