sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: MDX breaks as now requires "use client"
Labels: bug,Markdown (MDX)

### Link to the code that reproduces this issue

https://github.com/LunaticMuch/redesigned-octo-fortnight

### To Reproduce

1. Install NextJS v14
2. Follow the `[manual](https://nextjs.org/docs/app/building-your-application/configuring/mdx)` for installing MDX
3. Create a sample mdx page
4. Run `npm run dev`

### Current vs. Expected behavior

You would expect to see the mdx page, instead

```bash
 ⨯ node_modules/@mdx-js/react/lib/index.js (30:19) @ React
 ⨯ createContext only works in Client Components. Add the "use client" directive at the top of the file to use it. Read more: https://nextjs.org/docs/messages/context-in-server-component
    at __webpack_require__ (/Users/stefano/_TEST/potato-world/.next/server/webpack-runtime.js:33:42)
    at eval (./app/mdx/page.mdx:6:85)
    at (rsc)/./app/mdx/page.mdx (/Users/stefano/_TEST/potato-world/.next/server/app/mdx/page.js:184:1)
    at Function.__webpack_require__ (/Users/stefano/_TEST/potato-world/.next/server/webpack-runtime.js:33:42)
    at async Promise.all (index 0)
    at async Promise.all (index 0)
```

### 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:43 PDT 2023; root:xnu-10002.1.13~1/RELEASE_ARM64_T6000
Binaries:
  Node: 20.5.1
  npm: 9.8.0
  Yarn: 1.22.19
  pnpm: 8.7.6
Relevant Packages:
  next: 14.0.0
  eslint-config-next: 14.0.0
  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)

MDX (@next/mdx)

### Additional context

I just did a simple test following the manual.
Repository: vscode
Issue: allow configuring the ghost text style
Labels: feature-request,accessibility,ghost-text

https://github.com/github/accessibility-audits/issues/2913
Repository: transformers
Issue: example code problem
Labels: Feature request

while trying the example from https://huggingface.co/amazon/MistralLite This is the result.

