helloadhavan/github_issues huggingface dataset:
Repository: electron/electron
Pull request: fix: fix devtools patch type error on release builds

#### Description of Change

This PR fixes a type error in the DevTools extension patch that flags on release builds.

#### Checklist
<!-- Remove items that do not apply. For completed items, change [ ] to [x]. -->

- [ ] PR description included
- [ ] I have built and tested this PR
- [ ] `npm test` passes
- [ ] tests are [changed or added](https://github.com/electron/electron/blob/main/docs/development/testing.md)
- [ ] relevant API documentation, tutorials, and examples are updated and follow the [documentation style guide](https://github.com/electron/electron/blob/main/docs/development/style-guide.md)
- [ ] [PR release notes](https://github.com/electron/clerk/blob/main/README.md) describe the change in a way relevant to app developers, and are [capitalized, punctuated, and past tense](https://github.com/electron/clerk/blob/main/README.md#examples).

#### Release Notes

Notes: none


Changed files:
filename: patches/devtools_frontend/feat_allow_enabling_extension_panels_on_custom_protocols.patch
patch: @@ -7,14 +7,14 @@ This allows us to show Chrome extension panels on pages served over
 custom protocols.
 
 diff --git a/front_end/core/root/Runtime.ts b/front_end/core/root/Runtime.ts
-index 4f91e0d7b1d289f5eaaaf7c4e174679881fd9a54..cfdfdfe03edfdf89374763f5b3086f0eb15fa72c 100644
+index 4f91e0d7b1d289f5eaaaf7c4e174679881fd9a54..a26b2852662d10f10824cc45735ef12f19a3df86 100644
 --- a/front_end/core/root/Runtime.ts
 +++ b/front_end/core/root/Runtime.ts
 @@ -645,6 +645,7 @@ export type HostConfig = Platform.TypeScriptUtilities.RecursivePartial<{
     * or guest mode, rather than a "normal" profile.
     */
    isOffTheRecord: boolean,
-+  devToolsExtensionSchemes: string[],
++  devToolsExtensionSchemes: readonly string[],
    devToolsEnableOriginBoundCookies: HostConfigEnableOriginBoundCookies,
    devToolsAnimationStylesInStylesTab: HostConfigAnimationStylesInStylesTab,
    devToolsJpegXlImageFormat: HostConfigJpegXlImageFormat,
Repository: nodejs/node
Pull request: doc: add Rafael to last security release steward

Refs: https://github.com/nodejs-private/security-release/pull/71

Changed files:
filename: doc/contributing/security-release-process.md
patch: @@ -39,6 +39,7 @@ The current security stewards are documented in the main Node.js
 | NodeSource              | Rafael          | 2025-May-14  |
 | NodeSource              | Rafael          | 2025-Jul-15  |
 | HeroDevs and NodeSource | Marco / Rafael  | 2026-Jan-13  |
+| NodeSource              | Rafael          | 2026-Mar-24  |
 | Datadog                 | Bryan           |              |
 | IBM                     | Joe             |              |
 | Platformatic            | Matteo          |              |
Repository: ollama/ollama
Pull request: scripts: only prompt for CLI install on macOS when required


Changed files:
filename: scripts/install.sh
patch: @@ -72,10 +72,12 @@ if [ "$OS" = "Darwin" ]; then
     unzip -q "$TEMP_DIR/Ollama-darwin.zip" -d "$TEMP_DIR"
     mv "$TEMP_DIR/Ollama.app" "/Applications/"
 
-    status "Adding 'ollama' command to PATH (may require password)..."
-    mkdir -p "/usr/local/bin" 2>/dev/null || sudo mkdir -p "/usr/local/bin"
-    ln -sf "/Applications/Ollama.app/Contents/Resources/ollama" "/usr/local/bin/ollama" 2>/dev/null || \
-        sudo ln -sf "/Applications/Ollama.app/Contents/Resources/ollama" "/usr/local/bin/ollama"
+    if [ ! -L "/usr/local/bin/ollama" ] || [ "$(readlink "/usr/local/bin/ollama")" != "/Applications/Ollama.app/Contents/Resources/ollama" ]; then
+        status "Adding 'ollama' command to PATH (may require password)..."
+        mkdir -p "/usr/local/bin" 2>/dev/null || sudo mkdir -p "/usr/local/bin"
+        ln -sf "/Applications/Ollama.app/Contents/Resources/ollama" "/usr/local/bin/ollama" 2>/dev/null || \
+            sudo ln -sf "/Applications/Ollama.app/Contents/Resources/ollama" "/usr/local/bin/ollama"
+    fi
 
     if [ -z "${OLLAMA_NO_START:-}" ]; then
         status "Starting Ollama..."
Repository: huggingface/transformers
Pull request: Continuous batching thread safety

# What does this PR do?

Fix two `nogil` threading bugs (reproduced on 3.14) :

1. Continus Batching crashes with torch graph errors with 2 threads on 2 separate model instances (same model path, but two distinct instances). Cause is missing `capture_error_mode="thread_local"` so the graph capture operate safely in thread_local mode. 

```py
with torch.cuda.graph(
                    graph,
                    stream=compute_stream,
                    pool=self.graph_pool,
                    capture_error_mode="thread_local",
                ):
```                

2. Model loading of same model path but 2 different threads (2 different instaances) have `meta` device tensor issues due to `tie_weight()` code failing to execute because to `tie_weight` skipping logic/state is not thread safe. Fixed using contextar scope  state. Triggered with 2 threads loading at the same time with Llama 3.2 1B instruct. 
 
## 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).
- [x] Did you write any new necessary tests?


## Who can review?

@ArthurZucker @remi @McPatate 

Please trigger ci to run the new unit tests. My own tests are passing that use this PR code. 




Changed files:
filename: src/transformers/generation/continuous_batching/continuous_api.py
patch: @@ -464,7 +464,15 @@ def _generation_step(self, model: nn.Module, logit_processor: LogitsProcessorLis
                 # torch.cuda.current_stream().wait_stream(compute_stream)
                 # Capture
                 graph = torch.cuda.CUDAGraph()
-                with torch.cuda.graph(graph, stream=compute_stream, pool=self.graph_pool):
+                # Continuous batching can run multiple manager threads concurrently in one process.
+                # PyTorch's default capture mode ("global") errors on CUDA actions from other threads,
+                # which invalidates unrelated captures even when each manager uses a different device.
+                with torch.cuda.graph(
+                    graph,
+                    stream=compute_stream,
+                    pool=self.graph_pool,
+                    capture_error_mode="thread_local",
+                ):
                     forward_fn(
                         model, batch_data, logit_processor, do_sample, carry_over_ids, prev_output_ids, output_ids
                     )
Repository: rust-lang/rust
Pull request: Stabilize const ControlFlow predicates

<!-- homu-ignore:start -->
<!--
If this PR is related to an unstable feature or an otherwise tracked effort,
please link to the relevant tracking issue here. If you don't know of a related
tracking issue or there are none, feel free to ignore this.

This PR will get automatically assigned to a reviewer. In case you would like
a specific user to review your work, you can assign it to them by using

    r? <reviewer name>
-->
<!-- homu-ignore:end -->
Closes: rust-lang/rust#148738 (tracking issue)
Related: rust-lang/rust#140266 (moved the relevant const-unstables to that feature)
r? @dtolnay

Changed files:
filename: library/core/src/ops/control_flow.rs
patch: @@ -151,7 +151,7 @@ impl<B, C> ControlFlow<B, C> {
     /// ```
     #[inline]
     #[stable(feature = "control_flow_enum_is", since = "1.59.0")]
-    #[rustc_const_unstable(feature = "min_const_control_flow", issue = "148738")]
+    #[rustc_const_stable(feature = "min_const_control_flow", since = "CURRENT_RUSTC_VERSION")]
     pub const fn is_break(&self) -> bool {
         matches!(*self, ControlFlow::Break(_))
     }
@@ -168,7 +168,7 @@ impl<B, C> ControlFlow<B, C> {
     /// ```
     #[inline]
     #[stable(feature = "control_flow_enum_is", since = "1.59.0")]
-    #[rustc_const_unstable(feature = "min_const_control_flow", issue = "148738")]
+    #[rustc_const_stable(feature = "min_const_control_flow", since = "CURRENT_RUSTC_VERSION")]
     pub const fn is_continue(&self) -> bool {
         matches!(*self, ControlFlow::Continue(_))
     }
@@ -264,7 +264,7 @@ impl<B, C> ControlFlow<B, C> {
     /// ```
     #[inline]
     #[unstable(feature = "control_flow_ok", issue = "140266")]
-    #[rustc_const_unstable(feature = "min_const_control_flow", issue = "148738")]
+    #[rustc_const_unstable(feature = "control_flow_ok", issue = "140266")]
     pub const fn break_ok(self) -> Result<B, C> {
         match self {
             ControlFlow::Continue(c) => Err(c),
@@ -377,7 +377,7 @@ impl<B, C> ControlFlow<B, C> {
     /// ```
     #[inline]
     #[unstable(feature = "control_flow_ok", issue = "140266")]
-    #[rustc_const_unstable(feature = "min_const_control_flow", issue = "148738")]
+    #[rustc_const_unstable(feature = "control_flow_ok", issue = "140266")]
     pub const fn continue_ok(self) -> Result<C, B> {
         match self {
             ControlFlow::Continue(c) => Ok(c),
Repository: nodejs/node
Pull request: test: avoid flaky run wait in debugger restart test

## Summary

Follow-up to #61773

`test/parallel/test-debugger-run-after-quit-restart.js` can still flake on macOS unusual-path runs around `run`.
`stepCommand('run')` expects a break message immediately, but `run` may return `ok`/prompt before the break output.
This change switches those calls to `command('run')` and keeps `waitForInitialBreak()` for the actual break sync.

failed CI logs:
- https://github.com/nodejs/node/actions/runs/22647161362  (line:44)
- https://github.com/nodejs/node/actions/runs/22158756428 (line:74)

## Testing

```bash
UNUSUAL="$HOME/dir with \$unusual\"chars?'åß∂ƒ©∆¬…\`"
mkdir -p "$UNUSUAL"
ln -sfn "$PWD" "$UNUSUAL/node"
cd "$UNUSUAL/node"
```

- [x] `./tools/test.py -p actions parallel/test-debugger-run-after-quit-restart`
- [x] `./tools/test.py -p actions -j1 --repeat 50 parallel/test-debugger-run-after-quit-restart`
- [x] `./tools/test.py -p actions -j1 --repeat 50 parallel/test-debugger-run-after-quit-restart` (unusual path)

Refs: https://github.com/nodejs/node/issues/61762


Changed files:
filename: test/parallel/test-debugger-run-after-quit-restart.js
patch: @@ -41,7 +41,7 @@ const path = require('path');
     .then(() => {
       assert.match(cli.output, /Use `run` to start the app again/);
     })
-    .then(() => cli.stepCommand('run'))
+    .then(() => cli.command('run'))
     .then(() => cli.waitForInitialBreak())
     .then(() => cli.waitForPrompt())
     .then(() => {
@@ -71,7 +71,7 @@ const path = require('path');
     .then(() => {
       assert.match(cli.output, /Use `run` to start the app again/);
     })
-    .then(() => cli.stepCommand('run'))
+    .then(() => cli.command('run'))
     .then(() => cli.waitForInitialBreak())
     .then(() => cli.waitForPrompt())
     .then(() => {
Repository: vercel/next.js
Pull request: TURBOPACK: support parse windows absolute path with single slash

The path like which starts with single slash:

```bash
C:/Users/demo/src/index.ts
```

Shoud parse as windows path.

Changed files:
filename: turbopack/crates/turbopack-core/src/resolve/parse.rs
patch: @@ -90,7 +90,8 @@ fn split_off_query_fragment(mut raw: &str) -> (Pattern, RcStr, RcStr) {
     (Pattern::Constant(RcStr::from(raw)), query, hash)
 }
 
-static WINDOWS_PATH: LazyLock<Regex> = LazyLock::new(|| Regex::new(r"^[A-Za-z]:\\|\\\\").unwrap());
+static WINDOWS_PATH: LazyLock<Regex> =
+    LazyLock::new(|| Regex::new(r"^[A-Za-z]:[/\\]|^\\\\").unwrap());
 static URI_PATH: LazyLock<Regex> = LazyLock::new(|| Regex::new(r"^([^/\\:]+:)(.+)$").unwrap());
 static DATA_URI_REMAINDER: LazyLock<Regex> =
     LazyLock::new(|| Regex::new(r"^([^;,]*)(?:;([^,]+))?,(.*)$").unwrap());
@@ -855,6 +856,27 @@ pub async fn stringify_data_uri(
 mod tests {
     use super::*;
 
+    #[test]
+    fn test_parse_windows_paths() {
+        assert_eq!(
+            Request::Windows {
+                path: rcstr!(r"C:\Users\demo\src\index.ts").into(),
+                query: rcstr!(""),
+                fragment: rcstr!(""),
+            },
+            Request::parse_ref(rcstr!(r"C:\Users\demo\src\index.ts").into())
+        );
+
+        assert_eq!(
+            Request::Windows {
+                path: rcstr!("C:/Users/demo/src/index.ts").into(),
+                query: rcstr!(""),
+                fragment: rcstr!(""),
+            },
+            Request::parse_ref(rcstr!("C:/Users/demo/src/index.ts").into())
+        );
+    }
+
     #[test]
     fn test_parse_module() {
         assert_eq!(
Repository: electron/electron
Pull request: fix: register `PrintDialogLinuxFactory` on Linux

#### Description of Change

Fixes https://github.com/electron/electron/issues/50420

Chromium 145 refactored Linux print dialog creation to use a factory pattern instead of directly calling `LinuxUi::CreatePrintDialog()`. Chrome registers this factory in
`ChromeBrowserMainExtraPartsViewsLinux::ToolkitInitialized()`, but Electron did not, causing `PrintingContextLinux::EnsurePrintDialog()` to leave `print_dialog_` null on every call.

Without a dialog, `UseDefaultSettings()` and `UpdatePrinterSettings()` return success but with empty/unprocessed settings, causing `PrintMsgPrintParamsIsValid()` to fail. This broke both `window.print()` and `webContents.print()`.

#### Checklist
<!-- Remove items that do not apply. For completed items, change [ ] to [x]. -->

- [x] PR description included
- [x] I have built and tested this PR
- [x] `npm test` passes
- [x] [PR release notes](https://github.com/electron/clerk/blob/main/README.md) describe the change in a way relevant to app developers, and are [capitalized, punctuated, and past tense](https://github.com/electron/clerk/blob/main/README.md#examples).

#### Release Notes

Notes: Fixed printing on Linux failing with "Invalid printer settings".

Changed files:
filename: shell/browser/electron_browser_main_parts.cc
patch: @@ -127,6 +127,10 @@
 #include "shell/common/plugin_info.h"
 #endif  // BUILDFLAG(ENABLE_PLUGINS)
 
+#if BUILDFLAG(ENABLE_PRINTING)
+#include "components/printing/common/print_dialog_linux_factory.h"
+#endif
+
 namespace electron {
 
 namespace {
@@ -415,6 +419,10 @@ void ElectronBrowserMainParts::ToolkitInitialized() {
 
   ui::LinuxUi::SetInstance(linux_ui);
 
+#if BUILDFLAG(ENABLE_PRINTING)
+  print_dialog_factory_ = std::make_unique<printing::PrintDialogLinuxFactory>();
+#endif
+
   // Cursor theme changes are tracked by LinuxUI (via a CursorThemeManager
   // implementation). Start observing them once it's initialized.
   ui::CursorFactory::GetInstance()->ObserveThemeChanges();

filename: shell/browser/electron_browser_main_parts.h
patch: @@ -14,8 +14,13 @@
 #include "content/public/browser/browser_main_parts.h"
 #include "electron/buildflags/buildflags.h"
 #include "mojo/public/cpp/bindings/remote.h"
+#include "printing/buildflags/buildflags.h"
 #include "services/device/public/mojom/geolocation_control.mojom.h"
 
+#if BUILDFLAG(ENABLE_PRINTING)
+#include "printing/printing_context_linux.h"
+#endif
+
 class BrowserProcessImpl;
 class IconManager;
 
@@ -179,6 +184,11 @@ class ElectronBrowserMainParts : public content::BrowserMainParts {
   std::unique_ptr<display::ScopedNativeScreen> screen_;
 #endif
 
+#if BUILDFLAG(ENABLE_PRINTING)
+  std::unique_ptr<printing::PrintingContextLinux::PrintDialogFactory>
+      print_dialog_factory_;
+#endif
+
   static ElectronBrowserMainParts* self_;
 };
Repository: huggingface/transformers
Pull request: Fix backward compatibility for full path imports of Fast Image Processors

# What does this PR do?

Solve import errors when trying to import `from transformers.models.llama4.image_processing_llama4_fast import Llama4ImageProcessorFast` for example

Changed files:
filename: src/transformers/__init__.py
patch: @@ -822,6 +822,28 @@ def _get_target():
     _create_module_alias(f"{__name__}.tokenization_utils", ".tokenization_utils_sentencepiece")
     _create_module_alias(f"{__name__}.image_processing_utils_fast", ".image_processing_backends")
 
+    for _proc_file in sorted((Path(__file__).parent / "models").rglob("image_processing_*.py")):
+        _model = _proc_file.parent.name
+        _module = _proc_file.stem
+        _target = f".models.{_model}.{_module}"
+        _create_module_alias(f"{__name__}.models.{_model}.{_module}_fast", _target)
+
+        # Also map XImageProcessorFast -> XImageProcessor for backward compat with old class names.
+        def getattr_factory(target):
+            def _getattr(name):
+                new_name = name.removesuffix("Fast")
+                logger.warning(
+                    "Accessing `%s` from `%s`. Returning `%s` instead. Behavior may be "
+                    "different and this alias will be removed in future versions.",
+                    name,
+                    target,
+                    new_name,
+                )
+                return getattr(importlib.import_module(target, __name__), new_name)
+
+            return _getattr
+
+        sys.modules[f"{__name__}.models.{_model}.{_module}_fast"].__getattr__ = getattr_factory(_target)
 
 if not is_torch_available():
     logger.warning_advice(

filename: utils/check_repo.py
patch: @@ -1191,6 +1191,9 @@ def ignore_undocumented(name: str) -> bool:
     # BLT models are internal building blocks, tested implicitly through BltForCausalLM
     if name.startswith("Blt"):
         return True
+    # image_processing_*_fast are backward-compat module aliases, not public objects.
+    if name.startswith("image_processing_") and name.endswith("_fast"):
+        return True
     if name in SHOULD_HAVE_THEIR_OWN_PAGE:
         return True
     return False
Repository: nodejs/node
Pull request: doc: fix stray carriage return in packages.md

Removes a stray carriage return that's wreaking havoc in local and CI checkouts.

Refs: https://openjs-foundation.slack.com/archives/C019Y2T6STH/p1774015976262609
Refs: https://github.com/nodejs/node/pull/62302
Refs: https://github.com/nodejs/node/actions/runs/23347139396/job/67915524762?pr=61767

Changed files:
filename: doc/api/packages.md
patch: @@ -1012,7 +1012,7 @@ added: v0.4.0
 The `"main"` field defines the entry point of a package when imported by name
 via a `node_modules` lookup.  Its value is a path.
 
-The [`"exports"`][] field, if it exists, takes precedence over the
+The [`"exports"`][] field, if it exists, takes precedence over the
 `"main"` field when importing the package by name.
 
 It also defines the script that is used when the [package directory is loaded
Repository: electron/electron
Pull request: fix: hex-encode Windows notification icon temp filenames

Backport of #50454

See that PR for details.


Notes: Fixed a bug where Windows notification icons could fail to save because their temporary filenames contained invalid characters.


Changed files:
filename: shell/browser/notifications/win/notification_presenter_win.cc
patch: @@ -72,7 +72,8 @@ std::wstring NotificationPresenterWin::SaveIconToFilesystem(
 
   std::string filename;
   if (origin.is_valid()) {
-    filename = base::SHA1HashString(origin.spec()) + ".png";
+    const auto hash = base::SHA1HashString(origin.spec());
+    filename = base::HexEncode(hash) + ".png";
   } else {
     const int64_t now_usec = base::Time::Now().since_origin().InMicroseconds();
     filename = base::NumberToString(now_usec) + ".png";
Repository: ollama/ollama
Pull request: x: configurable model load timeout

Use `OLLAMA_LOAD_TIMEOUT` when loading experimental models.

Changed files:
filename: x/imagegen/server.go
patch: @@ -21,6 +21,7 @@ import (
 	"sync"
 	"time"
 
+	"github.com/ollama/ollama/envconfig"
 	"github.com/ollama/ollama/llm"
 	"github.com/ollama/ollama/ml"
 	"github.com/ollama/ollama/x/imagegen/manifest"
@@ -195,7 +196,7 @@ func (s *Server) Ping(ctx context.Context) error {
 // waitUntilRunning waits for the subprocess to be ready.
 func (s *Server) waitUntilRunning() error {
 	ctx := context.Background()
-	timeout := time.After(2 * time.Minute)
+	timeout := time.After(envconfig.LoadTimeout())
 	ticker := time.NewTicker(100 * time.Millisecond)
 	defer ticker.Stop()
Repository: vercel/next.js
Pull request: Fix DataUriSource description to include "data:" prefix

### What?

Fix the `description()` method of `DataUriSource` in Turbopack to include the full `data:` URI prefix in the display string.

**Before:** `data URI content (svg+xml;charset=utf8,...)`
**After:** `data URI content (data:svg+xml;charset=utf8,...)`

### Why?

The previous implementation only included the raw data content starting from the media type, omitting the `data:` scheme prefix. This made the description string look malformed and not recognizable as a data URI — especially in error messages where this description is shown to developers.

The fix reconstructs the proper data URI format (`data:<media_type>[;<encoding>],<data>`) before truncating it to 50 characters, so the displayed prefix is a valid (partial) data URI that developers can recognize and understand.

### How?

In `turbopack/crates/turbopack-core/src/data_uri_source.rs`, the `description()` function now builds the full data URI string first (`data:{media_type}{sep}{encoding},{data}`), then takes the first 50 characters of that. This ensures the `data:` scheme prefix is always present in the truncated display.

Closes NEXT-

Changed files:
filename: turbopack/crates/turbopack-core/src/data_uri_source.rs
patch: @@ -42,11 +42,15 @@ impl DataUriSource {
 impl Source for DataUriSource {
     #[turbo_tasks::function]
     async fn description(&self) -> Result<Vc<RcStr>> {
+        let media_type = &self.media_type;
+        let encoding = &self.encoding;
         let data = self.data.await?;
-        // Include a short prefix of the raw data for identification; data URIs
-        // can be very long so we cap it at 50 characters.
-        let prefix: String = data.chars().take(50).collect();
-        let ellipsis = if data.len() > 50 { "..." } else { "" };
+        // Build the data URI prefix for identification; data URIs can be very
+        // long so we cap the total display at 50 characters.
+        let sep = if encoding.is_empty() { "" } else { ";" };
+        let full_with_data = format!("data:{media_type}{sep}{encoding},{data}");
+        let prefix: String = full_with_data.chars().take(50).collect();
+        let ellipsis = if full_with_data.len() > 50 { "..." } else { "" };
         Ok(Vc::cell(
             format!("data URI content ({prefix}{ellipsis})").into(),
         ))