helloadhavan/github_issues huggingface dataset:
Repository: facebook/react
Pull request: Update DEVELOPMENT_GUIDE.md

fix: update CONTRIBUTING.md link path

Updated the relative path to CONTRIBUTING.md from `../CONTRIBUTING.md`  to `./../../CONTRIBUTING.md` to ensure the correct file is referenced.

<!--
  Thanks for submitting a pull request!
  We appreciate you spending the time to work on these changes. Please provide enough information so that others can review your pull request. The three fields below are mandatory.

  Before submitting a pull request, please make sure the following is done:

  1. Fork [the repository](https://github.com/facebook/react) and create your branch from `main`.
  2. Run `yarn` in the repository root.
  3. If you've fixed a bug or added code that should be tested, add tests!
  4. Ensure the test suite passes (`yarn test`). Tip: `yarn test --watch TestName` is helpful in development.
  5. Run `yarn test --prod` to test in the production environment. It supports the same options as `yarn test`.
  6. If you need a debugger, run `yarn test --debug --watch TestName`, open `chrome://inspect`, and press "Inspect".
  7. Format your code with [prettier](https://github.com/prettier/prettier) (`yarn prettier`).
  8. Make sure your code lints (`yarn lint`). Tip: `yarn linc` to only check changed files.
  9. Run the [Flow](https://flowtype.org/) type checks (`yarn flow`).
  10. If you haven't already, complete the CLA.

  Learn more about contributing: https://reactjs.org/docs/how-to-contribute.html
-->

## Summary

<!--
 Explain the **motivation** for making this change. What existing problem does the pull request solve?
-->

## How did you test this change?

<!--
  Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes the user interface.
  How exactly did you verify that your PR solves the issue you wanted to solve?
  If you leave this empty, your PR will very likely be closed.
-->


Changed files:
filename: compiler/docs/DEVELOPMENT_GUIDE.md
patch: @@ -1,6 +1,6 @@
 # React Compiler Development Guide
 
-Note: for general notes about contributing, see the [CONTRIBUTING.md](../CONTRIBUTING.md).
+Note: for general notes about contributing, see the [CONTRIBUTING.md](../../CONTRIBUTING.md).
 
 ## Compiler Development
Repository: vuejs/vue
Pull request: clone `isComment` when cloneVNode

<!--
Please make sure to read the Pull Request Guidelines:
https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#pull-request-guidelines
-->

<!-- PULL REQUEST TEMPLATE -->
<!-- (Update "[ ]" to "[x]" to check a box) -->

**What kind of change does this PR introduce?** (check at least one)

- [x] Bugfix
- [ ] Feature
- [ ] Code style update
- [ ] Refactor
- [ ] Build-related changes
- [ ] Other, please describe:

**Does this PR introduce a breaking change?** (check one)

- [ ] Yes
- [x] No

If yes, please describe the impact and migration path for existing applications:

**The PR fulfills these requirements:**

- [x] It's submitted to the `dev` branch for v2.x (or to a previous version branch), _not_ the `master` branch
- [ ] When resolving a specific issue, it's referenced in the PR's title (e.g. `fix #xxx[,#xxx]`, where "xxx" is the issue number)
- [x] All tests are passing: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#development-setup
- [ ] New/updated tests are included

If adding a **new feature**, the PR's description includes:
- [ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

**Other information:**

when call `cloneVNode`, the key `isComment` was lost. this could effect `patch` and component was re-created. see this [demo](https://jsfiddle.net/16hf328c/)


Changed files:
filename: src/core/vdom/vnode.js
patch: @@ -84,6 +84,7 @@ export function cloneVNode (vnode: VNode): VNode {
   cloned.ns = vnode.ns
   cloned.isStatic = vnode.isStatic
   cloned.key = vnode.key
+  cloned.isComment = vnode.isComment
   cloned.isCloned = true
   return cloned
 }
Repository: facebook/react
Pull request: [rollup] Add support for running prebuild commands


Extracting portions of #32416 for easier review.

Adds a new `prebuild` option to allow for a prebuild command to be run prior to building the bundle.

Co-authored-by: michael faith <michaelfaith@users.noreply.github.com>
---
[//]: # (BEGIN SAPLING FOOTER)
Stack created with [Sapling](https://sapling-scm.com). Best reviewed with [ReviewStack](https://reviewstack.dev/facebook/react/pull/32592).
* __->__ #32592
* #32591
* #32590
* #32589
* #32588

Changed files:
filename: scripts/rollup/build.js
patch: @@ -12,6 +12,7 @@ const stripBanner = require('rollup-plugin-strip-banner');
 const chalk = require('chalk');
 const resolve = require('@rollup/plugin-node-resolve').nodeResolve;
 const fs = require('fs');
+const childProcess = require('child_process');
 const argv = require('minimist')(process.argv.slice(2));
 const Modules = require('./modules');
 const Bundles = require('./bundles');
@@ -812,6 +813,11 @@ function handleRollupError(error) {
   }
 }
 
+function runShellCommand(command) {
+  console.log(chalk.dim('Running: ') + chalk.cyan(command));
+  childProcess.execSync(command, {stdio: 'inherit', shell: true});
+}
+
 async function buildEverything() {
   if (!argv['unsafe-partial']) {
     await asyncRimRaf('build');
@@ -859,6 +865,9 @@ async function buildEverything() {
 
   // eslint-disable-next-line no-for-of-loops/no-for-of-loops
   for (const [bundle, bundleType] of bundles) {
+    if (bundle.prebuild) {
+      runShellCommand(bundle.prebuild);
+    }
     await createBundle(bundle, bundleType);
   }
Repository: ggml-org/llama.cpp
Pull request: github : add missing backends to issue templates

Hi, I’d like to report some issues related to the Hexagon backend, but it appears to be missing on issue template. I opened this PR to add it, as well as any other backends I found to be absent. Please let me know if anything needs adjustment.

Changed files:
filename: .github/ISSUE_TEMPLATE/010-bug-compilation.yml
patch: @@ -41,7 +41,7 @@ body:
     attributes:
         label: GGML backends
         description: Which GGML backends do you know to be affected?
-        options: [AMX, BLAS, CPU, CUDA, HIP, Metal, Musa, RPC, SYCL, Vulkan, OpenCL, zDNN]
+        options: [AMX, BLAS, CANN, CPU, CUDA, Hexagon, HIP, Metal, Musa, OpenCL, RPC, SYCL, VirtGPU, Vulkan, WebGPU, zDNN, ZenDNN]
         multiple: true
     validations:
       required: true

filename: .github/ISSUE_TEMPLATE/011-bug-results.yml
patch: @@ -42,7 +42,7 @@ body:
     attributes:
         label: GGML backends
         description: Which GGML backends do you know to be affected?
-        options: [AMX, BLAS, CPU, CUDA, HIP, Metal, Musa, RPC, SYCL, Vulkan, OpenCL, zDNN]
+        options: [AMX, BLAS, CANN, CPU, CUDA, Hexagon, HIP, Metal, Musa, OpenCL, RPC, SYCL, VirtGPU, Vulkan, WebGPU, zDNN, ZenDNN]
         multiple: true
     validations:
       required: true
Repository: huggingface/transformers
Pull request: Fix interactions between require_read_token and staticmethod

As @Sai-Suraj-27 pointed out in #42476, there's something weird going on with static methods in some tests. The cause seems to be `require_read_token` having a faulty check for `staticmethod` which obliterates args in some cases. Trying this to see if it helps!

Changed files:
filename: src/transformers/testing_utils.py
patch: @@ -638,6 +638,9 @@ def require_read_token(test_case):
                 if getattr(attr, "__require_read_token__", False):
                     continue
                 wrapped = require_read_token(attr)
+                if isinstance(inspect.getattr_static(test_case, attr_name), staticmethod):
+                    # Don't accidentally bind staticmethods to `self`
+                    wrapped = staticmethod(wrapped)
                 setattr(test_case, attr_name, wrapped)
         return test_case
     else:
@@ -650,10 +653,6 @@ def wrapper(*args, **kwargs):
                 with patch("huggingface_hub.utils._headers.get_token", return_value=token):
                     return test_case(*args, **kwargs)
             else:  # Allow running locally with the default token env variable
-                # dealing with static/class methods and called by `self.xxx`
-                if "staticmethod" in inspect.getsource(test_case).strip():
-                    if len(args) > 0 and isinstance(args[0], unittest.TestCase):
-                        return test_case(*args[1:], **kwargs)
                 return test_case(*args, **kwargs)
 
         wrapper.__require_read_token__ = True
Repository: electron/electron
Pull request: fix: CSD window frame tiles properly on Wayland

Backport of #48765

See that PR for details.


Notes: Corrected the appearance of tiled windows on GNOME (when frame: true), and removed resize handles from tiled edges.

Changed files:
filename: shell/browser/ui/electron_desktop_window_tree_host_linux.cc
patch: @@ -100,13 +100,19 @@ void ElectronDesktopWindowTreeHostLinux::OnWindowStateChanged(
 void ElectronDesktopWindowTreeHostLinux::OnWindowTiledStateChanged(
     ui::WindowTiledEdges new_tiled_edges) {
   if (auto* const view = native_window_view_->GetClientFrameViewLinux()) {
-    bool maximized = new_tiled_edges.top && new_tiled_edges.left &&
-                     new_tiled_edges.bottom && new_tiled_edges.right;
+    // GNOME on Ubuntu reports all edges as tiled
+    // even if the window is only half-tiled so do not trust individual edge
+    // values.
+    bool maximized = native_window_view_->IsMaximized();
     bool tiled = new_tiled_edges.top || new_tiled_edges.left ||
                  new_tiled_edges.bottom || new_tiled_edges.right;
     view->set_tiled(tiled && !maximized);
   }
   UpdateFrameHints();
+  ScheduleRelayout();
+  if (GetWidget()->non_client_view()) {
+    GetWidget()->non_client_view()->SchedulePaint();
+  }
 }
 
 void ElectronDesktopWindowTreeHostLinux::UpdateWindowState(

filename: shell/browser/ui/views/client_frame_view_linux.cc
patch: @@ -40,7 +40,6 @@ namespace {
 
 // These values should be the same as Chromium uses.
 constexpr int kResizeBorder = 10;
-constexpr int kResizeInsideBoundsSize = 5;
 
 ui::NavButtonProvider::ButtonState ButtonStateToNavButtonProviderState(
     views::Button::ButtonState state) {
@@ -151,8 +150,19 @@ gfx::Insets ClientFrameViewLinux::RestoredMirroredFrameBorderInsets() const {
 
 gfx::Insets ClientFrameViewLinux::RestoredFrameBorderInsets() const {
   gfx::Insets insets = GetFrameProvider()->GetFrameThicknessDip();
-  insets.SetToMax(GetInputInsets());
-  return insets;
+  const gfx::Insets input = GetInputInsets();
+
+  auto expand_if_visible = [](int side_thickness, int min_band) {
+    return side_thickness > 0 ? std::max(side_thickness, min_band) : 0;
+  };
+
+  gfx::Insets merged;
+  merged.set_top(expand_if_visible(insets.top(), input.top()));
+  merged.set_left(expand_if_visible(insets.left(), input.left()));
+  merged.set_bottom(expand_if_visible(insets.bottom(), input.bottom()));
+  merged.set_right(expand_if_visible(insets.right(), input.right()));
+
+  return merged;
 }
 
 gfx::Insets ClientFrameViewLinux::GetInputInsets() const {
@@ -197,9 +207,7 @@ void ClientFrameViewLinux::OnWindowButtonOrderingChange() {
 }
 
 int ClientFrameViewLinux::ResizingBorderHitTest(const gfx::Point& point) {
-  return ResizingBorderHitTestImpl(point,
-                                   RestoredMirroredFrameBorderInsets() +
-                                       gfx::Insets(kResizeInsideBoundsSize));
+  return ResizingBorderHitTestImpl(point, RestoredMirroredFrameBorderInsets());
 }
 
 gfx::Rect ClientFrameViewLinux::GetBoundsForClientView() const {
Repository: vuejs/vue
Pull request: Fix use mixin  API feat continuous operation

### Example
```javascript
import Vue from 'vue'
Vue
  .use(...)
  .use(...)
  .use(...)
  .mixin(...)
  .mixin(...)
  .mixin(...)
```

Changed files:
filename: src/core/global-api/mixin.js
patch: @@ -5,5 +5,6 @@ import { mergeOptions } from '../util/index'
 export function initMixin (Vue: GlobalAPI) {
   Vue.mixin = function (mixin: Object) {
     this.options = mergeOptions(this.options, mixin)
+    return this
   }
 }

filename: src/core/global-api/use.js
patch: @@ -6,7 +6,7 @@ export function initUse (Vue: GlobalAPI) {
   Vue.use = function (plugin: Function | Object) {
     /* istanbul ignore if */
     if (plugin.installed) {
-      return
+      return this
     }
     // additional parameters
     const args = toArray(arguments, 1)
Repository: vercel/next.js
Pull request: [devtool] make the draggable content selective

Make the text under `<Draggable>` in devtool selectable.

The previous `select: none` on the `<Draggable>` was added to avoid text being selected during dragging in safari (@RobPruzan). The logic is moved to pointer move handler, we don't need to explicitly `override user-select: none` on the top for all cases.

Changed files:
filename: packages/next/src/next-devtools/dev-overlay/components/errors/dev-tools-indicator/draggable.tsx
patch: @@ -143,17 +143,7 @@ export function Draggable({
   }
 
   return (
-    <div
-      {...props}
-      ref={ref}
-      {...drag}
-      style={{
-        touchAction: 'none',
-        userSelect: 'none',
-        WebkitUserSelect: 'none',
-        ...props.style,
-      }}
-    >
+    <div {...props} {...drag} ref={ref}>
       {children}
     </div>
   )
@@ -208,6 +198,7 @@ function useDrag(options: UseDragOptions) {
     velocities.current = []
 
     ref.current?.classList.remove('dev-tools-grabbing')
+    ref.current?.style.removeProperty('-webkit-user-select')
     document.body.style.removeProperty('user-select')
     document.body.style.removeProperty('-webkit-user-select')
   }, [])
@@ -310,6 +301,7 @@ function useDrag(options: UseDragOptions) {
         machine.current = { state: 'drag', pointerId: e.pointerId }
         ref.current?.setPointerCapture(e.pointerId)
         ref.current?.classList.add('dev-tools-grabbing')
+        ref.current?.style.setProperty('-webkit-user-select', 'none')
         document.body.style.userSelect = 'none'
         document.body.style.webkitUserSelect = 'none'
         options.onDragStart?.()

filename: packages/next/src/next-devtools/dev-overlay/components/overview/segment-explorer.css
patch: @@ -41,7 +41,6 @@
   display: flex;
   align-items: center;
   white-space: pre;
-  cursor: default;
   color: var(--color-gray-1000);
 }
 
@@ -90,8 +89,6 @@
   line-height: 16px;
   font-size: var(--size-12);
   font-weight: 500;
-  user-select: none;
-  cursor: pointer;
   background-color: var(--color-gray-300);
   color: var(--color-gray-1000);
 }
Repository: nodejs/node
Pull request: test: spin longer on flaky platforms for test-worker-prof

Try spinning longer to get more ticks on flaky platforms and reduce flakiness.

Refs: https://github.com/nodejs/reliability/blob/main/reports/2025-10-29.md
<!--
Before submitting a pull request, please read:

- the CONTRIBUTING guide at https://github.com/nodejs/node/blob/HEAD/CONTRIBUTING.md
- the commit message formatting guidelines at
  https://github.com/nodejs/node/blob/HEAD/doc/contributing/pull-requests.md#commit-message-guidelines

For code changes:
1. Include tests for any bug fixes or new features.
2. Update documentation if relevant.
3. Ensure that `make -j4 test` (UNIX), or `vcbuild test` (Windows) passes.

If you believe this PR should be highlighted in the Node.js CHANGELOG
please add the `notable-change` label.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.
-->


Changed files:
filename: test/sequential/test-worker-prof.js
patch: @@ -16,10 +16,16 @@ if (process.argv[2] === 'child') {
   console.log('parent prof file:', parentProf);
 
   const { Worker } = require('worker_threads');
+  let spinTime = 1500;
+  if (common.isWindows || common.isMacOS || process.arch === 's390x') {
+    // Windows and MacOS tend to be flaky in CI, s390x as well.
+    // Give them more spins.
+    spinTime = 4500;
+  }
   const w = new Worker(`
   const { parentPort, workerData } = require('worker_threads');
 
-  const SPIN_MS = 1500;
+  const SPIN_MS = ${spinTime};
   const start = Date.now();
   parentPort.on('message', (data) => {
     if (Date.now() - start < SPIN_MS) {
Repository: facebook/react
Pull request: [rollup] Fix codeFrame is not a function


Extracting portions of #32416 for easier review.

Fixes a small issue where `codeFrame` is not a function when a rollup error was encountered.

Co-authored-by: michael faith <michaelfaith@users.noreply.github.com>
---
[//]: # (BEGIN SAPLING FOOTER)
Stack created with [Sapling](https://sapling-scm.com). Best reviewed with [ReviewStack](https://reviewstack.dev/facebook/react/pull/32591).
* #32592
* __->__ #32591
* #32590
* #32589
* #32588

Changed files:
filename: scripts/rollup/build.js
patch: @@ -22,7 +22,7 @@ const useForks = require('./plugins/use-forks-plugin');
 const dynamicImports = require('./plugins/dynamic-imports');
 const Packaging = require('./packaging');
 const {asyncRimRaf} = require('./utils');
-const codeFrame = require('@babel/code-frame');
+const codeFrame = require('@babel/code-frame').default;
 const Wrappers = require('./wrappers');
 
 const RELEASE_CHANNEL = process.env.RELEASE_CHANNEL;
Repository: ggml-org/llama.cpp
Pull request: ggml-cpu: arm64: Fix wrong memcpy length for q4_K block_interleave == 4

https://github.com/ggml-org/llama.cpp/issues/19561 reports issues with the stack for Q4_K. 
I can't reproduce the issue locally, but the `make_block_q4_Kx8` function would write past the buffer size 4 extra bytes,  which could be the issue. 

@taronaeo, since you found the problem, are you able to check if this patch fixes it?
 
Q6_K and Q5_K (https://github.com/ggml-org/llama.cpp/pull/19356, still opened at the moment this description was written) already address this problem.

Changed files:
filename: ggml/src/ggml-cpu/repack.cpp
patch: @@ -1916,9 +1916,10 @@ static block_q4_Kx8 make_block_q4_Kx8(block_q4_K * in, unsigned int blck_size_in
         int src_offset = (i / 8) * blck_size_interleave;
         int dst_offset = i * blck_size_interleave;
 
+        // buffer large enough for the max interleave block size (8 bytes)
         uint64_t elems;
-        memcpy(&elems, &in[src_id].qs[src_offset], sizeof(uint64_t));
-        memcpy(&out.qs[dst_offset], &elems, sizeof(uint64_t));
+        memcpy(&elems, &in[src_id].qs[src_offset], blck_size_interleave);
+        memcpy(&out.qs[dst_offset], &elems, blck_size_interleave);
     }
 
     // The below logic is designed so as to unpack and rearrange scales and mins values in Q4_K
Repository: facebook/react
Pull request: [ez] Run Prettier on eslint-plugin-react-compiler/src/types


Extracting portions of #32416 for easier review.

This PR contains small formatting fixes.

Co-authored-by: michael faith <michaelfaith@users.noreply.github.com>
---
[//]: # (BEGIN SAPLING FOOTER)
Stack created with [Sapling](https://sapling-scm.com). Best reviewed with [ReviewStack](https://reviewstack.dev/facebook/react/pull/32590).
* #32592
* #32591
* __->__ #32590
* #32589
* #32588

Changed files:
filename: compiler/packages/eslint-plugin-react-compiler/src/types/hermes-eslint.d.ts
patch: @@ -6,7 +6,7 @@
  */
 
 // v0.17.1
-declare module "hermes-eslint" {
+declare module 'hermes-eslint' {
   // https://fburl.com/2vikhmaa
   type ParseForESLintOptions = {
     /**
@@ -37,7 +37,7 @@ declare module "hermes-eslint" {
     /**
      * The source type of the script.
      */
-    sourceType: "script" | "module";
+    sourceType: 'script' | 'module';
 
     /**
      * Ignore <fbt /> JSX elements when adding references to the module-level `React` variable.

filename: compiler/packages/eslint-plugin-react-compiler/src/types/hermes-parser.d.ts
patch: @@ -6,14 +6,14 @@
  */
 
 // v0.17.1
-declare module "hermes-parser" {
+declare module 'hermes-parser' {
   type HermesParserOptions = {
     allowReturnOutsideFunction?: boolean;
     babel?: boolean;
-    flow?: "all" | "detect";
+    flow?: 'all' | 'detect';
     enableExperimentalComponentSyntax?: boolean;
     sourceFilename?: string;
-    sourceType?: "module" | "script" | "unambiguous";
+    sourceType?: 'module' | 'script' | 'unambiguous';
     tokens?: boolean;
   };
   export function parse(code: string, options: Partial<HermesParserOptions>);
Repository: huggingface/transformers
Pull request: [kernels] fix typing for Kernel mapping

# What does this PR do?

Fix the type of the kernel mapping

Changed files:
filename: src/transformers/integrations/hub_kernels.py
patch: @@ -78,7 +78,7 @@ def use_kernel_func_from_hub(func_name: str):
                 )
             return lambda func: func
 
-    _KERNEL_MAPPING: dict[str, dict[Device | str, LayerRepository]] = {
+    _KERNEL_MAPPING: dict[str, dict[Device | str, LayerRepository | dict[Mode, LayerRepository]]] = {
         "MultiScaleDeformableAttention": {
             "cuda": LayerRepository(
                 repo_id="kernels-community/deformable-detr",
@@ -328,7 +328,7 @@ def lazy_load_kernel(kernel_name: str, mapping: dict[str, ModuleType | None] = _
     if kernel_name in mapping and isinstance(mapping[kernel_name], ModuleType):
         return mapping[kernel_name]
     if kernel_name not in _HUB_KERNEL_MAPPING:
-        logger.warning(f"Kernel {kernel_name} not found in _HUB_KERNEL_MAPPING")
+        logger.warning_once(f"Kernel {kernel_name} not found in _HUB_KERNEL_MAPPING")
         mapping[kernel_name] = None
         return None
     if _kernels_available: