sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: [flutter_tools] SocketException: The remote computer refused the network connection during debug-adapter
Labels: P2,team-tool,triaged-tool

On version `stable/3.19.3`
With command `flutter debug_adapter`

```
SocketException: The remote computer refused the network connection.
 (OS Error: The remote computer refused the network connection.
, errno = 1225), address = 127.0.0.1, port = 57309
at _NativeSocket.startConnect(socket_patch.dart:721)
at _RawSocket.startConnect(socket_patch.dart:1914)
at RawSocket.startConnect(socket_patch.dart:27)
at Socket._startConnect(socket_patch.dart:2138)
at Socket.startConnect(socket.dart:805)
at _ConnectionTarget.connect(http_impl.dart:2487)
at _HttpClient._getConnection.connect(http_impl.dart:2926)
at _HttpClient._getConnection(http_impl.dart:2931)
at _HttpClient._openUrl(http_impl.dart:2786)
at _HttpClient.openUrl(http_impl.dart:2623)
at _WebSocketImpl.connect(websocket_impl.dart:1021)
at WebSocket.connect(websocket.dart:320)
at DartDebugAdapter._vmServiceConnectUri(dart.dart:2583)
at DartDebugAdapter.connectDebugger(dart.dart:647)
at FlutterDebugAdapter._connectDebugger(flutter_adapter.dart:381)
at FlutterDebugAdapter._handleDebugPort(flutter_adapter.dart:462)
at <asynchronous gap>(async)
```
Repository: rust
Issue: `-Zthreads` causes cycle errors in previously passing code
Labels: C-bug,WG-compiler-parallel,I-cycle

````
cargo new t
cd t
cargo add ppv-lite86
RUSTFLAGS="-Zthreads=16" ~/.cargo/bin/cargo +master build
````

````
   Compiling ppv-lite86 v0.2.17
error[E0391]: cycle detected when type-checking `x86_64::sse2::<impl at /home/matthias/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ppv-lite86-0.2.1>
   --> /home/matthias/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ppv-lite86-0.2.17/src/x86_64/sse2.rs:290:9
    |
290 |         fn $name(self) -> Self {
    |         ^^^^^^^^^^^^^^^^^^^^^^
...
313 |     rotr_128!(rotate_each_word_right32, 32);
    |     --------------------------------------- in this macro invocation
    |
note: ...which requires evaluating type-level constant...
   --> /home/matthias/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ppv-lite86-0.2.17/src/x86_64/sse2.rs:294:21
    |
294 |                     _mm_slli_si128(self.x, 128 - $i as i32),
    |                     ^^^^^^^^^^^^^^
...
313 |     rotr_128!(rotate_each_word_right32, 32);
    |     --------------------------------------- in this macro invocation
note: ...which requires const-evaluating + checking `x86_64::sse2::<impl at /home/matthias/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ppv-lite86-0>
   --> /home/matthias/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ppv-lite86-0.2.17/src/x86_64/sse2.rs:294:21
    |
294 |                     _mm_slli_si128(self.x, 128 - $i as i32),
    |                     ^^^^^^^^^^^^^^
...
313 |     rotr_128!(rotate_each_word_right32, 32);
    |     --------------------------------------- in this macro invocation
note: ...which requires caching mir of `x86_64::sse2::<impl at /home/matthias/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ppv-lite86-0.2.17/src/x86>
   --> /home/matthias/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ppv-lite86-0.2.17/src/x86_64/sse2.rs:294:21
    |
294 |                     _mm_slli_si128(self.x, 128 - $i as i32),
    |                     ^^^^^^^^^^^^^^
...
313 |     rotr_128!(rotate_each_word_right32, 32);
    |     --------------------------------------- in this macro invocation
note: ...which requires elaborating drops for `x86_64::sse2::<impl at /home/matthias/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ppv-lite86-0.2.17/>
   --> /home/matthias/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ppv-lite86-0.2.17/src/x86_64/sse2.rs:294:21
    |
294 |                     _mm_slli_si128(self.x, 128 - $i as i32),
    |                     ^^^^^^^^^^^^^^
