sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: After Node3D::set_quaternion(q), get_quaternion returns different quaternion than q
Labels: topic:core,needs testing

### Godot version

4.2.beta, 4.1.2.stable

### System information

Windows 11

### Issue description

When incrementally updating a Node3D's quaternion property, either by *= or direct assignment, an erroneous operation in set_quaternion or get_quaternion will cause the value to flip to the complementary rotation after around 3/4ths of Pi.

This is incorrect and makes interpolation between quaternions over time error-prone (e.g. when using an interpolator that also tracks or limits angular velocity)


### Steps to reproduce

1. Load repro product (in Godot 4.2 or 4.1)
2. Press Play
3. Examine Log Output (there is no visual output, only text)
4. Observe: after 75% of the rotation, the quaternion's components suddenly change their sign, representing the complementary rotation
5. Examine code in `reproduction.gd`: we're actually assigning the correct quaternion, but the rotation is corrupted by the conversion by the basis operation in set_quaternion or perhaps get_quaternion.


You'll see something like:
```
Rotation (% of 2pi)
5% (0, 0.156434, 0, 0.987688) == (0, 0.156434, 0, 0.987688)
10% (0, 0.309017, 0, 0.951056) == (0, 0.309017, 0, 0.951057)
15% (0, 0.453991, 0, 0.891007) == (0, 0.453991, 0, 0.891007)
20% (0, 0.587785, 0, 0.809017) == (0, 0.587785, 0, 0.809017)
25% (0, 0.707107, 0, 0.707107) == (0, 0.707107, 0, 0.707107)
30% (0, 0.809017, 0, 0.587785) == (0, 0.809017, 0, 0.587785)
35% (0, 0.891007, 0, 0.45399) == (0, 0.891007, 0, 0.453991)
40% (0, 0.951057, 0, 0.309017) == (0, 0.951057, 0, 0.309017)
45% (0, 0.987688, 0, 0.156434) == (0, 0.987689, 0, 0.156434)
50% (0, 1, 0, -0) == (0, 1, 0, -0)
55% (0, 0.987688, 0, -0.156435) == (0, 0.987689, 0, -0.156435)
60% (0, 0.951056, 0, -0.309017) == (0, 0.951057, 0, -0.309017)
65% (0, 0.891006, 0, -0.453991) == (0, 0.891007, 0, -0.453991)
70% (0, -0.809017, 0, 0.587785) != (0, 0.809017, 0, -0.587786) <<<<< ERROR
75% (0, -0.707107, 0, 0.707107) != (0, 0.707107, 0, -0.707107) <<<<< ERROR
80% (0, -0.587785, 0, 0.809017) != (0, 0.587785, 0, -0.809017) <<<<< ERROR
85% (0, -0.45399, 0, 0.891007) != (0, 0.45399, 0, -0.891007) <<<<< ERROR
90% (0, -0.309017, 0, 0.951057) != (0, 0.309017, 0, -0.951057) <<<<< ERROR
95% (0, -0.156434, 0, 0.987688) != (0, 0.156434, 0, -0.987689) <<<<< ERROR
100% (0, 0, 0, 1) != (0, -0, 0, -1) <<<<< ERROR
```

### Minimal reproduction project

