helloadhavan/github_issues huggingface dataset:
Repository: vuejs/vue
Pull request: [automated] Patreon backers update (Jul 2021

This is an automated pull request.

Changed files:
filename: BACKERS.md
patch: @@ -417,7 +417,6 @@ Funds donated via Patreon go directly to support Evan You's full-time work on Vu
 <!--50 start-->
 - Yoshitaka M
 - Peter Imburg
-- Sean Ferguson
 - Johnny Ray Austin
 - errorrik 
 - Wasim Khamlichi
@@ -431,7 +430,6 @@ Funds donated via Patreon go directly to support Evan You's full-time work on Vu
 - Sara McVey
 - Роман Латкин
 - Alex Riviere
-- WhereJuly
 - Fontis 
 - Jack 
 - Nick Carr
@@ -460,10 +458,8 @@ Funds donated via Patreon go directly to support Evan You's full-time work on Vu
 - Nick Dandakis
 - Yusuke Kawabata
 - Shawn Wildermuth
-- Andrew Willis
+- Elon Hung
 - Meinhard Dam
-- Princeyesuraj Edward
-- Juan Bermudez
 - Daniel Mattingley
 - Matt Sencenbaugh
 - Jaeyoung Lee
@@ -496,7 +492,7 @@ Funds donated via Patreon go directly to support Evan You's full-time work on Vu
 - Victor Tolbert
 - Lars Andreas Ness
 - Benjamin Listwon
-- Elon Hung
+- Juan Bermudez
 <!--10 end-->
 
 <h2 align="center">Backers via OpenCollective</h2>
Repository: nodejs/node
Pull request: test: remove duplicate wpt tests

This removes DOMException specific wpt subset that is now included in the whole webidl run (added in #61316). 

This fixes a wpt.fyi processing issue which marks our runs as invalid

<img width="1226" height="452" alt="image" src="https://github.com/user-attachments/assets/0188cc4e-0dc1-4fd1-a5fb-f4f296bbf621" />

```
Conflicting '/webidl/ecmascript-binding/es-exceptions/DOMException-constants.any.html' found in the merged report (['gs://wptd-results-buffer/nodejs/60fc8a1b-ed23-4b89-9d73-1bc9cd1e00b0/0.json'])
```

Refs: https://github.com/nodejs/node/pull/61316#issuecomment-3831209155

Changed files:
filename: test/wpt/status/webidl/ecmascript-binding/es-exceptions.json
patch: @@ -1 +0,0 @@
-{}

filename: test/wpt/test-domexception.js
patch: @@ -1,7 +0,0 @@
-'use strict';
-
-const { WPTRunner } = require('../common/wpt');
-
-const runner = new WPTRunner('webidl/ecmascript-binding/es-exceptions');
-
-runner.runJsTests();
Repository: vuejs/vue
Pull request: [automated] Patreon backers update (Jun 2021

This is an automated pull request.

Changed files:
filename: BACKERS.md
patch: @@ -440,6 +440,7 @@ Funds donated via Patreon go directly to support Evan You's full-time work on Vu
 - Pierre Baron
 - Donghai Gai
 - Aleksander Figiel
+- Dennis Zanetti
 - wickedwei 
 - Sunny Yuen
 - Jules 
@@ -467,6 +468,7 @@ Funds donated via Patreon go directly to support Evan You's full-time work on Vu
 - Matt Sencenbaugh
 - Jaeyoung Lee
 - David Kaplan
+- David Ang
 - Wakana Seki
 - Jere Sjöroos
 - Donald Fischer
Repository: ollama/ollama
Pull request: Add SimpleOllamaUnity to README.md


Added SimpleOllamaUnity - Unity Engine extension for communicating with Ollama in just two lines of code! Can work at runtime and in editor.

Changed files:
filename: README.md
patch: @@ -587,6 +587,7 @@ See the [API documentation](./docs/api.md) for all endpoints.
 - [Simple-Discord-AI](https://github.com/zyphixor/simple-discord-ai)
 - [LLM Telegram Bot](https://github.com/innightwolfsleep/llm_telegram_bot) (telegram bot, primary for RP. Oobabooga-like buttons, [A1111](https://github.com/AUTOMATIC1111/stable-diffusion-webui) API integration e.t.c)
 - [mcp-llm](https://github.com/sammcj/mcp-llm) (MCP Server to allow LLMs to call other LLMs)
+- [SimpleOllamaUnity](https://github.com/HardCodeDev777/SimpleOllamaUnity) (Unity Engine extension for communicating with Ollama in a few lines of code. Also works at runtime)
 - [UnityCodeLama](https://github.com/HardCodeDev777/UnityCodeLama) (Unity Edtior tool to analyze scripts via Ollama)
 
 ### Supported backends
Repository: vuejs/vue
Pull request: [automated] Patreon backers update (Jun 2021

This is an automated pull request.

Changed files:
filename: BACKERS.md
patch: @@ -426,10 +426,11 @@ Funds donated via Patreon go directly to support Evan You's full-time work on Vu
 <h2 align="center">Backers via Patreon</h2>
 
 <!--10 start-->
-- Sara McVey
+- Jeffrey Rennie
 - Keisuke Kita
+- Sara McVey
+- Роман Латкин
 - Alex Riviere
-- Thomas Sittig
 - WhereJuly
 - Fontis 
 - Jack 
@@ -439,17 +440,14 @@ Funds donated via Patreon go directly to support Evan You's full-time work on Vu
 - Pierre Baron
 - Donghai Gai
 - Aleksander Figiel
-- Faizal Andyka
 - wickedwei 
 - Sunny Yuen
 - Jules 
 - Zeth Odderskov
-- Santi Sanchez Canals
 - Thomas Wiedemann
 - Nobuhide Esaki
 - Roy Segall
 - Allan McKernan
-- 琚致远 
 - Diana Bergholz
 - Riki Fridrich
 - Alfonso Herrera
@@ -462,15 +460,13 @@ Funds donated via Patreon go directly to support Evan You's full-time work on Vu
 - Yusuke Kawabata
 - Shawn Wildermuth
 - Andrew Willis
-- Elon Hung
-- Роман Латкин
+- Meinhard Dam
+- Princeyesuraj Edward
 - Juan Bermudez
-- Hannes Kochniß
 - Daniel Mattingley
 - Matt Sencenbaugh
 - Jaeyoung Lee
 - David Kaplan
-- David Ang
 - Wakana Seki
 - Jere Sjöroos
 - Donald Fischer
@@ -482,7 +478,6 @@ Funds donated via Patreon go directly to support Evan You's full-time work on Vu
 - IMGNRY 
 - Jim Raden
 - Haim Yulzari
-- Anthony Estebe
 - Asaf Yishai
 - Jon Hobbs-Smith
 - Pierre Vanhulst
@@ -495,11 +490,11 @@ Funds donated via Patreon go directly to support Evan You's full-time work on Vu
 - Matsumoto Takamasa
 - Barbara Liau
 - Wen-Tien Chang
-- Stephen Michael Hartley
+- Stephen Hartley
 - Victor Tolbert
 - Lars Andreas Ness
 - Benjamin Listwon
-- Chris Calo
+- Elon Hung
 <!--10 end-->
 
 <h2 align="center">Backers via OpenCollective</h2>
Repository: electron/electron
Pull request: fix: draggable region position with docked DevTools

#### Description of Change

Closes #46256

Fixes draggable regions not updating their position when DevTools is docked to the left (or right) side of a frameless window. The issue was that `WebContentsView::NonClientHitTest()` was converting the hit-test point from widget coordinates to the `InspectableWebContentsView` coordinate space, but the draggable region stored on the `WebContents` is relative to the `contents_web_view_`. When DevTools is docked to the side, `contents_web_view_` is offset within the `InspectableWebContentsView`, causing the coordinate spaces to be misaligned — so hits were being tested against the wrong position.

This converts the point to `contents_web_view_` coordinates instead, which correctly accounts for any offset introduced by docked DevTools.

#### Checklist
<!-- Remove items that do not apply. For completed items, change [ ] to [x]. -->

- [x] PR description included
- [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 draggable regions not updating position when DevTools is docked to the left or right in a frameless window.

Changed files:
filename: shell/browser/api/electron_api_web_contents_view.cc
patch: @@ -83,8 +83,16 @@ void WebContentsView::ApplyBorderRadius() {
 
 int WebContentsView::NonClientHitTest(const gfx::Point& point) {
   if (api_web_contents_) {
+    // Convert the point to the contents view's coordinate space rather than
+    // the InspectableWebContentsView's coordinate space, because the draggable
+    // region is relative to the web content area. When DevTools is docked
+    // (e.g. to the left), the contents view is offset within the parent,
+    // so we need to account for that offset.
+    auto* inspectable_view =
+        api_web_contents_->inspectable_web_contents()->GetView();
+    auto* contents_view = inspectable_view->GetContentsView();
     gfx::Point local_point(point);
-    views::View::ConvertPointFromWidget(view(), &local_point);
+    views::View::ConvertPointFromWidget(contents_view, &local_point);
     SkRegion* region = api_web_contents_->draggable_region();
     if (region && region->contains(local_point.x(), local_point.y()))
       return HTCAPTION;

filename: shell/browser/ui/inspectable_web_contents_view.h
patch: @@ -62,9 +62,9 @@ class InspectableWebContentsView : public views::View {
   // views::View:
   void Layout(PassKey) override;
 
- private:
   views::View* GetContentsView() const;
 
+ private:
   // Owns us.
   raw_ptr<InspectableWebContents> inspectable_web_contents_;
Repository: ggml-org/llama.cpp
Pull request: memory : fix seq_id bounds in llama_memory_recurrent::state_read_meta()

Prevent reading malformed session data.

Changed files:
filename: src/llama-memory-recurrent.cpp
patch: @@ -928,11 +928,8 @@ bool llama_memory_recurrent::state_read_meta(llama_io_read_i & io, uint32_t cell
                 llama_seq_id seq_id;
                 io.read_to(&seq_id, sizeof(seq_id));
 
-                // TODO: llama_memory_recurrent should have a notion of max sequences
-                //if (seq_id < 0 || (uint32_t) seq_id >= llama_n_seq_max(ctx)) {
-                if (seq_id < 0) {
-                    //LLAMA_LOG_ERROR("%s: invalid seq_id, %d is out of range [0, %u)\n", __func__, seq_id, llama_n_seq_max(ctx));
-                    LLAMA_LOG_ERROR("%s: invalid seq_id, %d is out of range [0, inf)\n", __func__, seq_id);
+                if (seq_id < 0 || (uint32_t) seq_id >= this->n_seq_max) {
+                    LLAMA_LOG_ERROR("%s: invalid seq_id, %d is out of range [0, %u)\n", __func__, seq_id, this->n_seq_max);
                     return false;
                 }
Repository: electron/electron
Pull request: ci: fixup build stats upload on Windows

Backport of #49845

See that PR for details.


Notes: <!-- 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 -->none


Changed files:
filename: .github/actions/build-electron/action.yml
patch: @@ -95,7 +95,7 @@ runs:
         # Upload build stats to Datadog
         if ($env:DD_API_KEY) {
           try {
-            npx node electron\script\build-stats.mjs out\Default\siso.exe.INFO --upload-stats
+            npx node electron\script\build-stats.mjs out\Default\siso.exe.INFO --upload-stats ; $LASTEXITCODE = 0
           } catch {
             Write-Host "Build stats upload failed, continuing..."
           }
Repository: vuejs/vue
Pull request: fix(v-slot): fix scoped slot normalization combined with v-if

<!--
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)

- [ ] Bugfix
- [ ] Feature
- [ ] Code style update
- [ ] Refactor
- [ ] Build-related changes
- [ ] Other, please describe:

**Does this PR introduce a breaking change?** (check one)

- [ ] Yes
- [ ] No

If yes, please describe the impact and migration path for existing applications:

**The PR fulfills these requirements:**

- [ ] 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:**
Fixes #12102 
Closes #12103 

Changed files:
filename: src/core/vdom/helpers/normalize-scoped-slots.js
patch: @@ -61,10 +61,10 @@ function normalizeScopedSlot(normalSlots, key, fn) {
     res = res && typeof res === 'object' && !Array.isArray(res)
       ? [res] // single vnode
       : normalizeChildren(res)
-    let vnode: VNode = res && res[0]
+    let vnode: ?VNode = res && res[0]
     return res && (
       !vnode ||
-      (vnode.isComment && !isAsyncPlaceholder(vnode)) // #9658, #10391
+      (res.length === 1 && vnode.isComment && !isAsyncPlaceholder(vnode)) // #9658, #10391
     ) ? undefined
       : res
   }

filename: test/unit/features/component/component-slot.spec.js
patch: @@ -986,4 +986,18 @@ describe('Component slot', () => {
       expect(vm.$el.firstChild.innerHTML).toBe('<span><b>2</b></span>')
     }).then(done)
   })
+
+  // #12102
+  it('v-if inside scoped slot', () => {
+    const vm = new Vue({
+      template: `<test><template #custom><span v-if="false">a</span><span>b</span></template></test>`,
+      components: {
+        test: {
+          template: `<div><slot name="custom"/></div>`
+        }
+      }
+    }).$mount()
+
+    expect(vm.$el.innerHTML).toBe(`<!----><span>b</span>`)
+  })
 })
Repository: nodejs/node
Pull request: test: update WPT for url to e3c46fdf55

This is an automated update of the WPT for url to https://github.com/web-platform-tests/wpt/commit/e3c46fdf5587369127de2863a7e38295f4e07f16.

Changed files:
filename: test/fixtures/wpt/README.md
patch: @@ -28,7 +28,7 @@ Last update:
 - resource-timing: https://github.com/web-platform-tests/wpt/tree/22d38586d0/resource-timing
 - resources: https://github.com/web-platform-tests/wpt/tree/1d2c5fb36a/resources
 - streams: https://github.com/web-platform-tests/wpt/tree/bc9dcbbf1a/streams
-- url: https://github.com/web-platform-tests/wpt/tree/81a2aed262/url
+- url: https://github.com/web-platform-tests/wpt/tree/e3c46fdf55/url
 - urlpattern: https://github.com/web-platform-tests/wpt/tree/a2e15ad405/urlpattern
 - user-timing: https://github.com/web-platform-tests/wpt/tree/5ae85bf826/user-timing
 - wasm/jsapi: https://github.com/web-platform-tests/wpt/tree/cde25e7e3c/wasm/jsapi

filename: test/fixtures/wpt/url/resources/urltestdata.json
patch: @@ -6835,6 +6835,34 @@
     "search": "",
     "hash": ""
   },
+  {
+    "input": "..",
+    "base": "abc://x/y/z/C:/",
+    "href": "abc://x/y/z/",
+    "protocol": "abc:",
+    "username": "",
+    "password": "",
+    "hostname": "x",
+    "port": "",
+    "host": "x",
+    "pathname": "/y/z/",
+    "search": "",
+    "hash": ""
+  },
+  {
+    "input": "..",
+    "base": "file://x/C:/",
+    "href": "file://x/C:/",
+    "protocol": "file:",
+    "username": "",
+    "password": "",
+    "hostname": "x",
+    "port": "",
+    "host": "x",
+    "pathname": "/C:/",
+    "search": "",
+    "hash": ""
+  },
   "# Do not drop the host in the presence of a drive letter",
   {
     "input": "file://example.net/C:/",

filename: test/fixtures/wpt/versions.json
patch: @@ -72,7 +72,7 @@
     "path": "streams"
   },
   "url": {
-    "commit": "81a2aed262a6e82824afa19509583a736da580ed",
+    "commit": "e3c46fdf5587369127de2863a7e38295f4e07f16",
     "path": "url"
   },
   "urlpattern": {
Repository: ollama/ollama
Pull request: llm: Make "POST predict" error message more informative

"POST predict" basically means that the runner has crashed, which can have many reasons. However, many people think this is a specific error and either report only this message or group together unrelated bugs. This replaces it with a more friendly and helpful message.

Changed files:
filename: llm/server.go
patch: @@ -797,7 +797,8 @@ func (s *llmServer) Completion(ctx context.Context, req CompletionRequest, fn fu
 
 	res, err := http.DefaultClient.Do(serverReq)
 	if err != nil {
-		return fmt.Errorf("POST predict: %v", err)
+		slog.Error("post predict", "error", err)
+		return errors.New("model runner has unexpectedly stopped, this may be due to resource limitations or an internal error, check ollama server logs for details")
 	}
 	defer res.Body.Close()
Repository: vercel/next.js
Pull request: Fix a small doc typo

<!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:

## For Contributors

### Improving Documentation

- Run `pnpm prettier-fix` to fix formatting issues before opening the PR.
- Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md


## For Maintainers

- Minimal description (aim for explaining to someone not on the team to understand the PR)
- When linking to a Slack thread, you might want to share details of the conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic behind a change

### What?

### Why?

### How?

Closes NEXT-
Fixes #

-->


Changed files:
filename: packages/next/src/server/config-shared.ts
patch: @@ -482,7 +482,7 @@ export interface ExperimentalConfig {
   turbopackMinify?: boolean
 
   /**
-   * Enable support for `with {type: "module"}` for ESM imports.
+   * Enable support for `with {type: "bytes"}` for ESM imports.
    */
   turbopackImportTypeBytes?: boolean
Repository: ggml-org/llama.cpp
Pull request: server: use httplib dynamic threads

Alternative to https://github.com/ggml-org/llama.cpp/pull/20799

Fix https://github.com/ggml-org/llama.cpp/issues/20684

Server can now create up to maximum of 1024 threads on demand. Dynamic threads will be terminated once they finish their task.

Changed files:
filename: tools/server/server-http.cpp
patch: @@ -227,11 +227,17 @@ bool server_http_context::init(const common_params & params) {
 
     int n_threads_http = params.n_threads_http;
     if (n_threads_http < 1) {
-        // +2 threads for monitoring endpoints
-        n_threads_http = std::max(params.n_parallel + 2, (int32_t) std::thread::hardware_concurrency() - 1);
+        // +4 threads for monitoring, health and some threads reserved for MCP and other tasks in the future
+        n_threads_http = std::max(params.n_parallel + 4, (int32_t) std::thread::hardware_concurrency() - 1);
     }
     LOG_INF("%s: using %d threads for HTTP server\n", __func__, n_threads_http);
-    srv->new_task_queue = [n_threads_http] { return new httplib::ThreadPool(n_threads_http); };
+    srv->new_task_queue = [n_threads_http] {
+        // spawn n_threads_http fixed thread (always alive), while allow up to 1024 max possible additional threads
+        // when n_threads_http is used, server will create new "dynamic" threads that will be destroyed after processing each request
+        // ref: https://github.com/yhirose/cpp-httplib/pull/2368
+        size_t max_threads = (size_t)n_threads_http + 1024;
+        return new httplib::ThreadPool(n_threads_http, max_threads);
+    };
 
     //
     // Web UI setup
Repository: huggingface/transformers
Pull request: Fix CLIPOutput attentions not being returned

## What does this PR do?

Fixes #43618

### Problem

Since v5, `CLIPVisionModel` and `CLIPTextModel` no longer return attention weights when `output_attentions=True`:

```python
model = CLIPModel.from_pretrained(model_path, attn_implementation="eager")
vision_outputs = model.vision_model(pixel_values=pixel_values, output_attentions=True)
assert vision_outputs.attentions is not None  # FAILS - attentions is None
```

### Root Cause

`CLIPVisionTransformer.forward()` and `CLIPTextTransformer.forward()` both call their respective encoders which return a `BaseModelOutput` containing `hidden_states` and `attentions`. However, when constructing the `BaseModelOutputWithPooling` return value, only `last_hidden_state` and `pooler_output` were being passed - the `hidden_states` and `attentions` fields were omitted.

### Solution

Pass through `hidden_states` and `attentions` from the encoder outputs to the return value in both transformers:

```python
return BaseModelOutputWithPooling(
    last_hidden_state=last_hidden_state,
    pooler_output=pooled_output,
    hidden_states=encoder_outputs.hidden_states,  # NEW
    attentions=encoder_outputs.attentions,        # NEW
)
```

## Who can review?

@yonigozlan @molbap

Changed files:
filename: src/transformers/models/clip/modeling_clip.py
patch: @@ -587,6 +587,8 @@ def forward(
         return BaseModelOutputWithPooling(
             last_hidden_state=last_hidden_state,
             pooler_output=pooled_output,
+            hidden_states=encoder_outputs.hidden_states,
+            attentions=encoder_outputs.attentions,
         )
 
 
@@ -682,6 +684,8 @@ def forward(
         return BaseModelOutputWithPooling(
             last_hidden_state=last_hidden_state,
             pooler_output=pooled_output,
+            hidden_states=encoder_outputs.hidden_states,
+            attentions=encoder_outputs.attentions,
         )
 
 

filename: src/transformers/models/metaclip_2/modeling_metaclip_2.py
patch: @@ -984,6 +984,8 @@ def forward(
         return BaseModelOutputWithPooling(
             last_hidden_state=last_hidden_state,
             pooler_output=pooled_output,
+            hidden_states=encoder_outputs.hidden_states,
+            attentions=encoder_outputs.attentions,
         )
Repository: electron/electron
Pull request: ci: fixup build stats upload on Windows

#### Description of Change
Occasionally Windows builds are failing with the following error:
```
2026-02-18T14:58:23.5809594Z ERROR: Invalid string length
2026-02-18T14:58:23.7429489Z ##[error]Process completed with exit code 1.
```

This appears to be coming from the step to `Upload build stats to Datadog`.  On non Windows platforms we ignore the exit code from this step; this PR does the same for Windows platforms.
<!--
Thank you for your Pull Request. Please provide a description above and review
the requirements below.

Contributors guide: https://github.com/electron/electron/blob/main/CONTRIBUTING.md
-->

#### 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] [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: <!-- 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 -->none


Changed files:
filename: .github/actions/build-electron/action.yml
patch: @@ -98,7 +98,7 @@ runs:
         # Upload build stats to Datadog
         if ($env:DD_API_KEY) {
           try {
-            npx node electron\script\build-stats.mjs out\Default\siso.exe.INFO --upload-stats
+            npx node electron\script\build-stats.mjs out\Default\siso.exe.INFO --upload-stats ; $LASTEXITCODE = 0
           } catch {
             Write-Host "Build stats upload failed, continuing..."
           }