...
313 |     rotr_128!(rotate_each_word_right32, 32);
...
...
...
...
```
Repository: next.js
Issue: Couldn't find all resumable slots by key/index during replaying.
Labels: bug

### Link to the code that reproduces this issue

https://github.com/jahirfiquitiva/jahir.dev/pull/81

### To Reproduce

1. Deploy on Vercel.
2. Visit the deployment URL
3. Visit a blog post (example: https://website-bmqg5pjuv-jahirfiquitiva.vercel.app/blog/how-tailwind-grew-on-me)
4. Refresh/reload the page (cmd+R)

### Current vs. Expected behavior

**Current:**

The website shows `not found` after reloading, and this error is logged in Vercel

```gradle
Error: Couldn't find all resumable slots by key/index during replaying. The tree doesn't match so React will fallback to client rendering.
    at nW (/var/task/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:12:70706)
    at nz (/var/task/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:12:69570)
    at nG (/var/task/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:12:73218)
    at nW (/var/task/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:12:71383)
    at nz (/var/task/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:12:69570)
    at nH (/var/task/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:12:63588)
    at nz (/var/task/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:12:67383)
    at nB (/var/task/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:12:51051)
    at nH (/var/task/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:12:51758)
    at nH (/var/task/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:12:66179) {
  digest: '4172697567'
}
```

https://github.com/vercel/next.js/assets/10360816/e24018b4-76e3-4b68-99b4-a54d952e3578


**Expected:**

The website keeps loading the site normally

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.3.0: Wed Dec 20 21:30:44 PST 2023; root:xnu-10002.81.5~7/RELEASE_ARM64_T6000
  Available memory (MB): 16384
  Available CPU cores: 10
Binaries:
  Node: 20.11.0
  npm: 10.2.4
  Yarn: 4.1.0
  pnpm: 8.15.4
Relevant Packages:
  next: 14.2.0-canary.19 // Latest available version is detected (14.2.0-canary.19).
  eslint-config-next: 14.1.3
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.4.2
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Not sure

### Which stage(s) are affected? (Select all that apply)

Vercel (Deployed)

### Additional context

I tested my reproduction against different canary releases, and the first one that introduced the bug was `14.2.0-canary.14`, since reverting to `14.2.0-canary.13` works.
Repository: flutter
Issue: [Impeller] Document all the flatbuffer identifiers used by Impeller.
Labels: engine,P2,e: impeller,team-engine,triaged-engine

We use IPLR for runtime stages in Flutter. But now there are shader bundles for Flutter GPU and probably some others. We should document the ones is use.
Repository: flutter
Issue: [Flutter GPU] Add support for cubemaps.
Labels: engine,c: proposal,P2,team-engine,triaged-engine,flutter-gpu
Repository: ollama
Issue: Please support Zephyr 7B Gemma
Labels: model request

Please support [Zephyr 7B Gemma](https://huggingface.co/HuggingFaceH4/zephyr-7b-gemma-v0.1)! This [HG Chat](https://huggingface.co/spaces/HuggingFaceH4/zephyr-7b-gemma-chat) is a lot better than Zephyr beta (fine-tuned on Mistral 7B).
Repository: deno
Issue: Deno closes Socket's readable stream sooner than Node
Labels: bug,node compat,node API

When using the node compatible modules, Deno behaves differently from Node in regards to `Socket` instance created with the `net` module.

For example:

```js
// index.mjs
import net from 'node:net';
import { Readable } from 'node:stream';

net.createServer((socket) => {
  socket.on("data", (data) => {
    console.log('Server received:', data.toString());

    socket.write('oh, hi!');
  });
  socket.on("end", () => console.log('Server ended'));
}).listen(42069);

const socket = net.createConnection({ port: 42069, host: "localhost" }, () => {
  let i = 0;
  const readable = new Readable({
    read(_size) {
      console.log('Readable read:', i);
      if (i++ < 2) {
        this.push('is this thing on? ' + i + '\n');
      } else {
        this.push(null);
      }
    },
  });

  socket.on('data', (data) => console.log('Client received:', data.toString()));
  socket.on('end', () => console.log('Client ended'));

  readable.pipe(socket);
});
```

When running with Node (v18.17.0) using `node index.mjs` I get the following output:
```
Readable read: 0
Readable read: 1
Readable read: 2
Server received: is this thing on? 1
is this thing on? 2

Server ended
Client received: oh, hi!
Client ended
```

When running with Deno (v1.41.2) using `deno run -A index.mjs` I get the following output:
```
Readable read: 0
Readable read: 1
Readable read: 2
Client ended
Server received: is this thing on? 1
is this thing on? 2

