helloadhavan/github_issues huggingface dataset:
Repository: facebook/react
Pull request: Fix prelease workflows for `dry: false`

## Summary

Follow-up to https://github.com/facebook/react/pull/33525

Fixes `Unsupported tag: "false"` (https://github.com/facebook/react/actions/runs/15773778995/job/44463562733#step:13:12) which also affects nightly releases.

## How did you test this change?

- [x] Run successful, manual prerelease from this branch: https://github.com/facebook/react/actions/runs/15774083406


Changed files:
filename: .github/workflows/runtime_prereleases.yml
patch: @@ -85,7 +85,7 @@ jobs:
             --skipTests \
             --tags=${{ inputs.dist_tag }} \
             --onlyPackages=${{ inputs.only_packages }} ${{ (inputs.dry && '') || '\'}}
-            ${{ inputs.dry && '--dry'}}
+            ${{ inputs.dry && '--dry' || '' }}
       - if: '${{ inputs.skip_packages }}'
         name: 'Publish all packages EXCEPT ${{ inputs.skip_packages }}'
         run: |
@@ -94,14 +94,14 @@ jobs:
             --skipTests \
             --tags=${{ inputs.dist_tag }} \
             --skipPackages=${{ inputs.skip_packages }} ${{ (inputs.dry && '') || '\'}}
-            ${{ inputs.dry && '--dry'}}
+            ${{ inputs.dry && '--dry' || '' }}
       - if: '${{ !(inputs.skip_packages && inputs.only_packages) }}'
         name: 'Publish all packages'
         run: |
           scripts/release/publish.js \
             --ci \
             --tags=${{ inputs.dist_tag }} ${{ (inputs.dry && '') || '\'}}
-            ${{ inputs.dry && '--dry'}}
+            ${{ inputs.dry && '--dry' || '' }}
       - name: Notify Discord on failure
         if: failure() && inputs.enableFailureNotification == true
         uses: tsickert/discord-webhook@86dc739f3f165f16dadc5666051c367efa1692f4

filename: .github/workflows/runtime_releases_from_npm_manual.yml
patch: @@ -110,7 +110,7 @@ jobs:
             --tags=${{ inputs.tags }} \
             --publishVersion=${{ inputs.version_to_publish }} \
             --onlyPackages=${{ inputs.only_packages }} ${{ (inputs.dry && '') || '\'}}
-            ${{ inputs.dry && '--dry'}}
+            ${{ inputs.dry && '--dry' || '' }}
       - if: '${{ inputs.skip_packages }}'
         name: 'Publish all packages EXCEPT ${{ inputs.skip_packages }}'
         run: |
@@ -119,7 +119,7 @@ jobs:
             --tags=${{ inputs.tags }} \
             --publishVersion=${{ inputs.version_to_publish }} \
             --skipPackages=${{ inputs.skip_packages }} ${{ (inputs.dry && '') || '\'}}
-            ${{ inputs.dry && '--dry'}}
+            ${{ inputs.dry && '--dry' || '' }}
       - name: Archive released package for debugging
         uses: actions/upload-artifact@v4
         with:
Repository: electron/electron
Pull request: fix: macOS menu item accelerators when item disabled

Backport of #49553

See that PR for details.


Notes: Fixed an issue where menu item accelerators stopped working after the item's enabled property was toggled on macOS.

Changed files:
filename: shell/browser/ui/cocoa/electron_menu_controller.mm
patch: @@ -484,8 +484,11 @@ - (void)applyStateToMenuItem:(NSMenuItem*)item {
   if (index < 0 || index >= count)
     return;
 
+  // When the menu is closed, we need to allow shortcuts to be triggered even
+  // if the menu item is disabled. So we only disable the menu item when the
+  // menu is open. This matches behavior of |validateUserInterfaceItem|.
+  item.enabled = model->IsEnabledAt(index) || !isMenuOpen_;
   item.hidden = !model->IsVisibleAt(index);
-  item.enabled = model->IsEnabledAt(index);
   item.state = model->IsItemCheckedAt(index) ? NSControlStateValueOn
                                              : NSControlStateValueOff;
 }
@@ -567,18 +570,19 @@ - (void)menuDidClose:(NSMenu*)menu {
   if (!isMenuOpen_)
     return;
 
-  bool has_close_cb = !popupCloseCallback.is_null();
+  isMenuOpen_ = NO;
+  [self refreshMenuTree:menu];
 
   // There are two scenarios where we should emit menu-did-close:
   // 1. It's a popup and the top level menu is closed.
   // 2. It's an application menu, and the current menu's supermenu
   //    is the top-level menu.
+  bool has_close_cb = !popupCloseCallback.is_null();
   if (menu != menu_) {
     if (has_close_cb || menu.supermenu != menu_)
       return;
   }
 
-  isMenuOpen_ = NO;
   if (model_)
     model_->MenuWillClose();
   // Post async task so that itemSelected runs before the close callback
Repository: vercel/next.js
Pull request: Turbopack: improve module type error message

### What?

improve module type error message

Changed files:
filename: turbopack/crates/turbopack/src/lib.rs
patch: @@ -674,10 +674,12 @@ async fn process_default_internal(
                                 ModuleIssue::new(
                                     *ident,
                                     rcstr!("Invalid module type"),
-                                    rcstr!(
+                                    format!(
                                         "The module type must be Ecmascript or Typescript to add \
-                                         Ecmascript transforms"
-                                    ),
+                                         Ecmascript transforms (got {})",
+                                        module_type
+                                    )
+                                    .into(),
                                     Some(IssueSource::from_source_only(current_source)),
                                 )
                                 .to_resolved()

filename: turbopack/crates/turbopack/src/module_options/module_rule.rs
patch: @@ -1,3 +1,5 @@
+use std::fmt::Display;
+
 use anyhow::Result;
 use bincode::{Decode, Encode};
 use turbo_rcstr::RcStr;
@@ -153,3 +155,24 @@ pub enum ModuleType {
     },
     Custom(ResolvedVc<Box<dyn CustomModuleType>>),
 }
+
+impl Display for ModuleType {
+    fn fmt(&self, f: &mut std::fmt::Formatter<'_>) -> std::fmt::Result {
+        match self {
+            ModuleType::Ecmascript { .. } => write!(f, "Ecmascript"),
+            ModuleType::Typescript { .. } => write!(f, "Typescript"),
+            ModuleType::TypescriptDeclaration { .. } => write!(f, "TypescriptDeclaration"),
+            ModuleType::EcmascriptExtensionless { .. } => write!(f, "EcmascriptExtensionless"),
+            ModuleType::Json => write!(f, "Json"),
+            ModuleType::Raw => write!(f, "Raw"),
+            ModuleType::NodeAddon => write!(f, "NodeAddon"),
+            ModuleType::CssModule => write!(f, "CssModule"),
+            ModuleType::Css { .. } => write!(f, "Css"),
+            ModuleType::StaticUrlJs { .. } => write!(f, "StaticUrlJs"),
+            ModuleType::StaticUrlCss { .. } => write!(f, "StaticUrlCss"),
+            ModuleType::InlinedBytesJs => write!(f, "InlinedBytesJs"),
+            ModuleType::WebAssembly { .. } => write!(f, "WebAssembly"),
+            ModuleType::Custom(_) => write!(f, "Custom"),
+        }
+    }
+}
Repository: electron/electron
Pull request: build(dev-deps): bump @electron/lint-roller to 3.2.0

Backport of #49565

See that PR for details.


Notes: none <!-- Please add a one-line description for app developers to read in the release notes, or 'none' if no notes relevant to app developers. Examples and help on special cases: https://github.com/electron/clerk/blob/main/README.md#examples -->


Changed files:
filename: package.json
patch: @@ -10,7 +10,7 @@
     "@electron/docs-parser": "^2.0.0",
     "@electron/fiddle-core": "^1.3.4",
     "@electron/github-app-auth": "^3.2.0",
-    "@electron/lint-roller": "^3.1.2",
+    "@electron/lint-roller": "^3.2.0",
     "@electron/typescript-definitions": "^9.1.5",
     "@octokit/rest": "^20.1.2",
     "@primer/octicons": "^10.0.0",

filename: yarn.lock
patch: @@ -592,7 +592,7 @@ __metadata:
     "@electron/docs-parser": "npm:^2.0.0"
     "@electron/fiddle-core": "npm:^1.3.4"
     "@electron/github-app-auth": "npm:^3.2.0"
-    "@electron/lint-roller": "npm:^3.1.2"
+    "@electron/lint-roller": "npm:^3.2.0"
     "@electron/typescript-definitions": "npm:^9.1.5"
     "@octokit/rest": "npm:^20.1.2"
     "@primer/octicons": "npm:^10.0.0"
@@ -869,9 +869,9 @@ __metadata:
   languageName: node
   linkType: hard
 
-"@electron/lint-roller@npm:^3.1.2":
-  version: 3.1.2
-  resolution: "@electron/lint-roller@npm:3.1.2"
+"@electron/lint-roller@npm:^3.2.0":
+  version: 3.2.0
+  resolution: "@electron/lint-roller@npm:3.2.0"
   dependencies:
     "@dsanders11/vscode-markdown-languageservice": "npm:^0.3.0"
     ajv: "npm:^8.16.0"
@@ -896,7 +896,7 @@ __metadata:
     lint-roller-markdown-links: dist/bin/lint-markdown-links.js
     lint-roller-markdown-standard: dist/bin/lint-markdown-standard.js
     lint-roller-markdown-ts-check: dist/bin/lint-markdown-ts-check.js
-  checksum: 10c0/e98a65d44b99accf44e33d7dfb1e8d85a75580a7efa7b4a570b0f8e7274aad3eb60fc6d285b5d1d78ecd093e902820222cfdf3e193eec65a8a3536d4c75bb060
+  checksum: 10c0/5331163518f41c1ea8ac302891d808891b5570f657587194717e3a8214c0d99e04949cf500ff138b02b77a373e317c3e77042b19c7fbda186d5c970b6b81df80
   languageName: node
   linkType: hard
Repository: facebook/react
Pull request: [Flight] Don't use object property initializer for async iterable

It turns out this was being compiled to a `_defineProperty` helper by Babel or Closure. We're supposed to have it error the build when we use features like this that might get compiled.

We should stick to simple ES5 features.

Changed files:
filename: packages/react-client/src/ReactFlightClient.js
patch: @@ -2077,32 +2077,34 @@ function startAsyncIterable<T>(
       }
     },
   };
-  const iterable: $AsyncIterable<T, T, void> = {
-    [ASYNC_ITERATOR](): $AsyncIterator<T, T, void> {
-      let nextReadIndex = 0;
-      return createIterator(arg => {
-        if (arg !== undefined) {
-          throw new Error(
-            'Values cannot be passed to next() of AsyncIterables passed to Client Components.',
+
+  const iterable: $AsyncIterable<T, T, void> = ({}: any);
+  // $FlowFixMe[cannot-write]
+  iterable[ASYNC_ITERATOR] = (): $AsyncIterator<T, T, void> => {
+    let nextReadIndex = 0;
+    return createIterator(arg => {
+      if (arg !== undefined) {
+        throw new Error(
+          'Values cannot be passed to next() of AsyncIterables passed to Client Components.',
+        );
+      }
+      if (nextReadIndex === buffer.length) {
+        if (closed) {
+          // $FlowFixMe[invalid-constructor] Flow doesn't support functions as constructors
+          return new ReactPromise(
+            INITIALIZED,
+            {done: true, value: undefined},
+            null,
+            response,
           );
         }
-        if (nextReadIndex === buffer.length) {
-          if (closed) {
-            // $FlowFixMe[invalid-constructor] Flow doesn't support functions as constructors
-            return new ReactPromise(
-              INITIALIZED,
-              {done: true, value: undefined},
-              null,
-              response,
-            );
-          }
-          buffer[nextReadIndex] =
-            createPendingChunk<IteratorResult<T, T>>(response);
-        }
-        return buffer[nextReadIndex++];
-      });
-    },
+        buffer[nextReadIndex] =
+          createPendingChunk<IteratorResult<T, T>>(response);
+      }
+      return buffer[nextReadIndex++];
+    });
   };
+
   // TODO: If it's a single shot iterator we can optimize memory by cleaning up the buffer after
   // reading through the end, but currently we favor code size over this optimization.
   resolveStream(
Repository: facebook/react
Pull request: Rename serializeConsoleMap/Set to serializeDebugMap/Set

Follow up to #33583. I forgot to rename these too.

Changed files:
filename: packages/react-server/src/ReactFlightServer.js
patch: @@ -2435,7 +2435,7 @@ function serializeSet(request: Request, set: Set<ReactClientValue>): string {
   return '$W' + id.toString(16);
 }
 
-function serializeConsoleMap(
+function serializeDebugMap(
   request: Request,
   counter: {objectLimit: number},
   map: Map<ReactClientValue, ReactClientValue>,
@@ -2462,7 +2462,7 @@ function serializeConsoleMap(
   return '$Q' + id.toString(16);
 }
 
-function serializeConsoleSet(
+function serializeDebugSet(
   request: Request,
   counter: {objectLimit: number},
   set: Set<ReactClientValue>,
@@ -3993,10 +3993,10 @@ function renderDebugModel(
     }
 
     if (value instanceof Map) {
-      return serializeConsoleMap(request, counter, value);
+      return serializeDebugMap(request, counter, value);
     }
     if (value instanceof Set) {
-      return serializeConsoleSet(request, counter, value);
+      return serializeDebugSet(request, counter, value);
     }
     // TODO: FormData is not available in old Node. Remove the typeof later.
     if (typeof FormData === 'function' && value instanceof FormData) {
Repository: vuejs/vue
Pull request: fix(types) add exported version to type definiton

<!--
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)
- [ ] 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:**

```ts
import Vue from 'vue';

console.log(Vue.version)
```
currently throws an Error with: `Property 'version' does not exist on type 'VueConstructor<Vue>'.`

My PR fixed that...

Changed files:
filename: types/vue.d.ts
patch: @@ -122,6 +122,7 @@ export interface VueConstructor<V extends Vue = Vue> {
   observable<T>(obj: T): T;
 
   config: VueConfiguration;
+  version: string;
 }
 
 export const Vue: VueConstructor;
Repository: vuejs/vue
Pull request: [automated] Patreon sponsors update

This is an automated pull request.

Changed files:
filename: BACKERS.md
patch: @@ -67,11 +67,6 @@ Funds donated via Patreon go directly to support Evan You's full-time work on Vu
 <table>
   <tbody>
     <tr>
-      <td align="center" valign="middle">
-        <a href="https://e.coding.net/?utm_source=vue.js" target="_blank">
-          <img width="177px" src="https://raw.githubusercontent.com/vuejs/vuejs.org/master/themes/vue/source/images/coding.png">
-        </a>
-      </td>
       <td align="center" valign="middle">
         <a href="http://www.dcloud.io/?hmsr=vuejsorg&hmpl=&hmcu=&hmkw=&hmci=" target="_blank">
           <img width="177px" src="https://raw.githubusercontent.com/vuejs/vuejs.org/master/themes/vue/source/images/dcloud.gif">

filename: README.md
patch: @@ -77,11 +77,6 @@ Funds donated via Patreon go directly to support Evan You's full-time work on Vu
 <table>
   <tbody>
     <tr>
-      <td align="center" valign="middle">
-        <a href="https://e.coding.net/?utm_source=vue.js" target="_blank">
-          <img width="177px" src="https://raw.githubusercontent.com/vuejs/vuejs.org/master/themes/vue/source/images/coding.png">
-        </a>
-      </td>
       <td align="center" valign="middle">
         <a href="http://www.dcloud.io/?hmsr=vuejsorg&hmpl=&hmcu=&hmkw=&hmci=" target="_blank">
           <img width="177px" src="https://raw.githubusercontent.com/vuejs/vuejs.org/master/themes/vue/source/images/dcloud.gif">
Repository: ollama/ollama
Pull request: ml/backend/ggml: allocate memory with malloc when loading model

On some platforms the `bts` buffer would not be freed, leading to large memory allocation on model load

Changed files:
filename: ml/backend/ggml/ggml.go
patch: @@ -312,17 +312,19 @@ func New(r *os.File, params ml.BackendParams) (ml.Backend, error) {
 					return fmt.Errorf("unassigned tensor: %s", t.Name)
 				}
 
-				bts := make([]byte, t.Size())
-				n, err := io.ReadFull(io.NewSectionReader(sr, int64(t.Offset), int64(t.Size())), bts)
-				if err != nil {
-					return err
+				bts := C.malloc(C.size_t(t.Size()))
+				if bts == nil {
+					return errors.New("failed to allocate tensor buffer")
 				}
+				defer C.free(bts)
 
-				if n != len(bts) {
-					return errors.New("short read")
+				buf := unsafe.Slice((*byte)(bts), t.Size())
+				n, err := io.ReadFull(io.NewSectionReader(sr, int64(t.Offset), int64(t.Size())), buf)
+				if err != nil || n != len(buf) {
+					return errors.New("read failed")
 				}
 
-				C.ggml_backend_tensor_set(tt, unsafe.Pointer(&bts[0]), 0, C.size_t(t.Size()))
+				C.ggml_backend_tensor_set(tt, bts, 0, C.size_t(t.Size()))
 				return nil
 			})
 		}
Repository: huggingface/transformers
Pull request: fix(models) : string mutation bug in from_proteinnet_string

### what does this PR do?

fixes a `TypeError` in `openfold_utils/protein.py` where `from_proteinnet_string` attempts to mutate an immutable string in-place.

the original code tried to assign seq[i] = "X" to handle unknown residues, which crashes. this pr replaces that logic with a list comprehension to safely sanitize the sequence, resolving the existing `FIXME`.

### before submitting
- [ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
- [x] Did you read the [contributor guideline](https://github.com/huggingface/transformers/blob/main/CONTRIBUTING.md#create-a-pull-request), Pull Request section?
- [ ] Was this discussed/approved via a Github issue or the [forum](https://discuss.huggingface.co/)? Please add a link to it if that's the case.
- [ ] Did you make sure to update the documentation with your changes? Here are the [documentation guidelines](https://github.com/huggingface/transformers/tree/main/docs), and [here are tips on formatting docstrings](https://github.com/huggingface/transformers/tree/main/docs#writing-source-documentation).
- [ ] Did you write any new necessary tests?


### who can review?

@ArthurZucker 


Changed files:
filename: src/transformers/models/esm/openfold_utils/protein.py
patch: @@ -81,9 +81,8 @@ def from_proteinnet_string(proteinnet_str: str) -> Protein:
     for g in groups:
         if g[0] == "[PRIMARY]":
             seq = g[1][0].strip()
-            for i in range(len(seq)):
-                if seq[i] not in residue_constants.restypes:
-                    seq[i] = "X"  # FIXME: strings are immutable
+            # Replace unknown residues with "X" (strings are immutable, so convert to list first)
+            seq = [char if char in residue_constants.restypes else "X" for char in seq]
             aatype = np.array(
                 [residue_constants.restype_order.get(res_symbol, residue_constants.restype_num) for res_symbol in seq]
             )
Repository: vercel/next.js
Pull request: [devtool] Add hydration diff indicator for diff lines

Add a hydration diff indicator on the top right corner to tell users which line is from client and which line is from server. Heard feedback from users that sometimes they got confused about which line is from where. Now they'll clear know that:

- `+ Client` shows `+` is client rendered content
- `- Server` shows `-` is server rendered content

<img width="579" height="225" alt="image" src="https://github.com/user-attachments/assets/5285709a-044a-4d7f-87f9-08f1199eed4e" />


Changed files:
filename: packages/next/src/next-devtools/dev-overlay/components/hydration-diff/diff-view.tsx
patch: @@ -118,14 +118,24 @@ export function PseudoHtmlDiff({
       data-nextjs-container-errors-pseudo-html
       data-nextjs-container-errors-pseudo-html-collapse={isDiffCollapsed}
     >
-      <button
-        aria-expanded={!isDiffCollapsed}
-        aria-label="complete Component Stack"
-        data-nextjs-container-errors-pseudo-html-collapse-button
-        onClick={() => toggleCollapseHtml(!isDiffCollapsed)}
-      >
-        <CollapseIcon collapsed={isDiffCollapsed} />
-      </button>
+      <div data-nextjs-hydration-diff-header>
+        <button
+          aria-expanded={!isDiffCollapsed}
+          aria-label="complete Component Stack"
+          data-nextjs-container-errors-pseudo-html-collapse-button
+          onClick={() => toggleCollapseHtml(!isDiffCollapsed)}
+        >
+          <CollapseIcon collapsed={isDiffCollapsed} />
+        </button>
+        <div data-nextjs-hydration-diff-badge>
+          <span data-nextjs-hydration-diff-badge-item="client">
+            <span>+</span> Client
+          </span>
+          <span data-nextjs-hydration-diff-badge-item="server">
+            <span>-</span> Server
+          </span>
+        </div>
+      </div>
       <pre className="nextjs__container_errors__component-stack">
         <code>{htmlComponents}</code>
       </pre>

filename: packages/next/src/next-devtools/dev-overlay/container/runtime-error/component-stack-pseudo-html.tsx
patch: @@ -89,4 +89,29 @@ export const PSEUDO_HTML_DIFF_STYLES = `
   .error-overlay-hydration-error-diff-minus-icon {
     color: var(--color-red-900);
   }
+  [data-nextjs-hydration-diff-header] {
+    display: flex;
+    align-items: center;
+    justify-content: space-between;
+    padding: 0 12px 0 0;
+  }
+  [data-nextjs-hydration-diff-badge] {
+    display: flex;
+    gap: 8px;
+    font-size: var(--size-12);
+  }
+  [data-nextjs-hydration-diff-badge-item] {
+    display: flex;
+    align-items: center;
+    gap: 4px;
+    color: var(--color-gray-900);
+  }
+  [data-nextjs-hydration-diff-badge-item='client'] span:first-child {
+    color: var(--color-green-900);
+    font-weight: bold;
+  }
+  [data-nextjs-hydration-diff-badge-item='server'] span:first-child {
+    color: var(--color-red-900);
+    font-weight: bold;
+  }
 `
Repository: ggml-org/llama.cpp
Pull request: ci : reduce webgpu tests timeout to 900s

The `test-thread-safety` test has been recently getting stuck with the WebGPU backend causing long runs. Reduce the timeout from 3600s -> 900s to reduce the CI hangs.

https://github.com/ggml-org/llama.cpp/actions/runs/23063874570/job/66997161164#step:10:17552
https://github.com/ggml-org/llama.cpp/actions/runs/23045127401/job/66932266420#step:10:17632
https://github.com/ggml-org/llama.cpp/actions/runs/22998877128/job/66778103540#step:10:17630

cc @reeselevine 

Changed files:
filename: .github/workflows/build.yml
patch: @@ -542,7 +542,7 @@ jobs:
         run: |
           cd build
           # This is using llvmpipe and runs slower than other backends
-          ctest -L main --verbose --timeout 3600
+          ctest -L main --verbose --timeout 900
 
   ubuntu-24-wasm-webgpu:
     runs-on: ubuntu-24.04