sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: [Web][HTML] Text is not rendered correctly with browser language
Labels: c: regression,engine,a: internationalization,a: typography,platform-web,e: web_html,has reproducible steps,P2,found in release: 3.3,found in release: 3.7,team-web,triaged-web



I was using flutter on web (`flutter run   -d chrome --web-renderer html` ), but when I set fontSize to 11 or less, the Text cannot be rendered correctly.
![image](https://user-images.githubusercontent.com/33513462/209254957-c66eecd4-3263-4472-ac8b-3d3da905ddc2.png)

Here is my code
```dart
 @override
  Widget build(BuildContext context) {
    return Scaffold(
        body: Center(
      child: Column(
        children: [
          Text("(单个文件最大上传1GB)"),
          Text(
            "(单个文件最大上传1GB)",
            style: TextStyle(
                color: Color.fromARGB(255, 151, 151, 151), fontSize: 9),
          )
        ],
      ),
    ));
  }
```

These 2 sentences are the same, but after set style to the second sentence, words are overlapped.

## flutter version
[✓] Flutter (Channel stable, 3.3.10, on Microsoft Windows [�汾 10.0.22621.963], locale zh-CN)
    • Flutter version 3.3.10 on channel stable at D:\flutter\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 135454af32 (7 days ago), 2022-12-15 07:36:55 -0800
    • Engine revision 3316dd8728
    • Dart version 2.18.6
    • DevTools version 2.15.0
    • Pub download mirror https://pub.flutter-io.cn
    • Flutter download mirror https://storage.flutter-io.cn

[!] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at D:\androidSDK
    ✗ cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/windows#android-setup for more details.

[✓] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[✓] Visual Studio - develop for Windows (Visual Studio Community 2022 17.3.1)
    • Visual Studio at C:\Program Files\Microsoft Visual Studio\2022\Community
    • Visual Studio Community 2022 version 17.3.32811.315
    • Windows 10 SDK version 10.0.19041.0

[✓] Android Studio (version 4.1)
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] Connected device (3 available)
    • Windows (desktop) • windows • windows-x64    • Microsoft Windows [�汾 10.0.22621.963]
    • Chrome (web)      • chrome  • web-javascript • Google Chrome 108.0.5359.125
    • Edge (web)        • edge    • web-javascript • Microsoft Edge 108.0.1462.54

[✓] HTTP Host Availability
    • All required HTTP hosts are available
Repository: ant-design
Issue: browser rendering in v5 is slower than v4
Labels: Inactive,⚡️ Performance

### Reproduction link

I tried a sample code with about 20 tables:
v5 https://deepmess.com/antd5performance/5.1/build/
v4https://deepmess.com/antd5performance/4.24/build/

### Steps to reproduce
use the performance tab in chrome's develop tool to reload these 2 pages 