Server ended
```

After a bit of debugging with `--inspect`, I was able to find the following info:
1. The `pipe` function triggers the `end` of the Socket
2. Since the Socket is a Duplex, it will close both the readable and writable parts 
  a) On Node, the Socket seems to ignore the `end()` call and keeps alive long enough to receive data back
  b) On Deno, the Socket seems to close the readable part before getting a "response"

I've tried to find the exact difference between the properties of Socket on Deno and Node with the debugger, but it is difficult for my untrained eyes to keep track of meaningful context when the execution goes back to the event loop handling and asynchronous processors.

What I could see was that in the Socket's `_final` method, it seems the `_handle.shutdown` call is different. By trying a `_handle.shutdown.toString()` I get the following results:

On Deno:
```
shutdown(req) {
    const status = this._onClose();
    try {
      req.oncomplete(status);
    } catch  {
    // swallow callback error.
    }
    return 0;
  }
```

On Node:
```
function shutdown() { [native code] }
```

The difference in execution could be there, but that's as far as I could on for now.
Repository: flutter
Issue: [flutter_tools] PathAccessException deleting files under build\app\intermediates because file "is being used by another process"
Labels: P2,team-tool,triaged-tool

On `beta/3.20.0-1.2.pre`
Command `flutter assemble ...`

```
PathAccessException: Cannot delete file, path = 'C:\src\my_flutter_app\build\app\intermediates\flutter\debug\flutter_assets\kernel_blob.bin' (OS Error: The process cannot access the file because it is being used by another process.
, errno = 32)
at _File.throwIfError(file_impl.dart:675)
at _File._deleteSync(file_impl.dart:329)
at FileSystemEntity.deleteSync(file_system_entity.dart:407)
at ForwardingFileSystemEntity.deleteSync(forwarding_file_system_entity.dart:70)
at ForwardingFileSystemEntity.deleteSync(forwarding_file_system_entity.dart:70)
at ErrorHandlingFileSystem.deleteIfExists(error_handling_io.dart:80)
at FlutterBuildSystem.trackSharedBuildDirectory(build_system.dart:778)
at FlutterBuildSystem.build(build_system.dart:666)
at <asynchronous gap>(async)
at AssembleCommand.runCommand(assemble.dart:322)
at <asynchronous gap>(async)
at FlutterCommand.run.<anonymous closure>(flutter_command.dart:1383)
at <asynchronous gap>(async)
at AppContext.run.<anonymous closure>(context.dart:153)
at <asynchronous gap>(async)
at CommandRunner.runCommand(command_runner.dart:212)
at <asynchronous gap>(async)
at FlutterCommandRunner.runCommand.<anonymous closure>(flutter_command_runner.dart:360)
at <asynchronous gap>(async)
at AppContext.run.<anonymous closure>(context.dart:153)
at <asynchronous gap>(async)
at FlutterCommandRunner.runCommand(flutter_command_runner.dart:300)
at <asynchronous gap>(async)
at run.<anonymous closure>.<anonymous closure>(runner.dart:119)
at <asynchronous gap>(async)
at AppContext.run.<anonymous closure>(context.dart:153)
at <asynchronous gap>(async)
at main(executable.dart:92)
at <asynchronous gap>(async)
```
Repository: flutter
Issue: Allow for disabling auto-update check from an environment variable
Labels: c: new feature,tool,c: proposal,P3,team-tool,triaged-tool

### Use case

I don't want to be notified by Flutter tool when new version of Flutter becomes available. Not only I always stay up to date on latest Flutter releases, but I often have to switch between versions using [`fvm`](https://github.com/leoafarias/fvm), and I get notified about "new version" way too often.

I can do `alias flutter="flutter --no-version-check"`, but I don't like it. I prefer to use environment variables for defining such options. Furthermore it's a usual approach followed by many CLI tools: you can configure the same setting in 3 places (config file -> env variable -> command-line flag).

I see that Flutter tool uses the [`cli_config`](https://pub.dev/packages/cli_config) package, which provides some facilities to implement the behavior I want

### Proposal

Teach `flutter_tools` to handle `FLUTTER_VERSION_CHECK` env variable. If this variable will be set to `false`, behave as if `--no-version-check` was passed.

---

I am willing to implement this once I get a buy-in from some other team members :)
Repository: pytorch
Issue: [DCP] Define how we should treat List/Dict
Labels: triaged,module: distributed_checkpoint

### 🚀 The feature, motivation and pitch

Should we just convert stuff to bytes inside DCP if we encounter something that’s not tensors?

### Alternatives

_No response_

### Additional context

_No response_

cc @LucasLLC
Repository: go
Issue: proposal: encoding/binary: Add `SizeUvarint()` and `SizeVarint()`
Labels: Proposal

### Proposal Details

It would be nice to have a function like `SizeUvarint()` and `SizeVarint()` that calculates the size of a `UVarint` or `Varint` representation without actually appending the bytes to a buffer. Exactly like [AppendUvarint](https://cs.opensource.google/go/go/+/refs/tags/go1.22.1:src/encoding/binary/varint.go;l=90-98) but it simply counts the bytes that would have been appended.


The current roundabout way of doing this is something like:
```go
lengthBytes := len(binary.AppendUvarint([]byte{}, uint64(k.DataPointer.Length)))
```
Repository: bitcoin
Issue: Intermittent failure in rpc_bind.py: in get_socket_inodes                                         FileNotFoundError: [Errno 2] No such file or directory: '/proc/34007/fd/23'
Labels: Tests,CI failed

### Is there an existing issue for this?

- [X] I have searched the existing issues

### Current behaviour

I opened a PR and the functional test failed 
https://github.com/bitcoin/bitcoin/pull/29500/checks?check_run_id=22324979545

random seed: 2149187499175826776

https://github.com/bitcoin/bitcoin/pull/29500#issuecomment-1987892121

### Expected behaviour

I expected the test runner to pass

### Steps to reproduce

Not sure how to reproduce other than running the test runner multiple times till it occurs

### Relevant log output

https://github.com/bitcoin/bitcoin/pull/29500/checks?check_run_id=22324979545

### How did you obtain Bitcoin Core

Compiled from source

### What version of Bitcoin Core are you using?

master@f9ba6fd46d454d0a56662db751675a6520e1c9f6

### Operating system and version

Cirrus CI / ASan + LSan + UBSan + integer, no depends, USDT

### Machine specifications

This happened in the ci/cd
Repository: flutter
Issue: [Impeller] impeller_dart_unittests crash when Vulkan validations are enabled.
Labels: P3,e: impeller,team-engine,triaged-engine

Seen in https://github.com/flutter/engine/pull/51341/

For now I've restricted this test set to Metal. Its unclear to me if these were running before.
Repository: pytorch
Issue: Suggest check_is_size if size oblivious test fails but symint is not size-like
Labels: triaged,small,module: dynamic shapes

### 🐛 Describe the bug

self explanatory

### Versions

main
Repository: vscode
Issue: Multi Diff doesn't seem to have Inline View toggle
Labels: feature-request,multi-diff-editor

<!-- ⚠️⚠️ 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. -->

Please add ability to toggle Inline View for the excellent new Multi Diff. Currently it doesn't seem to have the `...` menu with the `Inline View` toggle like regular single file diff has. Thx!
Repository: vscode
Issue: If a URI contains an authority component, then the path component must either be empty or begin with a slash ("/") character
Labels: bug,terminal-process

1. Create a new terminal in a workspace with two repos 
2. :bug: sometimes get this error

![Image](https://github.com/microsoft/vscode/assets/30305945/9a4ab600-4e56-4b88-a749-71fba8b7508b)
```
notificationsAlerts.ts:40 Error: [UriError]: If a URI contains an authority component, then the path component must either be empty or begin with a slash ("/") character
    at $ (uri.ts:36:11)
    at new c (uri.ts:175:4)
    at u (uri.ts:447:1)
    at c.from (uri.ts:338:18)
    at ae.Qb (terminalService.ts:1064:32)
    at ae.createTerminal (terminalService.ts:1001:16)
    at async T.run (terminalView.ts:254:28)
    at async E.u (actions.ts:194:3)
    at async E.run (actions.ts:185:4)