python examplecode.py 
Special tokens have been added in the vocabulary, make sure the associated word embeddings are fine-tuned or trained.
Traceback (most recent call last):
  File "/home/chris/ai/text-generation-webui/amazonmistral/examplecode.py", line 8, in <module>
    model = AutoModelForCausalLM.from_pretrained(model_id,
  File "/home/chris/anaconda3/envs/textgen/lib/python3.10/site-packages/transformers/models/auto/auto_factory.py", line 571, in from_pretrained
    return model_class.from_pretrained(
  File "/home/chris/anaconda3/envs/textgen/lib/python3.10/site-packages/transformers/modeling_utils.py", line 3076, in from_pretrained
    config = cls._check_and_enable_flash_attn_2(config, torch_dtype=torch_dtype, device_map=device_map)
  File "/home/chris/anaconda3/envs/textgen/lib/python3.10/site-packages/transformers/modeling_utils.py", line 1265, in _check_and_enable_flash_attn_2
    raise ValueError(
ValueError: The current architecture does not support Flash Attention 2.0. Please open an issue on GitHub to request support for this architecture: https://github.com/huggingface/transformers/issues/new
Repository: flutter
Issue: Add swift tests for the flutter framework
Labels: a: tests,platform-ios,engine,c: proposal,P2,team-ios,triaged-ios

https://github.com/flutter/flutter/issues/118832 found an issue which manifests only if you are writing against the flutter framework with swift.  There currently is no test harness that builds against the implicit swift interface.  We should add one so that we can assert we don't again somehow change the objc interface in a way that it breaks swift usage.

cc @hellohuanlin
Repository: flutter
Issue: Engine GTK4 headers are built against vulkan but missing vulkan headers
Labels: P2,team-linux,triaged-linux

The Flutter engine build directory contains `../build/linux/debian_sid_amd64-sysroot/usr/include/gtk-4.0/gdk/gdkconfig.h` which has `GDK_RENDERING_VULKAN` defined. However there are no vulkan headers in `../build/linux/debian_sid_amd64-sysroot/usr/include/`. Suggest either adding these headers (I manually copied them across and was able to use GTK4) or compiling GTK without vulkan support.
Repository: flutter
Issue: Make 'Selectable' to support getBoxesForSelection (TextSelection)
Labels: c: new feature,framework,c: proposal,P3,f: selection,team-framework,triaged-framework

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Use case

I would like to be able to use SelectableArea to layout my fixed position text, however, I still need to gather the Rects from the text to run my custom highlighting code. 

### Proposal

I would appreciate it if 'Selectable' were to offer getBoxesForSelection (TextSelection). After a preliminary search of the source code, it would seem as though all of the different pieces of data is there, it would be a matter of tying it all the pieces together in order to cleanly return the Rects from a given TextSelection. I'd be willing to work on this as well, but I would need a little direction and recommendation on where to start. My current issue is I'm unsure in the SelectableRegion/Area exists the ability to look through all the children who are Selectable.
Repository: rust
Issue: Wrong alignment for m68k pointer types
Labels: C-bug,A-layout,O-motorola68k

I'm working on making the libcore tests pass for m68k on rustc_codegen_gcc.

It looks like LLVM rust uses the SysV ABI for m68k, but it says the alignment for pointer types is 2, while [this doc](https://m680x0.github.io/doc/abi.html) says it should be 4.

Also, [this test](https://github.com/rust-lang/rust/blob/72b3b58efc6ed4bab93ba98586b62750abbdda79/library/core/tests/ptr.rs#L720) fails.

It also says the alignment of `usize`/`isize` is 2.

cc @glaubitz
Repository: puppeteer
Issue: [Feature]: Add `getText()` method on ElementHandle
Labels: feature

### Feature description

# Shorter interface for getting text of an element

## Why ?
For people using puppeteer for web scraping, it is really common to get the `innerText` of elements.

How common ? [This question](https://stackoverflow.com/questions/55237748/how-to-get-text-inside-div-in-puppeteer) on StackOverflow has gathered 121'000 views, 54+ upvotes, and 8 answers (with plenty of upvotes also).

And there [are](https://stackoverflow.com/questions/68158601/using-puppeteer-to-extract-text-from-span) [multiple](https://stackoverflow.com/questions/66173666/how-to-get-html-element-text-using-puppeteer) [such](https://stackoverflow.com/questions/71639420/puppeteer-how-to-extract-content-from-a-page-that-have-multiple-divs-with-same) [questions]()

## Symptoms

So our code is filled with :

```js
const theElement = page.waitForSelector(sel);
const theText = theElement.$eval(el => el.innerText)
```

This two-liner seems redundant. I also have this a lot:

```js
let studData = {
            name:       await student.$eval('td:nth-of-type(1)', el => el.innerText),
            department: await student.$eval('td:nth-of-type(2)', el => el.innerText),
            date:       await student.$eval(`td:nth-of-type(4)`, el => el.innerText),
}
```

## Current workaround

None yielded from my search.

I tried to extend `ElementHandle` or `JSHandle`, but it doesn't work:

```js
    // extend Element to be able to get text directly
    puppeteer.ElementHandle.prototype.getText = async function(selector) {
        return this.$eval(selector, el => el.innerText);
      };
```
I'm not a typescript guy, but I believe [this answers](https://stackoverflow.com/a/66327189/786559) why this cannot work. 

## Desired feature

Wouldn't it be a lot more elegant if we had `ElementHandle.getText(selector)` ? 

```js
let studData = {
            name:       await student.getText('td:nth-of-type(1)'),
            department: await student.getText('td:nth-of-type(2)'),
            date:       await student.getText(`td:nth-of-type(4)`),
}
```

Or it could be called `student.$text()`. The `$` still indicates we'll take a selector as first argument.

## Alternative 

Maybe even a custom QuerySelector that doesn't just search for text, but actually returns it . (although this is not such a good solution because it woudl return string so it breaks the interface of returning a `HandleFor`)

---

Any of these interfaces would save a lot of intermediate steps.

---
Repository: next.js
Issue: Route caching not working when forced
Labels: bug

### Link to the code that reproduces this issue

https://github.com/AaronLayton/next14-cache-test

### To Reproduce

1. Load the URL and note the date in the currentTimestamp
2. Refresh fast and the datestamp stays the same
3. Give it a few seconds and then refresh and the timestamp is updated again

### Current vs. Expected behavior

I would expect this to be a static response all the time.

![Code_wuJw0Q7yVx](https://github.com/vercel/next.js/assets/694964/9d809477-57b1-4bb4-887e-bd72f5848952)


### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Pro
Binaries:
  Node: 18.17.1
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 13.5.6
  eslint-config-next: 14.0.0
  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)

App Router

### Additional context

I am exploring the caching of API routes to ensure DB requests are not called on highly used route endpoings.

I have DB calls with unstable_cache and a tag against then and then a User endpoint where I use the userId in the URL.
My aim here is to static cache the users endpoint where internally I make 4 separate cached calls to the db for separate pieces of information.

I am exploring that the users endpoint is cached all the time, until I run revalidateTag to clear 1 of the data calls and then run revalidatePath to clear the statically generated user response.

In my testing all 4 tagged calls get cleared when I revalidate the path, so was doing some testing here and it seems none of it seems to work in this way.
Repository: deno
Issue: test runner runs a test multiple times
Labels: bug,testing

I recently split multiple tests from a single file into different ones in order to _speed_ up my tests. I noticed that my brand new Mac Studio ultra was only slightly faster than my aging iMac Pro of 2017. Since tests in a file are not run in parallel, the splitting allows for faster execution.

Now one interesting thing is the name of tests split across the 4 files all start with `jetstream -`.

Running tests like this:
```bash
> deno test -r -A  --filter "jetstream - term reason"
Check file:///Users/aricart/src/github.com/nats-io/nats.deno/jetstream/tests/consumeropts_test.ts
Check file:///Users/aricart/src/github.com/nats-io/nats.deno/jetstream/tests/consumers_test.ts
...
running 1 test from ./jetstream/tests/jetstream_fetchconsumer_test.ts
jetstream - term reason ... ok (131ms)
running 1 test from ./jetstream/tests/jetstream_pullconsumer_test.ts
jetstream - term reason ... ok (131ms)
running 1 test from ./jetstream/tests/jetstream_pushconsumer_test.ts
jetstream - term reason ... ok (129ms)
running 1 test from ./jetstream/tests/jetstream_test.ts
jetstream - term reason ... ok (130ms)

ok | 4 passed | 0 failed | 924 filtered out (1s)
```

The interesting thing is that `jetstream - term reason` only exists in one file:

```bash
 grep "jetstream - term reason" jetstream/tests/*.ts
jetstream/tests/jetstream_test.ts:Deno.test("jetstream - term reason", async () => {
```

However the test runner is very happy to execute the same test 4 times and report 925 tests (that number is inflated)

This is in 
> deno 1.37.2 (release, aarch64-apple-darwin)
v8 11.8.172.13
typescript 5.2.2

But is also reproducible on 1.36.4
Repository: terminal
Issue: Profile icons not displayed on Task bar
Labels: Issue-Bug,Product-Terminal,Priority-3,Area-ShellExtension

### Windows Terminal version

 1.18.2822.0

### Windows build number

10.0.22621

### Other Software

DevHome: 0.601.297.0

Not sure if the issue is with DevDrive, or just having two drives.

### Steps to reproduce

Pin Terminal to the task bar. Or launch terminal so the icon is visible on the task bar.

Install terminal from Store.

Create profiles that have a starting directory on drive D:. For the icon, select an image on drive C:, or specify an internet address (for example, https://github.com/Azure/bicep/blob/main/docs/images/BicepLogoImage.png?raw=true)



### Expected Behavior

Prior to creating a DevDrive, all icons displayed correctly.

### Actual Behavior

Right-click on the Terminal icon in the task bar. Profile icons only show if the icon file is on the same drive as the startup directory, or an OOB icon (for example, ms-appx://ProfileIcons/pwsh.png.

![image](https://github.com/microsoft/terminal/assets/8008013/fbadd711-1bbf-4528-82c5-dd5aa152c4c7)

In the above image, the icon for the "CLI" and "Manager" profiles are on drive D:.  The third profile uses "ms-appx://ProfileIcons/pwsh.png" All others are drive C: or internet address.


**Note:**

When viewing the profiles from the selector menu (the inverted carat in the menu bar) and from the Settigns page, all icons show as expected.
Repository: go
Issue: proposal: context: context.Cause should return a wrapped error
Labels: Proposal

(I previously made a [comment about this](https://github.com/golang/go/issues/51365#issuecomment-1774588274) which I am now turning into full proposal.)

I have been following [the #51365 issue](https://github.com/golang/go/issues/51365) for some time and was really happy that it landed. But now I tried to finally update code to use the new API and I was a bit surprised by it, primarily that it makes it hard to work with logic which expects that the error is `context.Canceled` and at the same time be able to retrieve the error at the end.

What I mean is that I have code which 1) obtains the error from the context, then it 2) passes it through by returning the error through a chain of function call returns, and then 3) inspects the error and determines that it is about the context cancellation and wants to obtain the cause for it (e.g., log it).

Now, the tricky thing is that at point 3) I cannot know both if the error is context cancellation and what was the cause. I can do that only at point 1).

Options to me seems to be:
* At point 1) do `errors.Join(ctx.Err(), context.Cause(ctx))`, but this is ugly if there was no cause, because `context.Cause(ctx) in that case returns the same as `ctx.Err()`, so I am joining two same errors. So more logic to combine only if they are different. Also returned error message is ugly.
* I could use `gitlab.com/tozd/go/errors`'s [WrapWith](https://pkg.go.dev/gitlab.com/tozd/go/errors#WrapWith) which was made so that one error can be made a cause of another error, without modifying either of them. The error message is nicer, but the logic to check if they are different has still to be added.

I understand that originally `ctx.Err` could not return an `context.Canceled` error which would unwrap to the cause error to assure that `err == context.Canceled` continues to work. But why not make `context.Cause` return such an error already?  So in my view, it would be better if `context.Cause` returned:
* Same error as `ctx.Err` if there is no cause.
* An error which satisfies both `context.Is(context.Canceled)` and can be unwrapped to the cause error. This can be done by having a custom `Is` method on the error.

For `context.Cause` returned errors we do not have to assure that `err == context.Canceled` holds.

I am not sure if we can still change `context.Cause` now? Probably not? But could we then introduce yet another `context.CauseError` or something, which would return an error with the behavior above? It can probably be made in 3rd party library as well, it is not too long, but I think it would be great to have it in standard library.
Repository: vscode
Issue: Slow startup
Labels: freeze-slow-crash-leak,linux,under-discussion

VSCode is starting up slow, I have all extensions disabled.
Thanks for help.

[prof-GJjEdYT5.main.cpuprofile.txt](https://github.com/microsoft/vscode/files/13183563/prof-GJjEdYT5.main.cpuprofile.txt)
[prof-GJjEdYT5.renderer.cpuprofile.txt](https://github.com/microsoft/vscode/files/13183565/prof-GJjEdYT5.renderer.cpuprofile.txt)
[StartUpPerformance.md](https://github.com/microsoft/vscode/files/13183589/StartUpPerformance.md)
Repository: tensorflow
Issue: Remove or update zh-cn translation from installation instructions
Labels: type:docs-bug,stat:awaiting tensorflower,type:build/install

The latest version of Tensorflow does not support GPU on Windows Native. However, the [zh-cn translation](https://www.tensorflow.org/install/pip?hl=zh-cn) says nothing about it. The translation has now been outdated and misleading.

When I tried to contribute to the [l10n](/tensorflow/docs-l10n/), I only found a "[DO_NOT_TRANSLATE](/tensorflow/docs-l10n/blob/master/site/zh-cn/install/DO_NOT_TRANSLATE)" file, and the [README](/tensorflow/docs-l10n#do-not-translate) says, "tensorflow.org does not translate time-sensitive sections like the installation instructions."

If the installation instructions will not be translated any more, please remove the translation.
Repository: stable-diffusion-webui
Issue: [Bug]: ugly images generated
Labels: bug-report

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What happened?

--xformers --disable-safe-unpickle --medvram --no-half-vae

model sdXL_v10VAEFix.safetensors

Some ugly images are generated
Tell me what to do :(
Same thing on the built-in 1.5 model.

![00010-1583576541](https://github.com/AUTOMATIC1111/stable-diffusion-webui/assets/15101984/bb5ee060-3cf1-4f09-a9a9-9d917fdcda49)
![00011-2340477522](https://github.com/AUTOMATIC1111/stable-diffusion-webui/assets/15101984/820fcd5a-7f3d-4bc4-832c-80c413ef98aa)
![00013-3838988980](https://github.com/AUTOMATIC1111/stable-diffusion-webui/assets/15101984/2900a3c2-ae9b-4443-bdd3-99f2967d852f)


### Steps to reproduce the problem

run gen automatic 1111
![image](https://github.com/AUTOMATIC1111/stable-diffusion-webui/assets/15101984/ccb360be-85b8-4aa9-bd84-01587516dfdb)


### What should have happened?

beautiful image

### Sysinfo

windows 11 х64 \ 16gb ram \ GTX 1660 6gb \ E5-2678 v3

### What browsers do you use to access the UI ?

_No response_

### Console logs

```Shell
venv "D:\auto1111\stable-diffusion-webui\venv\Scripts\Python.exe"
Python 3.10.6 (tags/v3.10.6:9c7b4bd, Aug  1 2022, 21:53:49) [MSC v.1932 64 bit (AMD64)]
Version: v1.6.0
Commit hash: 5ef669de080814067961f28357256e8fe27544f4
Launching Web UI with arguments: --xformers --disable-safe-unpickle --medvram --no-half-vae
Loading weights [e6bb9ea85b] from D:\auto1111\stable-diffusion-webui\models\Stable-diffusion\sdXL_v10VAEFix.safetensors
Running on local URL:  http://127.0.0.1:7860

To create a public link, set `share=True` in `launch()`.
Startup time: 18.5s (prepare environment: 4.5s, import torch: 5.1s, import gradio: 1.6s, setup paths: 1.4s, initialize shared: 0.4s, other imports: 1.1s, setup codeformer: 0.2s, load scripts: 1.7s, create ui: 1.0s, gradio launch: 1.5s).
Creating model from config: D:\auto1111\stable-diffusion-webui\repositories\generative-models\configs\inference\sd_xl_base.yaml
Loading VAE weights specified in settings: D:\auto1111\stable-diffusion-webui\models\VAE\sdxl_vae.safetensors
Applying attention optimization: xformers... done.
Model loaded in 18.5s (load weights from disk: 2.8s, create model: 1.2s, apply weights to model: 11.0s, apply half(): 0.1s, load VAE: 0.5s, calculate empty prompt: 2.5s).
```


### Additional information

_No response_
Repository: godot
Issue: «layout_mode» can't be changed in GDExtension, impossible to use anchors in GDExtension created controls.
Labels: discussion,topic:gdextension,topic:gui

### Godot version

v4.1.2.stable.official [399c9dc39]

### System information

Godot v4.1.2.stable - Windows 10.0.19045 - Vulkan (Compatibility) - NVIDIA GeForce GTX 650 (NVIDIA; 30.0.14.7430) - 13th Gen Intel(R) Core(TM) i5-13400 (16 Threads)

### Issue description

Anchors only work in «Anchors» layout mode, but controls creating with layout mode «Position» by default, and method for changing layout_mode is not exported for GDExtension. In result, methods «set_anchors_preset», «set_offsets_preset», «set_anchors_and_offsets_preset», «set_anchor», «set_offset», «set_anchor_and_offset» don't work as supposed, they change size and position in moment of call, and don't handle any future control layout changes. In source file of Control (scene/gui/control.h) I found method «void _set_layout_mode(LayoutMode p_mode)», assume, one of previous methods should use this method internally or it should be exported, but this didn't happen. Also, seems like LayoutMode enumeration (values for changing layout_mode property) wasn't exported for GDScript, but it can be done by integer (like self.layout_mode = 1).

### Steps to reproduce

1. By official docs get and compile «godot-cpp» (https://docs.godotengine.org/en/stable/tutorials/scripting/gdextension/gdextension_cpp_example.html).
2. Check «godot-cpp/gen/include/godot_cpp/classes/control.h» that miss «set_layout_mode» or any «layout_mode» related methods.

### Minimal reproduction project

N/A
Repository: godot
Issue: GPU Particles 3D doesn't apply tangential acceleration for particles moving on a straight line
Labels: bug,topic:rendering,topic:particles

### Godot version

v4.1.2.stable; v4.2.beta3

### System information

Godot v4.2.beta3 - Windows 10.0.19045 - Vulkan (Forward+, Mobile) - GLES3 (Compatibility) - dedicated NVIDIA GeForce GTX 1650 (NVIDIA; 31.0.15.4584) - Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz (8 Threads)

### Issue description

Tangential acceleration in 3D requires for the particle's spawn position and movement to not be perfectly aligned with any axis of the particle node position.

The best workaround I've found is to add a small spread of 0.01 to velocity, so the particles won't be at the perfect center.

It works as expected on 2D, but I understand that 3D has more rotation axis that make it more complex.
Is this a limitation? Similar to not being able to have linear acceleration on stationary particles or radial/tangential acceleration on particles at the center of their emission point?


### Steps to reproduce

The reproduction project has the "main_3d" scene to show the issue, even in the editor. There is also a "main_2d" scene to show how it works on 2D.

### Minimal reproduction project

[GPUParticle3D Tangential.zip](https://github.com/godotengine/godot/files/13183761/GPUParticle3D.Tangential.zip)