"Recalculate Style" takes about 200 ~350ms with v5 while the same example in v4 takes about 100ms.
![](https://azure-rnd.iot-dsa.org/file/proj/rick/assets/screenshot.png)


| Environment | Info |
| --- | --- |
| antd | 5.1.0 |
| React | 18 |
| System | windows 11 |
| Browser | Chrome 108 |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: pytorch
Issue: Remove redundant logics
Labels: triaged,oncall: pt2,module: dynamic shapes

In class SymInt, member data_(int64_t) can be casted to SymNodeImpl* by bit operation as follow:
https://github.com/pytorch/pytorch/blob/f471770fd40cae2065a8d066932ddf59e12a758d/c10/core/SymInt.h#L91-L99
It seems that `~MASK` always make 61st bit of `unextended_bits` as 0, which may leads to `(unextended_bits ^ sign_bit_mask) - sign_bit_mask` equal `unextended_bits` itself, not signed-extension(0b111........).
I’m confused that whether is there may be special circumstances to make signed-extension really happen, or just comment out L94-L96 is fine.

cc @ezyang @msaroufim @wconstab @bdhirsh @anijain2305 @zou3519 @soumith @ngimel
Repository: godot
Issue: Oneshot particles trigger when first drawn, not when emission is enabled
Labels: bug,topic:rendering,usability,topic:3d

### Godot version

4.0 dev

### System information

Arch Linux

### Issue description

Here's a demonstration and explanation:
https://youtu.be/Hgjc2RQkXMo

TL;DW:

Oneshot particle systems don't  start processing until they are draw on screen. This has an unexpected side effect: particle explosions may occur when you turn around without visible reason. The reason is that the particle system was part of a VFX scene that was spawned and triggered by a projectile 3 seconds ago, but only now the AABB of that particle system is overlapping the frustum so it gets drawn fro the first time and the particle system does it's thing delayed.

The same thing happens because of distance fade - particles that should be long gone suddenly explode when you come closer because the they are drawn for the first time and the simulation starts only at that point.

### Steps to reproduce

1. Create a oneshot particle system outside of camera view.
2. Trigger it
3. Rotate the camera to show the particle system
4. Observe the particles spawning in that moment, even though they were triggered seconds ago

### Minimal reproduction project

Just hit F5.

[Delayed Oneshot Particles.zip](https://github.com/godotengine/godot/files/10291801/Delayed.Oneshot.Particles.zip)
Repository: material-ui
Issue: [material-ui][Menu] Update icons to behave consistently in light & dark mode
Labels: bug 🐛,component: menu,package: material-ui,design

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Link to live example:
Current icon menu: https://mui.com/material-ui/react-menu/#icon-menu in dark mode

### Current behavior 😯

Light mode: 
**Active + unfocused** icons are at 54% opacity
**Active + focused** icons do not change

Dark mode: 
**Active + unfocused** icons are at 100% opacity
**Active + focused** icons do not change


### Expected behavior 🤔

[Material Design 2 guidelines for light and dark mode](https://m2.material.io/design/iconography/system-icons.html#color) indicated that active + unfocused in dark mode should be at 70% opacity. 
<img src="https://user-images.githubusercontent.com/106991024/209720154-6dae2004-564e-4f2c-9035-323b4db38038.png" width="300" alt="Light mode with icons Active + Focused state at 87% #000000; Active + Unfocused state at 54% #000000; Inactive state at 38% #000000">

<img src="https://user-images.githubusercontent.com/106991024/209262079-43c24f72-4f76-48db-a99d-a88acf392ee7.png" width="300" alt="Dark mode with icons Active + Focused state at 100% #FFFFFF; Active + Unfocused state at 70% #FFFFFF; Inactive state at 50% #FFFFFF">

Noting that [Material Design 3](https://m3.material.io/components/menus/specs) handles this differently and does not change the icon color upon focus. They opt for outlined vs filled icons in many examples. 

### Context 🔦

[#6619 comment](https://github.com/mui/mui-x/pull/6619#issuecomment-1363027203) 

### Your environment 🌎

_No response_
Repository: material-ui
Issue: [List] Provide a divider prop for inserting a separator
Labels: new feature,component: list,package: material-ui,package: joy-ui

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Summary 💡

The List component will put the `divider` element in between items (similar to [Stack](https://mui.com/material-ui/react-stack/#dividers)).

```js
<List divider={<ListDivider />}>
  <ListItem>...</ListItem>
  <ListItem>...</ListItem>
  <ListItem>...</ListItem>
</List>
```

### Examples 🌈

https://reactnative.dev/docs/flatlist#itemseparatorcomponent

### Motivation 🔦

1. The server data for rendering the list is common. Without the `divider` prop, the code could look like this:

```js
const data = useData(); // the data could be from prop or a react hook

<List>
  {data.map((item, index) => (
    <React.Fragment key={item.id}>
      {index !== 0 && <ListDivider />
      <ListItem>...</ListItem>
    </React.Fragment>
  ))}
</List>
```

It is pretty annoying to write `React.Fragment` and the condition all the time for this simple scenario.

This will be a lot easier if the List support divider prop:

```js
<List divider={<ListDivider />}>
  {data.map((item) => <ListItem key={item.id}>...</ListItem>)}
</List>
```

2. The `divider` prop will make the code transition better. When building a prototype, the code could be static:

```js
<List>
  <ListItem>...</ListItem>
  <ListDivider />
  <ListItem>...</ListItem>
  <ListDivider />
  <ListItem>...</ListItem>
  <ListDivider />
</List>
```

When it comes to integration with the server, the code will change to use `data.map(...)`:

```diff
- <List>
+ <List divider={<ListDivider />}>
+    {data.map(item =>
         <ListItem key={item.id}>...</ListItem>
+    )}
-    <ListDivider />
```
Repository: godot
Issue: Implement autowrap or horizontal scrolling for long error messages in the Errors and MSBuild bottom panels
Labels: enhancement,topic:editor,usability,topic:dotnet

### Godot version

3.5.1mono

### System information

windows10

### Issue description

Bugs in msbuild and debugger windows show up outside the window and are obscured when they encounter long entries, and there are no horizontal scroll bars, I think horizontal scroll bars or word wrap should be added for both windows

### Steps to reproduce

no

### Minimal reproduction project

no
Repository: next.js
Issue: Intellisense not working in /app/**/page.tsx
Labels: bug,TypeScript,stale

### Verify canary release

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

### Provide environment information

    Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Pro
    Binaries:
      Node: 18.12.1
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 13.0.8-canary.0
      eslint-config-next: 13.0.7
      react: 18.2.0
      react-dom: 18.2.0

warn  - Latest canary version not detected, detected: "13.0.8-canary.0", newest: "13.1.0".
        Please try the latest canary version (`npm install next@canary`) to confirm the issue still exists before creating a new issue.
        Read more - https://nextjs.org/docs/messages/opening-an-issue

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

App directory (appDir: true), TypeScript

### Link to the code that reproduces this issue

https://github.com/sohanemon/influencer-next-ts

### To Reproduce

Suggestions are not showing on any /page.tsx
![image](https://user-images.githubusercontent.com/42204040/209273788-4de75907-f8e3-486a-8e9b-73acd72d0144.png)
But it works if I change its name to /page.jsx or /page.js or anything else
![image](https://user-images.githubusercontent.com/42204040/209273952-776fe5c2-7f9e-4f5c-8b06-6cc73a21b0f3.png)


### Describe the Bug

Intellisense is working everywhere else on page.tsx.  It works if I rename the file to pAge.tsx, page.jsx or anything.

### Expected Behavior

Should show IntelliSense in page.tsx

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

Chrome Latest

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

Vercel
Repository: godot
Issue: Failed to create c#  project
Labels: enhancement,usability,topic:dotnet

### Godot version

4.0(beta 9)

### System information

windows10

### Issue description

I tried to create a new C# script and I got a error window said "Failed to create C# project" with some error message in console like these

Transient parent has another exclusive child.
  modules/mono/glue/runtime_interop.cpp:1223 - System.BadImageFormatException: 试图加载格式不正确的程序。 (0x8007000B)
     at GodotTools.ProjectEditor.ProjectGenerator.GenAndSaveGameProject(String dir, String name)
     at GodotTools.CsProjOperations.GenerateGameProject(String dir, String name) in /root/godot/modules/mono/editor/GodotTools/GodotTools/CsProjOperations.cs:line 13
  Transient parent has another exclusive child.

I make sure I have the newest .net version.

### Steps to reproduce

no

### Minimal reproduction project

It is a new project
Repository: vscode
Issue: Investigate performance of `menubar.updateOverflowAction`
Labels: bug,perf,titlebar

Follow up from https://github.com/microsoft/vscode/issues/165441

When profiling window resize on Windows, this [method](https://github.com/microsoft/vscode/blob/7b70ddcd7647b531970ecc32b14bda66c90be6c9/src/vs/base/browser/ui/menu/menubar.ts#L471) appears as somewhat slow:

<img width="643" alt="image" src="https://user-images.githubusercontent.com/900690/209278045-7783dd5a-80bb-4f74-9214-b28df3d1a309.png">

This is not entirely surprising, given it checks on `container.offsetWidth`.

Maybe we can do a bit of debouncing or scheduling on the next animation frame? Editor tabs have a similar problem where we need the container width, but we do debouncing there:

https://github.com/microsoft/vscode/blob/7b70ddcd7647b531970ecc32b14bda66c90be6c9/src/vs/workbench/browser/parts/editor/tabsTitleControl.ts#L1471

Profile:

[CPU-20221223T064049.zip](https://github.com/microsoft/vscode/files/10292340/CPU-20221223T064049.zip)

//cc @jrieken
Repository: vscode
Issue: [scss] Display a wrong selector preview when using sibling combinators in SCSS, Less
Labels: bug,help wanted,css-less-scss

Type: <b>Bug</b>

When using both style nesting and sibling combinators (`+` and `~`) in SCSS or Less, VSCode will display a wrong selector preview. I've determined that this error also occurs when no extensions are running.

For example, if writing a stylesheet like this:
```scss
.foo + .bar {
    .baz & {
        color: red;
    }
}
```
VSCode will display a wrong selector preview like this:
![image](https://user-images.githubusercontent.com/56647156/209282302-49d3c9c5-cfe1-486f-873b-ce89c28ce099.png)
```html
<element class="foo">
<element class="baz">
  …
    <element class="bar">
```

Expect this:
```html
<element class="baz">
  …
    <element class="foo">
    <element class="bar">
```

Same when using `~`:
![image](https://user-images.githubusercontent.com/56647156/209282811-e91be46b-1e1e-4931-8ab0-537007691e75.png)

Expect this:
```html
<element class="baz">
  …
    <element class="foo">
    ⋮
    <element class="bar">
```

----

VS Code version: Code 1.74.2 (e8a3071ea4344d9d48ef8a4df2c097372b0c5161, 2022-12-20T10:29:14.590Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: No

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz (8 x 2112)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: disabled_off<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_renderer: enabled_on<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: disabled_off|
|Load (avg)|undefined|
|Memory (System)|11.80GB (2.37GB free)|
|Process Argv|--crash-reporter-id 76088c10-0186-42e8-9434-fc9aba83ae2a|
|Screen Reader|no|
|VM|0%|
</details><details>
<summary>A/B Experiments</summary>

```
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
azure-dev_surveyone:30548225
vscccc:30610679
pyindex848:30577860
nodejswelcome1:30587005
2e4cg342:30602488
gswce1:30612156
3d0df643:30613357
f6dab269:30613381
fim-prod:30623723
vscsbc:30628655

```

</details>

<!-- generated by issue reporter -->
Repository: deno
Issue: node-compat: z3-solver
Labels: bug,node compat

```ts
import { init } from "npm:z3-solver";
const { Context } = await init();
const { Solver, Int, And } = new Context("main");

const x = Int.const("x");

const solver = new Solver();
solver.add(And(x.ge(0), x.le(9)));
console.log(await solver.check()); // line that fails
```
error:
```
error: Uncaught RangeError: Maximum call stack size exceeded
    this._events = Object.create(null);
                          ^
    at Function.create (<anonymous>)
    at _Worker.EventEmitter.init (https://deno.land/std@0.170.0/node/_events.mjs:176:27)
    at new EventEmitter (https://deno.land/std@0.170.0/node/_events.mjs:56:21)
    at new _Worker (https://deno.land/std@0.170.0/node/worker_threads.ts:49:5)
    at new _Worker (https://deno.land/std@0.170.0/node/worker_threads.ts:55:36)
    at new _Worker (https://deno.land/std@0.170.0/node/worker_threads.ts:55:36)
    at new _Worker (https://deno.land/std@0.170.0/node/worker_threads.ts:55:36)
    at new _Worker (https://deno.land/std@0.170.0/node/worker_threads.ts:55:36)
    at new _Worker (https://deno.land/std@0.170.0/node/worker_threads.ts:55:36)
    at new _Worker (https://deno.land/std@0.170.0/node/worker_threads.ts:55:36)
```

Also there seem to be a lint issue ? 
![image](https://user-images.githubusercontent.com/22427111/209286241-15bbde5e-616e-4009-98c5-2adb99788877.png)

The node packagae [has z3-solver/browser](https://www.npmjs.com/package/z3-solver) recomends z3-solver/browser for browsers, but I don't know how to use this with deno becasue using
```ts
import { init } from "npm:z3-solver/browser";
```
errors
```
error: Unable to load /home/mrcool/.cache/deno/npm/registry.npmjs.org/z3-solver/4.11.2/browser imported from file:///home/mrcool/dev/deno/lab/qqq.ts

Caused by:
```
Repository: go
Issue: cmd/vet: asmdecl parameter checking doesn't play well with arm64 LDP
Labels: Unfortunate,NeedsInvestigation,Analysis

### What version of Go are you using (`go version`)?

Go 1.19

### Does this issue reproduce with the latest release?

Yes, and also with tip.

And also with the latest x/tools repo (the home of the vet code).

### What operating system and processor architecture are you using (`go env`)?

I'm on linux/amd64, but I'm looking at arm64-specific checks (I'm running vet
with GOARCH=arm64).

### What did you do?

Run `GOARCH=arm64 go vet .` on a package with some code like this:

```
// func f(b []byte)
TEXT ·f(SB), NOSPLIT|NOFRAME, $0-24
	LDP b_base_len+0(FP), (R2, R3)
	...
```

Note the LDP instruction is a handy way on arm64 to load two registers at once. It's a pretty natural way to load the base pointer and length of a slice.

### What did you expect to see?

No complaints.

### What did you see instead?

    ./x_arm64.s:25:1: [arm64] f: unknown variable b_base_len; offset 0 is b_base+0(FP)

That is, vet expects that any reference to offset 0 is named `b_base`, but in this case the reference is actually 16 bytes long; it's both `base` and `len`.

I skimmed the asmdecl code but it's unfortunately not trivial to fix (there seems to be a pretty deeply-baked assumption that a reference to an FP offset corresponds to a single "var").

/cc @matloob and @timothy-king (owners of cmd/vet and x/tools/go/analysis)
Repository: three.js
Issue: Editor: Potential name conflicts when exporting multiple animated assets with `GLTFExporter`.
Labels: Bug,Editor

### Description

This is part of error stacks

```txt
Uncaught (in promise) RangeError: Invalid array length
    at getMinMax (GLTFExporter.js:248:8)
    at GLTFWriter.processAccessor (GLTFExporter.js:1038:18)
    at GLTFWriter.processAnimation (GLTFExporter.js:1857:18)
    at GLTFWriter.processInput (GLTFExporter.js:2140:9)
    at GLTFWriter.write (GLTFExporter.js:453:8)
    at GLTFExporter.parse (GLTFExporter.js:113:10)
    at UIRow.<anonymous> (Menubar.File.js:252:12)
```

### Reproduction steps

1. git clone https://github.com/mrdoob/three.js.git
2. npm install
3. npm run dev
4. after editor server running then import `three.js/examples/models/gltf/Horse.glb` and `three.js/examples/models/gltf/Stork.glb` into the editor scene
5. click file menu to export a glb file
6. open chrome dev tool to see error stacks


### Code

none

### Live example

none

### Screenshots

![image](https://user-images.githubusercontent.com/6262382/209297045-96932748-fcbc-40ae-92c0-df57dab33ac4.png)


### Version

0.147.0

### Device

Desktop

### Browser

Chrome

### OS

MacOS
Repository: flutter
Issue: Inspect Widget button is missing semantics label
Labels: framework,a: accessibility,f: inspector,P2,team-framework,triaged-framework

The widget inspector's select widget button is missing a semantics label:

<img width="292" alt="Screenshot showing an accessibility warning that the select widget button has no semantic label" src="https://user-images.githubusercontent.com/756862/209310120-b5088649-bc4a-45c8-b39e-977f41d3c3f2.png">

PR coming shortly 😊

## Steps to Reproduce

1. Whilst debugging an app, enter select widget mode
2. Select any widget
3. The magnifying glass icon that appears is missing any semantics label, and isn't accessible
Repository: react
Issue: Bug: SSR of malformed? `meta` renders nothing(working in 18.2)
Labels: Type: Bug,Component: Server Rendering

<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:

## Steps To Reproduce

1. SSR `<meta name="test" />` (`renderToString` and `renderToReadableStream`)

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example: 
- Working in 18.2: https://codesandbox.io/s/18-2-ssr-meta-only-working-t6lxvw
- render nothing in 18.3-5fcf1a4b4c2150a1b9fe0de0144a82a053c63966: https://codesandbox.io/s/18-3-5fcf1a4b4c2150a1b9fe0de0144a82a053c63966-ssr-meta-only-bug-woguy0?file=/src/index.js


## The current behavior

Renders empty string


## The expected behavior

Renders `<meta name="test" />`
Don't know if that's a valid use case but it should at least warn that the meta tag is malformed?

This broke the attribute fixture (originally reported in https://github.com/facebook/react/pull/25927).

Also:
1. `<meta name="description" content={content} />` renders nothing unless `content` is a string.
1. `<meta http-equiv />` i.e. any `http-equiv` usage no longer renders anything. It used to warn at least.