```
Repository: flutter
Issue: Marking digests as "negative" in Skia Gold has no impact on pre-submit, causing post-submit breakages
Labels: dependency: skia,P2,c: tech-debt,team-framework,triaged-framework

When a test reports a digest (read: an image with some metadata) to Skia Gold, there is a tri-modal state of how it is considered:

State | What it means
----- | ---------------
✅  Positive | An _existing_ digest was found that matches[^1] the image that was marked _positive_ previously[^2].
❔Untriaged |  No _existing_ digest was found that matches the image.
🚫 Negative | An _existing_ digest was found that matches the image that was marked _negative_ previously[^3].

The way our (read: `flutter/flutter` and `flutter/engine`) trees work, is that when a test uses Skia Gold, and uploads a digest, the test passes _regardless_ of what match state occurred[^4], and later[^5], asynchronously,  our `Flutter Gold` custom check runs and verifies that _no untriaged digests exist at the current commit_.

That is, the following workflow causes a post-submit build breakage:

1. User `Octocat` pushes a PR that, as a result, produces an update to `draw_square_test`.
2. The test suite/builder, a hypothetical `linux: framework_draw_shapes`, runs, and reports all tests _passing_.
3. The `Flutter Gold` check holds a _pending_ state, and will report back pending untriage digests, similar to below:

![Example](https://github.com/flutter/flutter/assets/168174/ab46d036-c0ef-4f67-8932-2e88fbf2947d)

4. The square test now draws a circle. Oops! It is marked "negative".
5. Now, all tests are passing (as they were in step 2), and Flutter Gold is _also_ marked as passing.
6. Either manually, or via `auto-submit`, the PR lands.
7. ... eventually, it's run on post-submit, which cause a tree breakage, because a test matches a negative digest.

[^1]: What that means is out of scope of this issue, but it's not necessarily a 1:1 pixel match, nor a _specific_ match.
[^2]: I believe the heuristic also includes "and was seen in the last 100 landed commits".
[^3]: I'm not sure about the retention of negative digests, I'd assume they are 'forever' 🤞🏼.
[^4]: The context of this decision is in https://github.com/flutter/flutter/issues/48744.
[^5]: I believe it is a cron-job that runs every 5 minutes and checks if all other status checks are passing.

---

Possible improvements (to discuss):

- Update our [documentation on Skia Gold](https://github.com/flutter/flutter/wiki/Writing-a-golden-file-test-for-package:flutter#flutter-gold-check)
- Update the GitHub bot to print a scary message that "negative doesn't work like you think it does"
- Update the Flutter Gold check to consider matching negative digests as a failure (note that from talking to @kjlubick, this currently is not something available in the Skia Gold API - we'd either need to request the API, help implement it, or find another way to get this functionality)
- Update the Skia Gold Client logic to fail pre-submit on matching negatives (we could keep the current untriaged behavior)

/cc @Piinks @jonahwilliams @gaaclarke @goderbauer
Repository: vscode
Issue: pushStackElement API in Notebook Editor Model needs to line up with Text Editor 
Labels: debt,notebook-undo-redo

Ensure we have real support for `pushStackElement`
allowing us to merge multiple edit operations into a single undo/redo.



Related issue https://github.com/microsoft/vscode/issues/117945
Repository: stable-diffusion-webui
Issue: [Feature Request]: Improved Extra Tab Features
Labels: enhancement

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

Automatic Scaling of Input Images
When working with a folder full of images where one side is greater than about 2000 pixels, processing may fail due to Video Card VRAM or some other limitations. The only current solution is to resize all of the images with an external graphics program. If the all of the images are the same size, this works well, if they are not, then manual scaling is often, though not always) the only solution. 


In Automatic 1111, when working with img2img etc. there are two setting for the Scaling feature. One for setting x and y separately, and another for multiplying both x and y at once allowing both + and - values. In the Extras Tab, you are limited to + values (this is very bad!).  _In fact, in my experience, these settings do nothing at all. There is no scaling, thus the output image has the same size as the input image, regardless of any setting. Is there anyone who has experienced otherwise ?_

Once again this requires extra manual work unless all of the images in a folder are the same size, and when using the Extras Tab (for Reactor for example), image sizes above your max value makes it unusable. Once again forcing you to use an external graphics program to downscale before you can run img2img etc.

I don't see why A1111 has not already built in an option to scale the input images automatically, so that the maximum size is limited to a user set value such as 1280, or 1600, or 2000 pixels (or specific values that work best for SDXL)).

Describe the idea you'd like

A1111 feature should in img2img, and especially in Extras Tab automatically set maximum pixel size for the longest side of an image. After all, this program is called "Automatic" right ?

In addition, would it be possible to also have a batch mode allowing the user to browse for both an input and and output folder. This would be far easier than having to change the semi-permanent setting whenever necessary, although the default of saving in the Source folder works great almost all the time.

Thanks !

ADDED LATER - In fact I stumbled on how to use the Scaling in the Extras TAB. Because the Upscaler type (4x-Ultrasharp etc.) is below the setting and appears to be part of a different section it was not, at least to me, obvious that it had to be filled out. Once again it does not work the way things are laid out in the img2img Tab. There you simply move the pointer to get scaling without apparently having to choose who does the scaling. So, now I can scale up, but still cannot scale down.

### Proposed workflow

1. Go to .... 
2. Press ....
3. ...
The automatic scaling could simply be a user setting, just in case someone does not want automatic scaling.

### Additional information

_No response_