[quaternion-wrap-bug.zip](https://github.com/godotengine/godot/files/13072142/quaternion-wrap-bug.zip)
Repository: godot
Issue: Color Picker Node set in a drop down of VBoxContainer in Create New Node menu
Labels: discussion,topic:editor,usability

### Godot version

3.5 Stable up to 4.2 Beta 1.0

### System information

Godot v4.2.beta1 - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3060 Laptop GPU (NVIDIA; 31.0.15.2849) - AMD Ryzen 9 5900HS with Radeon Graphics (16 Threads)

### Issue description

Color Picker Node set in a drop down of VBoxContainer in Create New Node menu

![huh](https://github.com/godotengine/godot/assets/10922622/3a2407c0-3664-4bc8-9734-fca41742823d)


### Steps to reproduce

Open godot > CTRL + A > Scroll down to VBoxContainer > Open Drop down

### Minimal reproduction project

Any godot project will work.
Repository: flutter
Issue: More options for drawing stroked text and paths
Labels: c: proposal,P3,team-framework,triaged-framework

Design programs support a number of options for configuring stroke on text and paths. For example, Adobe Illustrator defaults stroked text to "outside".

![image002](https://github.com/flutter/flutter/assets/6343103/af3434df-1ec8-4667-b693-f0cde5b1d181)

(Generalizing this a bit, "Inside" to "outside" could be represented as floats between -1.0 and 1.0 with 0.0 mapping to "center".)

Skia does not support this concept natively for text or paths. The concept exists in the SVG standard, however Chrome (and `package:flutter_svg` which attempts to emulate Chrome) can have undesirable behavior depending on the specific paths that appear in the font:

<img width="857" alt="image (1)" src="https://github.com/flutter/flutter/assets/6343103/8b84f053-2621-4969-b9d5-c1cba90151cb">

To accomplish this today in Flutter, there are a couple of options. First you can use a `Stack` of two `Text` widgets. The top one gets the text fill color. The one behind gets a stroke and you set the one behind to be twice the size of the stroke you need (so that ½ of it is revealed from the edges of the top-fill-colored text). This is problematic because there are two `Text` widgets when there technically should only be one, for example you'd need to use an `ExcludeSemantics` widget to wrap one of the `Text` widgets, and potentially other pitfalls.

Alternatively, you could get down to the render objects and write the code to do this stacked painting without separate widgets. However, then one would need to reimplement all the rest of the functionality of the `Text` widget, which is a heavy burden.

There are strategies for implementing this natively in Impeller (and possibly also as a feature request for the Skia team). However, for consistency across platforms, implementing this using the render object approach in the framework as part of the existing `Text` widget seems like it would be the most convenient. Later, if needed for performance for example, we could then explore adding features to Impeller and/or Skia to implement this. Tagging this as 'team-framework'.
Repository: next.js
Issue: Error persists if used string interpolation in class names with tailwind, even if commented
Labels: bug

### Link to the code that reproduces this issue

https://codesandbox.io/p/sandbox/next-js-module-not-found-shw3c5

### To Reproduce

1. Go to Test.tsx, Check commented Line 10. It has incorrect string interpolation in class names
2. In the server, the error persists: Module not found: Can't resolve './${src}'
3. Error persists if the line is commented on or even removed.

### Current vs. Expected behavior

Current: Error persists if line 10 is commented on or even removed
Expected: Error must not occur if commented line has error or is removed.

### 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 23.0.0: Fri Sep 15 14:41:34 PDT 2023; root:xnu-10002.1.13~1/RELEASE_ARM64_T8103
Binaries:
  Node: 16.17.0
  npm: 8.15.0
  Yarn: 1.22.19
  pnpm: N/A
Relevant Packages:
  next: 13.5.7-canary.16
  eslint-config-next: 13.5.5
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.2.2
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Not sure

### Additional context

https://tailwindcss.com/docs/content-configuration#dynamic-class-names 

https://github.com/tailwindlabs/tailwindcss/discussions/8503#discussioncomment-4827396
Repository: pytorch
Issue: Revisit security implications of #31875
Labels: triaged,better-engineering,topic: security,security

### 🐛 Describe the bug

https://github.com/pytorch/pytorch/issues/31875 was closed by adding a warning to the documentation of `load`.

This is unhelpful because by the time you come to load the model, it's too late. Your choice is either run the binary blob or... not use the model at all.

I would like to suggest moving to a default serialization format which does not rely on arbitrary code execution. Ideally the format would also be based on some standard so that it could be easily read by other tools.

A `load_insecure()` function could be retained for backwards compatibility with older models, but the important thing is that new models be saved to a safer format by default.

I did notice that the docs for `torch.save()` mention a new "zip-file based serialization format". However, it is not documented whether this new format is also vulnerable to RCE. Furthermore, there doesn't appear to be an option in `pytorch.load()` to reject the older *definitely insecure* format.

### Versions

N/A
Repository: storybook
Issue: [Bug]: Canvas code examples don't work with angular components that require a template
Labels: bug,documentation,angular

### Describe the bug

When writing stories for angular components that need a template: The code example in <Canvas> does not update arg values when they are changed in the controls.

Example:
```
import { 
  Meta, 
  StoryObj, 
  // argsToTemplate 
} from '@storybook/angular';
import Button from './button.component';

const meta: Meta<Button> = {
  title: 'Example/Button',
  component: Button,
  tags: ['autodocs'],
  render: (args: Button) => ({
    props: {
      backgroundColor: null,
      ...args,
    },
    // template: `<storybook-button ${argsToTemplate(args)}></storybook-button>`
  }),
  argTypes: {
    backgroundColor: {
      control: 'color',
    },
  },
};

export default meta;
type Story = StoryObj<Button>;

export const Primary: Story = {
  args: { 
    primary: true,
    label: 'Button',
  },
};
```
In the above example, in the Canvas code preview, the values of the inputs will change based on the values set in the controls.

![as-expected](https://github.com/storybookjs/storybook/assets/33633281/f5649285-e636-4bdb-a128-cd8324ad849c)

However, if you comment in the `argsToTemplate` import and the `template` prop inside the Meta, the values do not update.

![actual-result](https://github.com/storybookjs/storybook/assets/33633281/10c30589-8ceb-4773-bbad-f52b30f4db69)


### To Reproduce

1. [Download this repository](https://github.com/kaydeejay/storybook-argstotemplate-repro)
2. `npm install`
3. `npm run storybook`
4. Comment/uncomment lines 4 and 18 of `src/stories/Button.stories.ts` 

### System

```bash
System:
    OS: Linux 6.5 Pop!_OS 22.04 LTS
    CPU: (16) x64 AMD Ryzen 7 3800XT 8-Core Processor
    Shell: 5.1.16 - /bin/bash
  Binaries:
    Node: 18.17.0 - ~/.nvm/versions/node/v18.17.0/bin/node
    npm: 9.6.7 - ~/.nvm/versions/node/v18.17.0/bin/npm <----- active
  npmPackages:
    @storybook/addon-essentials: 7.5.1 => 7.5.1 
    @storybook/addon-interactions: 7.5.1 => 7.5.1 
    @storybook/addon-links: 7.5.1 => 7.5.1 
    @storybook/angular: 7.5.1 => 7.5.1 
    @storybook/blocks: 7.5.1 => 7.5.1 
    @storybook/testing-library: ^0.0.14-next.2 => 0.0.14-next.2 
    storybook: 7.5.1 => 7.5.1
```


### Additional context

None
Repository: go
Issue: x/telemetry/counter: simplify counter file release logic by always rotate it daily
Labels: NeedsInvestigation,telemetry

The current implementation computes the counter file end time during the file creation time.
The end time is the next upload date (that's determined by the day of week written in the weekends file). [An exception](https://github.com/golang/telemetry/blob/master/internal/counter/file.go#L190) also applies for the new users - instead of the next upload date, the counter packages picks 7+ days later.  This exception was originally designed before the telemetry was changed to the opt-in model, to ensure to give at least a week before uploading telemetry data. However, this requirement is no longer critical in the current telemetry model.

The start time is on the other hand determined mostly by the instrumented process's start time (unless the process is a long running process and the counter file rotation happens to occur during the process lifetime). For example, if a user starts gopls on oct 21, 22 and 23, and the week ends on oct 24 according to the user's weekends file, there are three counter files (created on 2023-10-21, 2023-10-22, and 2023-10-23) and they all have the end date 2023-10-24. In theory the 2023-10-21 file can be still active and certain processes are still holding the reference. 

This end time computation adds extra complexity: the counter package computes the end time deep in the call chain of rotate ->  rotate1 -> filename -> fileValidity -> read weekends. The upload package also cannot safely determine when to upload a file without reading the file's content and its metadata.

If we change the counter file to always rotate daily, we may simplify both counter and uploader.

* Counter package creates and rotates counter file daily. The counter package doesn't need to read the weekends file.
* Each count file ends at the end of the day. (UTC)
* Upload package assumes all the files whose names indicate old(+some slack time).

Additional benefits include:
* Upload some counters sooner (if we want and need to).
* Remove the unnecessary 7day+ delay for new users.

cc @golang/tools-team @pjweinb @findleyr
Repository: go
Issue: x/tools/gopls: make a decision about the CLI
Labels: FeatureRequest,gopls,Tools

gopls has a command-line interface that exposes many useful pieces of server functionality (e.g. show analysis diagnostics, rename an identifier) in a form that can be easily invoked from a shell script or other program. Since we no longer support the older separate CLI tools (e.g. gorename), there is a case to be made that should be a first-class interface. However, it is currently nominally "experimental".

The task of this issue is to:
(a) figure out roughly how many people use the CLI tool in its current form. Telemetry should make this easy.
(b) decide whether to publish a stable, coherent, and well-documented set of command-line operations, and, if so,
(c) build and document it.

Another possibility we should consider is whether to provide a pure LSP client (I am guessing such a thing exists) that knows nothing of gopls. This may be less work overall and may align better with standard client-side ways of doing things, though it's also possible that it's more verbose, or clunky, or just can't easily express all the things we would like it to do.
Repository: godot
Issue: Bitmap Font Scaling pushes editor off-screen
Labels: bug,topic:editor,topic:gui

### Godot version

v4.2.beta2.official [f8818f85e]

### System information

Godot v4.2.beta2 - Ubuntu 23.10 23.10 - Wayland - Vulkan (Forward+) - dedicated AMD Radeon RX 6600 (RADV NAVI23) () - 12th Gen Intel(R) Core(TM) i5-12400F (12 Threads)

### Issue description

After enabling bitmap font scaling. Right side of editor is pushed off-screen. Could be related to how the font also seems different size? Fixed when disabled.


### Steps to reproduce

bitmap font scale is disabled in this test project import settings to begin with

- work
  - create a new scene with a label, or open `control.tscn`
  - uses `SuperWhite.fnt` (default font in project settings)
  - works fine, note size of font, normal, about the size of a default button or label, same size it was in 4.1

![277365331-304125d4-2bb6-4fca-bdd6-c9ad9cab4f39](https://github.com/godotengine/godot/assets/962340/ccf6ebed-dcbc-4bbb-9ce9-0f214282e9d8)

- not work:
  - change font scale in `SuperWhite.fnt` import settings to `fractional` (default)
  - need to reload project to use new settings?
  - note size of font, it is now much bigger, about 3x the size of a default button or label
  - want to check size of font but right half of editor is pushed off screen

![277365219-f56479f8-a1ba-4f00-8500-a04d286a5478](https://github.com/godotengine/godot/assets/962340/1daf59e0-2de2-43c3-9c18-2fe740e64e82)

to fix the editor temporarily can quit delete `.godot/imported` reload and will work till reload again

to fix editor permanently can disable bitmap font scaling and reload

### Minimal reproduction project

https://github.com/rakkarage/test-bitmap-font-scale
Repository: flutter
Issue: Enforce the rendering rule
Labels: c: proposal,P1,a: multi window,team-engine,triaged-engine

The rendering rule is a calling convention documented in `FlutterView.Render`:
```
  /// This function must be called within the scope of the
  /// [PlatformDispatcher.onBeginFrame] or [PlatformDispatcher.onDrawFrame]
  /// callbacks being invoked.
  ///
  /// If this function is called a second time during a single
  /// [PlatformDispatcher.onBeginFrame]/[PlatformDispatcher.onDrawFrame]
  /// callback sequence or called outside the scope of those callbacks, the call
  /// will be ignored.
```

This rule is very important to implementing multi-view without having to introduce new APIs. However, historically these illegal calls were not ignored and could cause unintended effects that many things were actually relying on.

With multiple PRs, we managed to make it closer to removing violations, but we still haven't fully enforced it.

The current status:
* On debug build, illegal calls are caught and skipped by the `PlatformDispatcher`.
* On release build, illegal calls are caught and skipped by the `Animator`.

We should:
* Unify the behavior of the debug build and the release build.
* Make both behavior assert on (and skip) illegal calls.

Obstacle:
* Currently a performance regression is caused by this change (see https://github.com/flutter/engine/pull/46919). However, we suspect that the regression is entirely caused by 2 frames being dropped, and those 2 frames are illegally drawn warm-up frames.
  * **Update:** The cause for the regression has found. https://github.com/flutter/flutter/issues/142851 needs to be resolved before this issue.
* The framework unit test harness is written in a way that calls `render` directly, and we can't change it for now since there are no dependency injection around `FlutterView` and `PlatformDispatcher`.
Repository: flutter
Issue: ☂️ Support multi-view rendering [Desktop]
Labels: framework,engine,P3,team-engine,triaged-engine

Embedders should offer an API for runners to add additional views. These views are exposed to the framework. The framework can render content into all available views from a single widget tree.

The framework part of this is done. Engine work is underway to support rendering into multiple views and we are in the process of defining the embedder and Runner APIs for this.
Repository: pytorch
Issue: [aot_inductor]14k models: RuntimeError: t == DeviceType::CUDA INTERNAL
Labels: low priority,triaged,oncall: pt2,module: aotinductor

Repro:
```
python main.py --compile_mode export -e ./generated/test_Vious_LBAM_Pytorch.py:GaussActivation
```

cc @ezyang @anijain2305 @chauhang @penguinwu @chenyang78 @msaroufim @bdhirsh @zou3519 @wconstab @avikchaudhuri @gmagogsfm @zhxchen17 @tugsbayasgalan @angelayi
Repository: kubernetes
Issue: Set up VEX to eliminate false-positives from vulnerability scanning tool results
Labels: area/security,sig/release,needs-triage

e.g., https://github.com/CycloneDX/bom-examples/tree/master/VEX/Use-Cases/Case-4

For false positives like:
- https://github.com/kubernetes/kubernetes/pull/121338#issuecomment-1771341403
Repository: pytorch
Issue: [aotinductor] 14k models: Function input to foward()
Labels: low priority,triaged,oncall: pt2,module: aotinductor

Repro:
```
python main.py --compile_mode aot_inductor -e  ./generated/test_ruotianluo_self_critical_pytorch.py:SublayerConnection
```

cc @ezyang @anijain2305 @chauhang @penguinwu @chenyang78 @msaroufim @bdhirsh @zou3519 @wconstab
Repository: pytorch
Issue: __slots__ + inheriting from torch.Tensor
Labels: triaged,tensor subclass,module: python frontend

# Sumary
Inheriting from torch.tensor causes the attribute checking from slots to not raise anymore 

``` Python
class Example():
    __slots__ = ['a', 'b']

class Example_2(torch.Tensor):
    __slots__ = ['a', 'b']

def main():
    ex1 = Example()
    ex2 = Example_2()
    except_raised = False
    try:
        ex1.c = 1
    except AttributeError:
        except_raised = True
    assert except_raised
    # No exception raised
    ex2.c = 1
  
main()
```

I imagine it is because torch.Tensor creates a __dict__ and we inherit this. I am curious if it is best practice to do something like this on the subclass, or would this cause other things to not work?

``` Python
    def __setattr__(self, name, value):
        if name not in self.__slots__:
            raise AttributeError(f"'{type(self).__name__}' object has no attribute '{name}'")
        super().__setattr__(name, value)

    def __getattr__(self, name):
        if name not in self.__slots__:
            raise AttributeError(f"'{type(self).__name__}' object has no attribute '{name}'")
        return super().__getattr__(name)
        ```

cc @ezyang @msaroufim @albanD
Repository: PowerToys
Issue: Custom Title Bar Color/Acrylic/Remove/ Theme aware
Labels: Idea-Enhancement,Needs-Triage,Product-CropAndLock

### Description of the new feature / enhancement

The ability to adjust the title bar of the new Crop and lock. It can match just the accent theme or make it any color or acralyc.

### Scenario when this would be used?

Biggest use case of Crop and lock for me is using it to crop media players to it's utilities only. However, having an app like Spotify where the theme is black. the white title bar UI just looks bad. This is just sort of small change and don't know if worth the time but I thought it would make this tool look much cleaner. Having a custom color or acrylic option would be great.
![Screenshot 2023-10-23 130301](https://github.com/microsoft/PowerToys/assets/119690670/5064815e-73fe-48ad-9b7a-86c78877ce1d)


### Supporting information

_No response_
Repository: stable-diffusion-webui
Issue: [Feature Request]: Please add a model selection option to the generation tabs
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 ?

I miss a possibility to select the model type from the tabs like "Checkpoints" and "Lora".
A selection for:
SD 1.5
SD 2.1
SD XL v1.0 
...
would be very helpful.

Reason:
Not all models do have a declaration of the Model type in it's title.

Example:
![image](https://github.com/AUTOMATIC1111/stable-diffusion-webui/assets/15383666/2f8e6955-71c4-4e0b-9191-be33b96f8d2a)
Question: What kind of model is this? (How can I know it?)

An alternative could be, to add a short info in the upper left corner of the preview image, which identifies it's type. (e.g. "SD1.5"). It should then be possible, to enable/disable this label in the UI settings.

### Proposed workflow

1. Go to txt2img - Generation section
2. Select the Checkpoints tab
3. Have a look, whether you can identify the model type of each model there ... specially, if you have more than 20 ...



### Additional information

There is also an "info"-Link and a "Settings" link in the upper right corner of the preview image.
The info does not help, to identify its type, even on "Settings" is nothing listed about.
Repository: go
Issue: cmd/doc: support 'go doc package@version' syntax
Labels: Proposal,Proposal-Accepted,GoCommand,modules

The `go doc` command displays documentation for packages in the workspace, but it would be very useful if it also worked on packages (and commands in particular) that are not part of the workspace, using an `@version` suffix. The implementation would consult the module cache, populating it as needed. For example:

```
$ go doc go.starlark.net/syntax@latest
go: downloading go.starlark.net v0.0.0-20231016134836-22325403fcb3
go: added go.starlark.net v0.0.0-20231016134836-22325403fcb3
package syntax // import "go.starlark.net/syntax"

Package syntax provides a Starlark parser and abstract syntax tree.
...
```

@rsc made the suggestion that the version suffix could be inferred if the package name was not part of the workspace, if it matched the name of a command on `$PATH`, and that command was a Go executable, and the metadata inside that Go executable provided a `module@version` provenance string.