sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: [tool] Tool can accept/reject compilation results from a compilation after already sending out a second compilation request
Labels: P2,team-tool,triaged-tool

Discovered while working on https://github.com/flutter/flutter/pull/152358. In this PR, I tried to change `DefaultResidentCompiler` to call `flush` on the stdin sink of the compiler frontend process after every `writeln` call.

However, this caused tests within [hot_reload_web_test.dart](https://github.com/flutter/flutter/blob/3c30e3cb208081fc9a7598a87608027250c7ad61/packages/flutter_tools/test/web.shard/hot_reload_web_test.dart) to flake (or even fail fairly consistently depending on the host machine).

After instrumenting `DefaultResidentCompiler` with tracking and logging code, I was able to determine that the flakes occur due to a `DefaultResidentCompiler::accept` call being concurrent with a `DefaultResidentCompiler::compileExpressionToJs` call. (Unfortunately, I've lost this logging code, but you can at least see the failure in [this old PR check](https://github.com/flutter/flutter/pull/152187/checks?check_run_id=27856744079)).

While this issue was discovered in the hot reload for web tests, I don't believe this issue is specific to them.

https://github.com/flutter/flutter/pull/18618 modified `DefaultResidentCompiler` to force compilations to happen serially. However, nothing enforces that an `accept` or `reject` is sent to the compiler before the next compilation is sent off. I am not sure if this currently causing any bugs, but it seems like a pitfall that easily could.

I plan to workaround this issue in https://github.com/flutter/flutter/pull/152358 since troubleshooting and fixing it would block troubleshooting the top crasher of the flutter tool.
Repository: go
Issue: x/tools/gopls/internal/test/integration/misc: TestTelemetryPrompt_Response failures
Labels: NeedsInvestigation,gopls,Tools,telemetry

```
#!watchflakes
default <- pkg == "golang.org/x/tools/gopls/internal/test/integration/misc" && test ~ `TestTelemetryPrompt_Response`
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8741307618506564305)):

    === RUN   TestTelemetryPrompt_Response/empty
        prompt_test.go:295: ReadCounter("gopls/telemetryprompt/accepted") failed: not found:"gopls/telemetryprompt/accepted"
    --- FAIL: TestTelemetryPrompt_Response/empty (0.00s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: crypto/tls: TestVerifyConnection/TLSv13 failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "crypto/tls" && test == "TestVerifyConnection/TLSv13"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8741054812401626609)):

    === RUN   TestVerifyConnection/TLSv13
        handshake_test.go:495: failed to call cli.Close: close tcp 127.0.0.1:24221->127.0.0.1:48674: connection reset by peer
    --- FAIL: TestVerifyConnection/TLSv13 (0.16s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: cmd/go: TestScript/mod_dir failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "cmd/go" && test == "TestScript/mod_dir"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8741043191885008481)):

    === RUN   TestScript/mod_dir
    === PAUSE TestScript/mod_dir
    === CONT  TestScript/mod_dir
        script_test.go:135: 2024-07-29T21:43:11Z
        script_test.go:137: $WORK=C:\b\s\w\ir\x\t\cmd-go-test-810710165\tmpdir3080745464\mod_dir556404051
    2024/07/29 14:43:11 serving /git/insecurerepo/info/refs?service=git-upload-pack
        script_test.go:159: 
            PATH=C:\b\s\w\ir\x\t\cmd-go-test-810710165\tmpdir3080745464\testbin;C:\b\s\w\ir\x\w\goroot\bin;C:\b\s\w\ir\x\w\goroot\bin;C:\b\s\w\ir\x\w\goroot\bin;C:\b\s\w\ir\cache\tools\bin;C:\b\s\w\ir\bbagent_utility_packages;C:\b\s\w\ir\bbagent_utility_packages\bin;C:\b\s\w\ir\cipd_bin_packages;C:\b\s\w\ir\cipd_bin_packages\bin;C:\b\s\w\ir\cipd_bin_packages\cpython3;C:\b\s\w\ir\cipd_bin_packages\cpython3\bin;C:\b\s\w\ir\cache\cipd_client;C:\b\s\w\ir\cache\cipd_client\bin;C:\b\s\cipd_cache\bin;C:\Program Files\OpenSSH\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program Files\Puppet Labs\Puppet\bin;C:\b\s\w\ir\cache\tools\cc\windows\gcc64\bin
            USERPROFILE=/no-home
            CCACHE_DISABLE=1
    ...
            > stdout 'x/sub'
            matched: x/sub
            > mkdir go.mod
            > exists go.mod
            > go list .
            [stderr]
            go: read C:\b\s\w\ir\x\t\cmd-go-test-810710165\tmpdir3080745464\mod_dir556404051\go.mod: The process cannot access the file because another process has locked a portion of the file.
        script_test.go:159: FAIL: testdata\script\mod_dir.txt:13: go list .: exit status 1
    2024/07/29 14:43:11 serving /git/insecurerepo/git-upload-pack
    --- FAIL: TestScript/mod_dir (0.21s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: cmd/go: TestScript/mod_get_direct failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "cmd/go" && test == "TestScript/mod_get_direct"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8740983986395767377)):

    === RUN   TestScript/mod_get_direct
    === PAUSE TestScript/mod_get_direct
    === CONT  TestScript/mod_get_direct
        script_test.go:135: 2024-07-30T13:29:20Z
        script_test.go:137: $WORK=/home/swarming/.swarming/w/ir/x/t/cmd-go-test-1123180603/tmpdir3991357469/mod_get_direct1207619188
    go proxy: no archive example.net v1.0.0: file does not exist
    go proxy: no archive rsc.io v1.5.1: file does not exist
        script_test.go:159: 
            PATH=/home/swarming/.swarming/w/ir/x/t/cmd-go-test-1123180603/tmpdir3991357469/testbin:/home/swarming/.swarming/w/ir/x/w/goroot/bin:/home/swarming/.swarming/w/ir/x/w/goroot/bin:/home/swarming/.swarming/w/ir/x/w/goroot/bin:/home/swarming/.swarming/w/ir/cache/tools/bin:/home/swarming/.swarming/w/ir/bbagent_utility_packages:/home/swarming/.swarming/w/ir/bbagent_utility_packages/bin:/home/swarming/.swarming/w/ir/cipd_bin_packages:/home/swarming/.swarming/w/ir/cipd_bin_packages/bin:/home/swarming/.swarming/w/ir/cipd_bin_packages/cpython3:/home/swarming/.swarming/w/ir/cipd_bin_packages/cpython3/bin:/home/swarming/.swarming/w/ir/cache/cipd_client:/home/swarming/.swarming/w/ir/cache/cipd_client/bin:/home/swarming/.swarming/cipd_cache/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
            HOME=/no-home
    ...
            > [!git] skip
            [condition not met]
            > env GO111MODULE=on
            > env GOPROXY=direct
            > env GOSUMDB=off
            > go list -m cloud.google.com/go@main
            [stderr]
            go: cloud.google.com/go@main: unrecognized import path "cloud.google.com/go": reading https://cloud.google.com/go?go-get=1: 500 Internal Server Error
        script_test.go:159: FAIL: testdata/script/mod_get_direct.txt:12: go list -m cloud.google.com/go@main: exit status 1
    --- FAIL: TestScript/mod_get_direct (6.80s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: pytorch
Issue: xpu: efficientnet inference underperforms ipex
Labels: triaged,module: xpu

Running efficientnet inference in eager mode using sample at https://github.com/intel/ai-reference-models/tree/a6a9365c0e94a78ea38bbeacc14f5b43bd5fd577/models_v2/pytorch/efficientnet/inference/gpu on Intel(R) Data Center GPU Max 1100 I observe underperformance of XPU pytorch backend vs. IPEX, ~60%:

* xpu pytorch BS1, fp32 (throughput): 198 fps
* ipex BS1, fp32 (throughput, fps): 320 fps

Similar difference is with other precisions and batch sizes.

Example can be executed as follows:
```
git clone https://github.com/intel/ai-reference-models.git
cd ai-reference-models
export PYTHONPATH=$(pwd)/models_v2/common/:$PYTHONPATH

# run with XPU pytorch backend (note: --ipex no):
cd ai-reference-models/models_v2/pytorch/efficientnet/inference/gpu
PLATFORM=Max ./run_model.sh --ipex no --dummy --min-test-duration 30 --max-test-duration 30 --precision fp32

# run with IPEX:
docker build -f docker/flex-gpu/pytorch-efficientnet-inference/pytorch-flex-series-efficientnet-inference.Dockerfile -t enet
docker run -it --rm --ipc=host --cap-add SYS_NICE --device /dev/dri/ -e OUTPUT_DIR=/opt/outputs -e PLATFORM=Flex enet \
    ./run_model.sh --dummy --min-test-duration 30 --max-test-duration 30 --precision fp32
```

Versions used:
* pytorch: 239d4d248908b3410ff40b5ceab02995a7d75f51
* https://github.com/intel/torch-xpu-ops/commit/f0d43e2edf18b68e5bbc61f3d958cb067d6cf7b5
* https://github.com/intel/ai-reference-models/commit/a6a9365c0e94a78ea38bbeacc14f5b43bd5fd577

CC: @gujinghui @EikanWang @fengyuan14 @guangyey @jgong5 @vlad-penkin

cc @gujinghui @EikanWang @fengyuan14 @guangyey
Repository: excalidraw
Issue: Option to add title to svg to make key words searchable in GitHub
Labels: good first issue,export

_Originally posted by @SoumayaMauthoorMOJ in https://github.com/excalidraw/excalidraw/discussions/8213_
Repository: vscode
Issue: Codelens references for properties of object in root module scope
Labels: help wanted,feature-request,typescript

<!-- ⚠️⚠️ 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. -->
References with codelens are a great feature 👍 
A while back there was an issue (.https://github.com/microsoft/vscode/issues/86495 ) that the references where displayed for every object property which is not always convenient.
On the other hand, objects in top scope, possibly exported, or objects with `as const` modifier could benefit from this feature, imho.

Example:
```typescript
const rootScopeObj = {
  foo: 1
}
export const exportedObj = {
  foo: 1
}
export const exportedConstObj = {
  foo: 1
} as const

const makeConstantObj = (val: string) => {
  return {foo: val} as const // questionable if really useful
}
```

Do these cases make sense - to show references for `foo` property? Similar to how `enum` works.
![image](https://github.com/microsoft/vscode/assets/3704482/f1c08b4e-b888-42c2-8d2c-674eb91d180e)

If not desirable for everyone, it could possibly be hidden behind some option(s), right?
I honestly believe it can be useful for many people.
Repository: go
Issue: proposal: os: stop manually setting sticky bit on file creation on *BSD, Solaris 
Labels: Proposal

### Proposal Details

On *BSD and Solaris systems, `open(2)` and `mkdir(2)` will not create a file with the [sticky bit](https://en.wikipedia.org/wiki/Sticky_bit) set. The FreeBSD [sticky(8)](https://man.freebsd.org/cgi/man.cgi?query=sticky&sektion=8&apropos=0&manpath=FreeBSD+7.1-RELEASE) manpage lists this as a bug. I don't know the historical reasons for this behavior.

#8383 reported this as a bug in `os.OpenFile` and `os.Mkdir`, and subsequently [CL 1673](https://go.dev/cl/1673) changed `OpenFile` to set the sticky bit after creation when the file mode includes `ModeSticky`. (A later CL added the same behavior for `Mkdir`.)

This operation is racy: When creating a file with `ModeSticky`, we:
1. Check to see if the file exists.
2. Open the file (possibly creating it).
3. If the file did not exist, stat it to find its current mode.
4. If the file did not exist, chmod the file to add the sticky bit.

If the target file is created between steps 1 and 2, then we may chmod a file we did not create. I think this is of minimal concern.

If the target file, or some part of its path, is replaced with a symlink between steps 2 and 4, however, we will chmod the target of the link, which could be anything. This is difficult to exploit: It requires that a privileged process be creating a file with the sticky bit set in a location that is writable by an attacker. If an exploitable scenario exists, however, it should be fairly straightforward to convert to local privilege escalation.

We can avoid the race in `OpenFile` by using `File.Chmod` to chmod the actual file opened.

Avoiding the race in `Mkdir` is harder, because `mkdir(2)` doesn't return a handle to the new directory. We could work around it with a multi-phase dance of opening the parent directory, using `mkdirat(2)` to create the new directory, and then using `openat(2)` to open the newly-created directory. This still leaves a race condition--we might be opening a directory different than the one we just created--but at least we'll be certain that we're chmodding a directory in the exact same location as the one we created.

I propose that working around the OS behavior in this case is a mistake, and that rather than putting in complicated workarounds we should remove the behavior introduced by [CL 1673](https://go.dev/cl/1673), with a GODEBUG to reenable the original behavior, race conditions and all.
Repository: deno
Issue: Test reports behave strange when error stack was manipulated
Labels: bug,testing

Manipulating error stack can be useful if in some cases stack is meaning less because something happened in handler and you want to indicate which function is the root cause of the problem. 

Minimal code to reproduce:
```ts
Deno.test("Hello World", () => {
	const e0 = new Error("Hello World");
	const stack = e0.stack;
	const err = new Error("Hello World");
	err.stack = stack;
	throw err;
})
```

Current output:
```
Hello World => ./main.test.ts:1:6
error: Error: World
    at <anonymous> (ext:core/01_core.js:735:34)
```

Expected output:
```
Hello World => ./main.test.ts:1:6
error: Error: World
	const e0 = new Error("Hello");
	           ^
    at file:///Users/raay/Workspace/CodeCat/DenoFail/main.test.ts:2:13
```

version:
```
deno 1.45.4 (release, aarch64-apple-darwin)
v8 12.7.224.13
typescript 5.5.2
```
Repository: pytorch
Issue: Broken link in doc. 
Labels: module: docs,triaged,module: special

### 📚 The doc issue

The link here is not working anymore:

https://github.com/pytorch/pytorch/blob/19db4f601441326bcc02d4d51e40a9586798f2bb/torch/csrc/api/include/torch/special.h#L945

 See
/// https://pytorch.org/docs/main/special.html#torch.special.hermite_polynomial_he.

There's no torch.special.hermite_polynomial_he in https://pytorch.org/docs/main/special.html. 

### Suggest a potential alternative/fix

_No response_

cc @svekars @brycebortree @mruberry @kshitij12345
Repository: flutter
Issue: Adding a bold typeface to test fonts
Labels: a: tests,framework,c: proposal,P2,team-framework,triaged-framework

The current test fonts all have the same weight.

It's difficult to verify the correct behavior for https://github.com/flutter/flutter/issues/151709 in framework tests. When a segment is selected, its font weight changes, so the width of the segment should also change as a result. We would need a bold font to verify the behavior.
Repository: deno
Issue: WebGPU: Deno hangs when destroying a device that has created a buffer
Labels: bug,web,upstream,webgpu

I compiled Deno from source using the latest commit (fe884c557a76fd288f7457aa433052f65be70c81 as of writing). 

I found that the following program causes Deno to hang on Linux (Ubuntu 22.04) and not finish execution (or at least not finish execution within 30 mins on my machine):
```js
async function main() {
	const adapter = await navigator.gpu.requestAdapter();
	const device = await adapter.requestDevice();
	const buffer = device.createBuffer({
		mappedAtCreation: true,
		size: 12,
		usage: GPUBufferUsage.COPY_SRC
	});
	device.destroy();
}
main().catch(console.error);
```

On macOS, there is some different behavior. The following is output to the console:
```console
No active command buffers for fence value 1
Failed to wait for buffer Id(0,1,mtl): Parent device is lost
```

It seems to be because `mappedAtCreation` is `true`. When `mappedAtCreation` is `false`, the program finishes executing on both macOS and Linux successfully.
Repository: godot
Issue: @icon annotation for custom resources not working with custom extensions
Labels: bug,topic:core,topic:gdscript,topic:editor,needs testing,topic:gdextension

### Tested versions

- 4.3 rc1 (Windows 11)

### System information

Godot v4.3.rc1 - Windows 10.0.22621 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3080 Ti (NVIDIA; 32.0.15.6070) - AMD Ryzen 9 5950X 16-Core Processor (32 Threads)

### Issue description

When using @ icon annotation to set an icon for a custom resource, it does not show in the editor's filesystem if the resource has a custom extension (not .tres)

### Steps to reproduce

1. Open MRP.
2. Open FileSystem.
3. Open the res_1.new file.
4. Notice the icon loads correctly in the inspector, but not the FileSystem.

I attached a screenshot too.
![image](https://github.com/user-attachments/assets/6f5fa18d-ecfd-407f-b59e-9a12542aa222)



### Minimal reproduction project (MRP)

[icon-extension-mrp.zip](https://github.com/user-attachments/files/16433782/icon-extension-mrp.zip)
Repository: flutter
Issue: [Impeller] Allow both linear and nearest sampling of AHB backed Vulkan textures.
Labels: P3,e: impeller,team-engine,triaged-engine

Today, AHB backed textures will prefer linear sampling (after checking for `VK_FORMAT_FEATURE_SAMPLED_IMAGE_YCBCR_CONVERSION_LINEAR_FILTER_BIT`) and fallback to nearest sampling. That is, sampling will ignore the min and mag filter specified in the `impeller::SamplerDescriptor`. This is because of stricter requirements when sampling from AHBs.

If `VK_FORMAT_FEATURE_SAMPLED_IMAGE_YCBCR_CONVERSION_LINEAR_FILTER_BIT` is not supported, there is no way linear sample without a render to an intermediate texture.

On the other hand, if `VK_FORMAT_FEATURE_SAMPLED_IMAGE_YCBCR_CONVERSION_LINEAR_FILTER_BIT` is supported, using nearest sampling is not possible today because we create only a single conversion.

It may be tempting to just check for `VK_FORMAT_FEATURE_SAMPLED_IMAGE_YCBCR_CONVERSION_SEPARATE_RECONSTRUCTION_FILTER_BIT` and use whatever is specified in the `impeller::SamplerDescriptor`. While this is extremely convenient, in practice, this bit is never set on most Android formats.

To work around this, a completely separate conversion must be created and cached in the conversions library. And, in the relatively uncommon case where linear sampling is not supported, a separate render to texture must be performed.

This describes an edge case since most uses require linear sampling and that seems to be well supported out of the box. But, if we get reports of users depending on specific kinds of sampling, we should look into using separate conversions and (in extreme cases to catch lack of support for direct linear sampling) render to texture.
Repository: kubernetes
Issue: Consistent behavior on nullable struct used in cel expression with optonal
Labels: kind/bug,sig/api-machinery,triage/accepted

### What happened?

Previous a issue reported in cel-go regarding with nullable struct behavior in optional (Related issue: https://github.com/google/cel-go/issues/937).
The fix is in https://github.com/google/cel-go/pull/938 and https://github.com/google/cel-go/pull/939 with a flag added for the fix. However, opt-in this fix in k8s would result in breaking change on certain cel expressions. 

Thanks to @TristonianJones who suggested the updates on cel type system to minimized the breakage: 
"Treat nullable fields as unset / absent within the `Get` and `Find` operations for unstructuredList and unstructuredMap types. This would be consistent with CEL's field presence semantics and result in the correct behavior for the existing expressions with and without optional syntax."
```
// Returns false today
// Returns true if CEL bug fix is enabled
// Returns false if K8s field traversal updated and bug fix enabled 
object.?complexType.hasValue() 
```
However, this change would still introduce a breaking behavior for comparisons of complex types to null values.
```
// Will return object.otherType today, but object.complexType.field tomorrow 
// when the complexType value is unset
object.complexType == null ? object.otherType : object.complexType.field

// Conditionally true or false today
// Trivially true or trivially false if the default value is returned with
// a change in K8s object traversal
object.complexType != null
object.complexType == null
```

Additionally, this would be considered as breaking change and should fulfill the compatibility policy in k8s.

### What did you expect to happen?

Fix the issue in a non-breaking way.

### How can we reproduce it (as minimally and precisely as possible)?

Using cel optional expression on nullable struct.

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
$ kubectl version
# paste output here
```

</details>


### Cloud provider

<details>

</details>


### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>
Repository: flutter
Issue: Support SwiftUI's spring animation
Labels: c: new feature,framework,a: animation,c: proposal,P2,team-framework,triaged-framework

### Use case

The spring animation is used all over iOS, and is critical to building widgets with iOS look and feel. Although Flutter currently provides spring simulators, they're not directly usable as animation curves.

### Proposal

The spring animation is introduced here: https://developer.apple.com/videos/play/wwdc2023/10158/

([Github backup](https://github.com/user-attachments/assets/0f8623c1-8e56-4d0f-a4e0-d6d4c0f40bbf))

Goals:
* Various ways to construct
  * Presets: Smooth, bouncy, flattened
  * Customize with `bounce` and `duration`
  * Professional customization with `mass`, `stiffness`, and `damping`
* Velocity: Smoothly connect animations
* Settling time: Continue the long-tail animation beyond `duration`


Convert `bounce` and `duration` to detailed parameters (from the video):
<img width="536" alt="image" src="https://github.com/user-attachments/assets/def7947f-1274-4d48-a5e8-27aa9933262d">

Questions:
* How `extraBounce` is applied
* How `settlingDuration` is derived (we might not need it since our spring simulator allows a settling tolerance)
Repository: flutter
Issue: Scroll "back" on web causes browser back action (unless perfectly horizontal)
Labels: framework,f: material design,f: scrolling,f: gestures,platform-web,has reproducible steps,P2,team-web,triaged-web,found in release: 3.24

https://main-api.flutter.dev/flutter/material/CarouselView-class.html

If you navigate to this page from somewhere else and try to scroll the carousel view BACK you have to slide perfectly horizontally. Any deviation and you start the mac "back" action in the browser.

Look at https://dartpad.dev/?run=true&sample_id=material.CarouselView.2&channel=main


Flutter 3.24.0-1.0.pre.214


https://github.com/user-attachments/assets/13cc05ce-5bbb-4302-9c5b-7fa196090491

I thought it was related to https://github.com/flutter/flutter/issues/143276#issuecomment-2251606907 – but I'm being told...not